Canon Indexes¶
Purpose¶
This page is the curated entrypoint into approved Ledger canon.
It does not try to mirror every file under docs/.
It points to the highest-signal documents by surface so readers can reach approved truth faster.
How To Use This Page¶
- start with the canon surface you actually need
- use the
README.mdfor that surface first - then read the smallest document set that answers the current question
If the answer is not yet canon, step back into research/ or records/ deliberately.
Canon Surface Map¶
flowchart TD
A["Approved canon"] --> B["Strategy"]
A --> C["Product"]
A --> D["Architecture"]
A --> E["Company"]
A --> F["Operating system"]
F --> F1["Models"]
F --> F2["Playbooks"]
F --> F3["Templates"]
Strategy Canon¶
| Start here | Why it matters | High-signal documents |
|---|---|---|
| docs/strategy/README.md | current strategic framing | ORBITRA_OVERVIEW.md, VISION_AND_SCOPE.md |
Use this when:
- you need current company or product framing
- you are deciding whether work fits present scope
- you need the stable baseline before reading broader research strategy notes
Product Canon¶
| Start here | Why it matters | High-signal documents |
|---|---|---|
| docs/product/README.md | active implementation truth | PHASE_1_WORKING_MODEL.md |
Use this when:
- you need the current shell and Phase 1 lock
- you need to know what implementation truth is active right now
- you need the boundary between current shell and longer-term architecture work
Architecture Canon¶
| Start here | Why it matters | High-signal documents |
|---|---|---|
| docs/architecture/README.md | durable repo and system structure | REPO_AND_SERVICE_MAP.md |
Use this when:
- you need the current bounded repo and service map
- you are orienting around cross-repo structure
- you need architecture baseline rather than research exploration
Company Canon¶
| Start here | Why it matters | High-signal documents |
|---|---|---|
| docs/company/README.md | approved company doctrine surface | SOFTWARE_AGENCY_ORG_CHART_AND_REPORTING_MODEL.md, CLIENT_SERVICES_OPERATING_MODEL.md, DELIVERY_OPERATING_MODEL_FOR_AGENCY_EXECUTION.md, PRODUCT_STUDIO_AND_INTERNAL_PRODUCTS_OPERATING_MODEL.md, PEOPLE_AND_CAPABILITY_OPERATING_MODEL.md, FINANCE_AND_COMPENSATION_OPERATING_MODEL.md |
Use this when:
- you need approved company-level doctrine
- you want to avoid mistaking company research for approved company canon
Operating-System Canon¶
| Start here | Why it matters | High-signal documents |
|---|---|---|
| docs/operating-system/README.md | human-agent execution canon | overview/GOVERNANCE_AND_OPERATING_MODEL.md, models/TASK_ROUTING_AND_LIFECYCLE_MODEL.md, models/ISSUE_GOVERNANCE_AND_NORMALIZATION_MODEL.md, models/REVIEW_AND_ACCEPTANCE_MODEL.md, playbooks/REVIEW_AND_CLOSEOUT_PLAYBOOK.md |
Use this when:
- you are starting or routing governed work
- you need lifecycle, review, closeout, or supervision doctrine
- you need execution truth rather than architecture vision
Related Control Surfaces¶
These are not part of docs/ canon, but they are high-signal surfaces that operators usually need next.
| Surface | Start here | Why it matters |
|---|---|---|
| governance | governance/GOVERNANCE-INDEX.md | enforceable repo rules and conventions |
| metadata | meta/task-routing.yaml, meta/issue-governance.yaml | machine-readable routing and issue truth |
| specs | specs/ORB-REGISTRY.md | versioned contract and registry surface |
| templates | templates/README.md | canonical reusable issue, PR, RFC, ADR, spec, and closeout forms |
| records | records/decisions/ACTIVE_DECISION_LOG.md | accepted decision memory and active direction |
Canon Versus Research Rule¶
If this page does not give you an approved answer directly:
- confirm the canon surface README first
- then move into the matching
research/surface - treat research as reference truth, not implementation truth, unless canon explicitly says otherwise