Structural document checks only. They do not run, test or approve anything; no scenario was executed and no DG approval exists.
Validation results
Exactly what was checked
Links (note links and relative file links, offline), counts and IDs (84 scenarios, 25 decisions, 13 service gates, 12 steps), scenario text against the source data shipped in 10-Sources/tdd-bundle, step structure and dependency table, wording rules (no test-pass or approval claims, exactly-once, state diagram, audience, attribution), shipped tooling names, and the integrity of every file listed in 10-Sources/source-inventory.csv (size and SHA-256), including retained duplicates.
Not checked
Whether the content is correct or complete beyond the byte comparisons above; any application behaviour; DG policy; legal, privacy or security properties; room links inside verbatim exchange text (not resolvable offline).
Files: 258 · notes: 209 · note links checked: 2263 · relative file links checked: 171 · room links ignored: 6 · inventory rows verified: 58
| Result | Check | Detail |
|---|---|---|
| PASS | Wiki links resolve (every double-bracket target exists) | 2263 checked; broken: [] |
| PASS | Relative Markdown links resolve offline | 171 checked; broken: [] |
| PASS | No ambiguous note names | [] |
| PASS | Source case data: 40 + 24 + 20 = 84 unique IDs T01–T40, DG01–DG44 | |
| PASS | 84 scenario notes | found 84 |
| PASS | 25 decision notes Q01–Q25, all pending | |
| PASS | 13 service gate notes S01–S13 | |
| PASS | 12 implementation step notes | |
| PASS | Every scenario note carries its source Given/When/Then/Evidence/Decision verbatim (compared with the shipped source data) | [] |
| PASS | Every scenario status is Not executed | [] |
| PASS | Every step states prerequisites, changes, outputs/invariants, tests-first subset, deferred integration checks, follow-up verification and exit evidence | [] |
| PASS | Every scenario is the tests-first subject of exactly one primary step | unassigned [] multiple [] |
| PASS | Dependency and regression table lists all 84 scenarios | |
| PASS | Scenario index and traceability matrix list all 84 | |
| PASS | Step 11 rechecks integrated evidence on a named integrated build and keeps manual rehearsals out of the software payment gate | |
| PASS | Overview: manual service approval is a parallel pre-sale/data gate | |
| PASS | No authored note claims tests passed or DG approval (unnegated) | [] |
| PASS | No note attributes the review or an approval to Kedar | [] |
| PASS | Reviewer is recorded as workspace agent 0feb059240ac with limited independence; Kedar/DG approval pending | |
| PASS | Original independent review is shipped unchanged | |
| PASS | Step 07 exit evidence does not imply exactly-once delivery | |
| PASS | Opportunity-state diagram keeps V1 live during V2 review (no Approved-to-MaterialEdit transition) | |
| PASS | Start page and README state INTERNAL working vault, not DG-ready, no client-safe/redacted claim | |
| PASS | Engineer-day figures appear only in the INTERNAL estimate note (authored notes) | [] |
| PASS | Internal and historical notes carry INTERNAL banners | |
| PASS | Pilot commercial position is labelled INTERNAL and HISTORICAL / partly superseded, not a quote or current Balanced scope | |
| PASS | Front matter present on vault notes | [] |
| PASS | Key honesty statements present (not an NDA; verification not LinkedIn; no guaranteed deal; public-use consent) | |
| PASS | F01: no step treats an unapproved default as a prerequisite; each step separates scaffolding from decision-dependent behaviour blocked until DG chooses | [] |
| PASS | F02: T37 needs steps 02, 03, 09 and 11; T38 needs 07 and 10; Step 01 covers only configuration/harness subsets | |
| PASS | F03: Step 12 requires no application build and uses procedure/charter, consent-template, fixture, roles, date and observed result as evidence | |
| PASS | F04: no future check is labelled Verified/Partially verified; no duplicated step numbers in status cells | |
| PASS | Second review record is shipped unchanged and names reviewer 0feb059240ac | |
| PASS | Every documented command names a shipped script | scripts: [‘11-Tooling/validate_vault.py’]; missing: [] |
| PASS | Source inventory: every row matches the file bytes (size and SHA-256) | 58 rows; mismatches: [] |
| PASS | Source inventory: lists every shipped source file (including original notes in the TDD bundle) except the generated 10-Sources notes, and does not list itself | unlisted []; extra [] |
| PASS | Retained duplicates are byte-identical (reference documents vs originals vs manifest; TDD PDF/HTML) | [] |
| PASS | Architecture source ZIP and pilot commercial position are present and inventoried | |
| PASS | Restored review: mixed manual/software disposition and software-dependent matrix rows | |
| PASS | Restored review: overview separates manual evidence from named-build software evidence | |
| PASS | Restored review: A11 has explicit proposed coverage disposition linked in matrix and Step 11 | |
| PASS | Restored review: lineage identifies current vault revision 1.3 |
Self-test (deliberate corruption in a temporary copy)
- DETECTED: flipped one byte in a source PDF
- DETECTED: deleted a decision note (broken links, missing Q05)
- DETECTED: changed a scenario status to Passed
Re-run offline from the extracted vault: python 11-Tooling/validate_vault.py . --selftest (add --write to refresh this note).
The ZIP’s own SHA-256 is published outside the ZIP (in the delivery message), because a file cannot contain its own final hash.
See also Source-Inventory, Vault-Review-Record, Tooling-README.