docs(traceability): render requirement→test matrix (#303/SR-44 visibility half)#308
Merged
Conversation
…lity half) The SR→test/proof mapping lives in traceability.yaml's `verification-status:` block, which rivet does NOT ingest into its trace graph (those fields are outside the requirement schema), so `rivet matrix`/`trace` cannot show it. This script renders it: per requirement, the tests/proofs that verify it and the (self-asserted) status — surfacing the mapping that was invisible (the original "I see requirements but not the test mapping" concern). docs/verification-matrix.md (generated): 41 requirements — 10 verified, 6 implemented, 24 partial, 1 not-verified. The 24 `partial` are loud on purpose (a test exists but doesn't fully discharge the requirement). VISIBILITY half of #303/SR-44. The ENFORCEMENT half (typed `verifies` links in the rivet graph) still needs the v0.36 traceability-model decision. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
LS-N verification gate✅ 57/57 approved LS entries verified
Approved Failed LS entries(none) Missing regression tests(none) Updated automatically by |
This was referenced Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Surfaces the requirement→test/proof mapping that was previously invisible.
Why: the SR→test mapping lives in
traceability.yaml'sverification-status:block, which rivet does not ingest into its trace graph (those fields are outside the requirement schema). Sorivet matrix/tracecan't show it — answering the standing "I see requirements but not the test mapping" concern (#303).What:
scripts/gen-verification-matrix.py— renders the block to markdown (re-runnable).docs/verification-matrix.md(generated) — per-requirement: tests (verifies), proofs, status. 41 reqs: 10 verified · 6 implemented · 24 partial · 1 not-verified. The 24partialare loud on purpose.Scope: the visibility half of #303/SR-44. The enforcement half — typed
verifieslinks in the rivet graph — still needs the v0.36 traceability-model decision (ASPICE migration vs custom test type vs stay-generic) and is not in this PR. Docs/tooling only; no Tier-5, no safety-trace structural change.Refs #303, SR-44.