Use this matrix to prove that the draft covers the behaviors a clean-room implementer must achieve. Keep one row per capability; do not hide gaps inside broad section summaries.
Status legend
| Status |
Meaning |
Action |
covered |
Evidence and draft text cover the capability. |
Keep mapped claims and examples current. |
partial |
Capability is real but conditional, limited, or missing an edge case. |
State the limit or escalate before normative wording. |
blocked |
Required capability is not yet supported by evidence, prose, or examples. |
Reopen the earliest faulty artifact. |
scoped-out |
Intentionally excluded from the current packet. |
Record the exclusion and residual risk. |
Capability matrix
| Capability ID |
Artifact |
Capability |
Implementer task |
Claim Refs |
Example Refs |
Evidence Refs |
Status |
Gap / Escalation |
CAP-0001 |
<draft-or-packet> |
<capability> |
<what the implementer must be able to do> |
CLM-0001 |
EX-0001 |
SRC-0001 |
blocked |
<gap-or-esc-id> |
Coverage summary by section
| Section |
Required Capabilities |
Covered |
Partial |
Blocked |
Scoped Out |
Notes |
<section> |
0 |
0 |
0 |
0 |
0 |
<notes> |
Exit checks
| Check |
Required Result |
Actual Result |
Notes |
| Every required implementer task has at least one matrix row. |
Yes |
<pass/fail> |
<notes> |
| Every matrix row points to claim evidence or an explicit escalation. |
Yes |
<pass/fail> |
<notes> |
No blocked capability is silently treated as covered in public prose. |
Yes |
<pass/fail> |
<notes> |