Managed Spaces is the registry layer under spaces/. It records where each project space lives, which servers and credentials references belong to it, which knowledge backend is active, and how future dashboards should address it.
It is the bridge between the human knowledge base and Control Arcana automation.
- Status
- Live
- Autonomy (AAL)
- L1 → L3
- Source of truth
- spaces/{name}/space.yml
- Secrets
- Never stored — references only
01
One file per space
Each space has a machine-readable record: its servers, access metadata, knowledge backend and history of backend switches.
02
No secrets in the registry
Servers and access are described through credentials references, so the registry can live in git without exposing anything.
03
Bridge to automation
The same record tells Control Arcana how to address a space and tells agents which autonomy policy applies to it.
Capabilities
Status not stated
- spaces/{name}/space.yml as source of truth
- Server inventory, access metadata, and credentials references without secrets
- Knowledge-backend history per space
- Dashboard configuration contract for Control Arcana
- Autonomy policy per space for feature branch, merge, and deploy decisions
Current autonomy level
Weakest link
The registry is active but still manually curated; stale metadata can misroute agents unless checked against live probes.
Roadmap to L3
- Add schema validation and drift probes for every registered space.
- Expose the registry through Control Arcana read-only dashboards.
- Automate safe inventory refresh from live servers while keeping secrets out of git.
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