GitHub and Cloudflare are connected. Custom domain target is command.odarius.com.
Suite governance
Odarius Command Center
Owner/admin control plane for app registry, backlog, style, security map, and build sequence.
Dashboard
Current sequence: Governance → Command Center MVP → AIOS → Aziana → ExpenseOS.
Static shell first, then app registry, backlog, security map, and AIOS handoff.
Top-level admin AI layer. Do not bury it inside any single company app.
Track where keys live, never the values.
App Registry
Each app remains separate. Command Center coordinates; it does not swallow the apps.
Master Backlog
Separated by stage so cleanup, build, refactor, design, security, and deployment do not get mixed.
Global Style
One professional suite identity, with each app allowed its own accent.
Design feel
Serious, clean, premium, operational, fast to understand.
UI pattern
Cards for summaries, tables for records, drawers/modals for detail flows.
Do not do
No random colors, no overloaded tabs, no marketing fluff inside admin tools.
Security Map
Track locations and responsibilities, not raw credentials.
| System | Purpose | Policy |
|---|---|---|
| Cloudflare | Pages, Workers, DNS, env vars | Secrets stay in dashboard/env only. |
| GitHub | Repos, issues, deploy source | No raw API keys in code/docs. |
| Supabase | Shared data layer | Scope by app + user_id. Additive migrations only. |
| Zoho | Accounting/export integrations | Credentials outside repo. |
AIOS Handoff
AIOS is the top-level admin AI layer. It can power app widgets, but it must not become only an Aziana widget.
Next sequence
- Review AIOS repo state.
- Align AIOS startup docs with governance.
- Define Command Center → AIOS context handoff.
- Then continue Aziana integration.
Audit Log
Early static audit log. Later this should become authenticated and server-backed.