Reference docs are machine-facing or contract-facing documents that should be stable enough to test, lint, or link from implementation.
Current groups:
- Reference contracts
- Protocol contracts
- Extensions and capabilities: outcome contracts, provider registration, extension packaging, readiness, and lifecycle boundaries.
- Project skill delivery: release-owned, project-local skill discovery and managed-copy lifecycle.
High-traffic read paths:
- agent_scoped_evidence_ledger_v0: thin, per-agent evidence chronology used before replan or handoff.