Reference

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.
• PostgreSQL authority service admission v0: opt-in authentication, tenant authorization, and restore-incarnation rotation.

High-traffic read paths:

• agent_scoped_evidence_ledger_v0: thin, per-agent evidence chronology used before replan or handoff.
• Goal acceptance observations: bounded, read-only Goal acceptance gaps, pending gates, and historical progress read from run_history.goals[].acceptance_observation, and the Dashboard entry that renders them. Partial observations never certify acceptance.