CVN-N001-EK-S01 — Test strategy¶
Story artifact required by ADR-0101. S01's deliverable is a document (rules + charter), so "test" here means validating the governance artifacts — completeness, consistency, and absence of loopholes — plus specifying the enforcement tests that downstream Stories must implement when the registries and gates become code.
1. What is under test in S01¶
Not code — the ADR adr/0102 + charter draft. Validation = (a) the artifacts satisfy the plan's
acceptance criteria,
(b) they are internally consistent with the architecture, and (c) they contain no wording
that reopens a closed loophole.
2. S01 validation table (checks runnable now)¶
| # | Check | How | Pass criterion |
|---|---|---|---|
| V1 | All content in English | review + grep | no French in ADR/charter body |
| V2 | ADR is instance-free | review/grep ADR | no defi_top5/ATR-H4/GBT in the durable rules |
| V3 | Charter has no quantitative value | review charter | every number is a placeholder with a source Story |
| V4 | Every placeholder names source + lock authority | charter table | 1:1 mapping, no blanks |
| V5 | Every anti-snooping rule has an enforcement consequence | cross-check ADR ↔ architecture §9 | no rule without an enforcement point |
| V6 | No "free/budget-free" retest wording | grep ADR + charter | 0 occurrences except explicit prohibitions |
| V7 | Final-holdout policy + violation consequence present | review | matches architecture §4.4 |
| V8 | Killed-tuple gate is blocking + material-equivalence defined | review | matches architecture §4.2 |
| V9 | Verdict taxonomy complete; INFEASIBLE next-actions constrained | review | matches architecture §5 |
| V10 | ADR Accepted / charter Draft; standalone adr/0102 + catalogue entry |
review | status + file location correct |
| V11 | Risk-owner veto blocking + scope defined | review | matches architecture §7 |
| V12 | Docs build | mkdocs build --strict |
green, no orphan, tables render |
| V13 | Design validation | committee plan_review |
PASSED (Meeting #269) ✅ |
V1–V12 are the S01 implementation acceptance gate; V13 is already satisfied for the plan.
3. Enforcement tests to implement downstream (specified here, built later)¶
The architecture's contracts become automated tests when the registries/gates are code (S03/S04+). This Story specifies them so they are not forgotten:
| Future test | Owner Story | Asserts |
|---|---|---|
| Tuple-schema completeness | S04 | a tuple missing any §4.1 field is rejected at registration |
| Killed-tuple blocking | S04 | a materially-equivalent tuple is rejected unless a recorded reopening condition holds |
| Holdout single-touch | S04 | a second holdout access invalidates the verdict |
| FDR ledger accounting | S04 | every test appends; budget exhaustion blocks further tests |
| Phase-order enforcement | S04 | a downstream phase cannot start before its entry condition |
| Charter immutability | S03 | a locked charter cannot be edited without a recorded re-lock |
| Risk-owner veto blocking | S03 | no lock/run without the risk-owner signature |
E_econ_min ≠ E_pred_min |
S02 | the two thresholds are separate fields and tested at Phase 4 vs Phase 2 respectively |
4. Non-applicable¶
Performance/load/integration testing is N/A for S01 (no runtime code). Rationale recorded per ADR-0101 Invariant 3; reviewer to accept. Such tests attach to the runtime/execution stories (S04+).
5. Definition of test-done (S01)¶
V1–V12 pass and are evidenced in the implementation PR; the enforcement-test table (§3) is carried into the S02/S03/S04 plans so each contract has an owner.