Control Arcana is the administrative control panel for the Arcanada ecosystem (my.arcanada.ai). It aggregates Auth Arcana, Ops Bot, Status, Model Connector, Publisher, and Datarim into four working planes: Infrastructure/Ops, Spaces, Marketing/Publishing, and Content/CRM. Read-only and dry-run operations can proceed autonomously.
The current codebase routes mutations through checksum-bound, auditable helpers and the policy of the selected space; production availability is confirmed only when the live health version matches the reviewed release. Actions marked operator-gated still require approval, and public publishing remains an explicit gate. Control duplicates none of the underlying services — it brings them into one interface.
- Status
- Live
- Autonomy (AAL)
- L2 → L4
- Address
- my.arcanada.ai
- Mutations
- Audited helpers; gated actions need approval
01
Aggregates, does not duplicate
Auth Arcana, Ops Bot, Status, Model Connector, Publisher, Datarim, the spaces registry and the content/CRM layer are brought into one interface; the underlying services stay where they are.
02
Four working planes
Infrastructure/Ops, Spaces, Marketing/Publishing and Content/CRM.
03
Autonomy with a boundary
Read-only and dry-run paths proceed on their own; mutations go through audited helpers and the policy of the selected space, operator-gated actions still need approval, and public publishing remains an explicit gate.
Capabilities
Status not stated
- Infrastructure and Ops panels over existing service health
- Spaces management plane with dry-run agent dispatch
- Publisher integration for marketing and social workflows
- Content/CRM state layer for drafts, variants, channels, and publications
- Adapter-based aggregation of Auth, Status, Model Connector, Publisher, and Datarim
Current autonomy level
Weakest link
Several adapter panels soft-degrade when upstream services or env vars are absent; the dashboard depends on each source exposing stable read contracts.
Roadmap to L4
- Harden every adapter with freshness, provenance, and typed errors.
- Complete the content/CRM stateful layer and Publisher approval flow.
- Add safe operator actions with audit records and space-policy gating.
Next step
Explore the available product and its current limits
LIVE means the project is available now; the weakest link and roadmap above state the current version’s limits.
Review the path to the target level