PRD: add FR-78 per-requirement test-coverage map (reported, per-build, justified-SKIP≠gap)#122
Merged
Merged
Conversation
…, justified-SKIP≠gap) Adds FR-78 to the Verification section: for each landing TDD, throughline produces a verification-status map of that TDD's in-scope requirements — each classified pinned / proposed / justified-no-surface / unverified-gap — that cannot read falsely-green. It is REPORTED for the human PR review (not an automatic flip-blocker; the FR-15 gates remain the auto-authority), scoped per-build (no retroactive whole-system audit), and distinguishes a justified no-observable-surface SKIP from a real gap (NFR-4 honesty). Closes the gap FR-15(a)/FR-23/FR-71 leave: FR-15(a) gates test-PRECEDES-impl (per-commit discipline, not per-requirement coverage); FR-23 states INTENDED observation points (pre-build design intent); FR-71 reports actual diff/scope, not per-requirement verification status. Non-goals added: a pre-build de-risking spike (considered, explicitly excluded — the build is the cheapest test for engineering design); the coverage map as a hard auto-gate or whole-system audit. Strictly WHAT (no format/location/which-gate/which- mechanism — those are /tdd-author's job). Cascade: none — FR-78 is purely additive (a new requirement). It needs a covering TDD via /tdd-author, but no existing TDD or accepted ADR becomes stale. Open assumptions & waivers: - redundant with FR-15(a)/FR-23/FR-71 — resolved: FR-78 is the falsifiable per-requirement POST-BUILD verification-status map those three leave uncovered (precedence-discipline / intended-plan / actual-diff-report respectively).
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
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.
Adds FR-78 to the Verification section: for each landing TDD, throughline produces a
verification-status map of that TDD's in-scope requirements — each classified pinned /
proposed / justified-no-surface / unverified-gap — that cannot read falsely-green. It
is REPORTED for the human PR review (not an automatic flip-blocker; the FR-15 gates
remain the auto-authority), scoped per-build (no retroactive whole-system audit), and
distinguishes a justified no-observable-surface SKIP from a real gap (NFR-4 honesty).
Closes the gap FR-15(a)/FR-23/FR-71 leave: FR-15(a) gates test-PRECEDES-impl
(per-commit discipline, not per-requirement coverage); FR-23 states INTENDED
observation points (pre-build design intent); FR-71 reports actual diff/scope, not
per-requirement verification status.
Non-goals added: a pre-build de-risking spike (considered, explicitly excluded — the
build is the cheapest test for engineering design); the coverage map as a hard
auto-gate or whole-system audit. Strictly WHAT (no format/location/which-gate/which-
mechanism — those are /tdd-author's job).
Cascade: none — FR-78 is purely additive (a new requirement). It needs a covering TDD
via /tdd-author, but no existing TDD or accepted ADR becomes stale.
Open assumptions & waivers:
per-requirement POST-BUILD verification-status map those three leave uncovered
(precedence-discipline / intended-plan / actual-diff-report respectively).