Reference¶
Canonical specifications, contracts, and schemas. Use these to look up exact rules, field definitions, and constraints.
Authority¶
- Authority model — ownership matrix, MCP operations, approval statuses, identifier allocation, documentation hierarchy
- Integration contract — what Conductor may read, authorize, and emit; authority matrix; GitHub boundary
Roles and tools¶
- Roles and tooling — all 25 role definitions across 6 line groups, authorized pack scope schema
- Tooling map — tool boundaries, by-line production surfaces, forbidden uses
Contracts¶
- Stage contracts — catalog of all 40 stage contracts across 6 lines
- Plan bundle schema — plan-bundle.v1 format specification
- Compiler specification — 8-step compilation algorithm
- Corpus architecture — corpus structure, unit schema, proposal lifecycle
State¶
- Notion hierarchy — Initiatives → Workstreams → Deliverables, approximating Azure DevOps Agile
- State model — (archived) compiler-era 9-database schema
- Asset registry — (archived) compiler-era asset schema
Standards¶
- Standards — cross-cutting always-on rules: secrets, GitHub-first workflow
Security¶
- Privacy model — privacy classes, filtering rules, role-permission mapping
- Secret management — secret names vs values, resolution path, never-in-pack rule
- Socket activation — service type defaults, systemd socket rules, idle-cold posture