Repository reference
Requirements traceability
Connect stable product-requirement families to their implementation, scoped verification, and the exact acceptance evidence still missing.
This is a family-level traceability matrix. A passing unit test proves only its named behavior and never upgrades an entire enterprise requirement to complete.
Use this reference when
- Reviewing whether a product requirement is implemented, previewed, designed, or blocked.
- Planning acceptance work across tenancy, MCP, policy, identity, sessions, approvals, observability, and deployment.
- Preventing UI, schema, or plugin scaffolding from being mistaken for end-to-end proof.
What it covers
Requirement families
Stable requirement ranges mapped to primary implementation, verification evidence, and required completion evidence.
Mandatory scenarios
The eight end-to-end enterprise scenarios, their current partial proof, and what a credible acceptance run must add.
Evidence locations
Where tests, deployment assets, implementation status, security gates, and known blockers are maintained.
Read the full repository reference
This page is a discovery map, not a shortened replacement for the maintained source. The complete reference includes exact tables, commands, boundaries, and cross-links in docs/requirements-traceability.md.
Open the complete Markdown reference ↗