Document hidden capabilities — the learning proposal platform and the governed loop

Several powerful capabilities exist but are effectively invisible: if they are not documented, they are neither known nor used.

Scope

• The learning proposal platform: how runs generate skill, rule and knowledge proposals; the approval, immutable activation and canary flow; and how later runs consume approved artifacts.
• Receipts and the integrity chain: what a receipt proves and where to find it.
• The security agent: its read-only report and the trusted issue-projection model.
• The doctor: what it checks and how to read a verdict.
• Lanes and gates: one conceptual page mapping issue → architect → approval → builder → review → merge → outcome.

Audience-first: write for a team adopting the platform, not for its authors. Feed real onboarding questions from new adopters back into these pages.

Acceptance

• Each capability above has a page reachable from the docs navigation.
• The learning proposal flow is demonstrated with screenshots from a real run.

Start by locating the documentation navigation and reviewing a real run that demonstrates the learning proposal flow. Map the requested capabilities into audience-focused pages, make each page reachable from navigation, and verify that the proposal flow includes screenshots from that run.