Repos
Every repository under governance (offline fixtures) — its autonomy level, which labs vote on it, and how it is authorized. Connecting a new repo starts in Setup.
AgenticMaterialism
AutonomyAuto-merge + freshness lane
Voting labsoperations · strategic · critical
Authorizationcloud routines via claude.ai GitHub app
Fact-only diffs auto-merge with citations after council vote; structural changes go to PR. Changes reach the operator's machine on the next daily pull.
Revolution
AutonomyPR-only (substrate maintenance)
Voting labsoperations · strategic · critical
Authorizationcloud routines via claude.ai GitHub app
Weekly drift scan (models, pricing, docs) → tests → 21-seat vote → pull request. The operator holds the merge button.
quorum
Autonomyoperator-only (no board yet)
Voting labs—
AuthorizationGitHub Actions OIDC → Azure
No board attached. Deploys via OIDC-authenticated GitHub Actions; governance can be attached via Setup.
Authorization modelhow agents get write access
Cloud routines → repos
Activeclaude.ai GitHub app grant, scoped to the repos each routine clones
GitHub Actions → Azure
ActiveOIDC workload-identity federation — no stored keys anywhere
Spine API → live repo sync
Pending operatorfine-grained PAT (read-only, single repo) as an ACA secret — replaces the baked snapshot
Customer repo connect
RoadmapGitHub App install flow with per-repo permissions — the productized path
Verified
Destroy → recreate cycle proven on this stack (Aug 16).The full infra can be torn down and rebuilt from the repo alone — governance includes the platform itself.