Page 15 of 15Traceability and QA

Resident question

How is this used and audited?

Answer so far

The workbook is one connected reasoning system, not fifteen independent dashboards. A reviewer can trace a Page 1 total backward to its source and an evidence item forward to every conclusion it affects.

The relationship to hold onto

Two-way traceability is the handoff test.

Backward tracePage 1 → Page 4 → Page 6 → engine → Page 5 → source.
Forward traceEvidence → assumption/readiness → schedule/cashflow → resident conclusion.
Independent reconstructionRules, contracts, checks, and history preserve institutional memory.

Current QA state

Twenty-four workbook structural assertions pass

Structure, blank safety, overlap control, terminal timing, chain integrity, readiness records, source contracts, and privacy checks pass. Results remain evidence-gated.

Operating boundary

The web app explains; Excel calculates

The web layer reads a bounded contract tied to the exact v0.7 hash. It does not refresh the source, mutate the workbook, or create a second calculation engine.

Resident resultPage 01
ComparisonPage 04
CashflowPage 06
InputPage 05
EvidenceSource contract

Protected support layers behind the journey

01Model Inputs
02Cashflow Event Ledger
03Economic Cash Flow
04Funding & Debt
05Terminal Position
06Sensitivity Engine
07Financial Dashboard
08Readiness Register
09Model Checks
10Source & Query Control
11Evidence Cache
24 / 24 structural checks passResults remain evidence-gated.
See the workbook connection and limits

Workbook binding: WMS Model Guide!A1:N54; WMS Model Checks!A1:I32

The 15 front sheets are followed by 11 protected support layers.

Every future update must retain source, as-of date, unit, evidence state, change reason, and release history.

Controlled baseline: v0.7, SHA-256 d35db6de8563ce17bd311f760ac14a607f35839e452d2865477dc067d405b6ff.

Open the full source, missingness, and calculation contract →