This guide is for whoever at Northwood updates the work next quarter. The short version: replace the data, set a new report date, run the numbered scripts in order, and rebuild the pages. Every script refuses to overwrite a file, so each run goes in its own new folder. The full run order, with what each script reads and writes, follows.
What this covers. The five deliverables: the connected dataset (D1), the financial exposure model (D2), the extended data (D3), the materiality matrix (D4) and the initiative ranking with the one-page view (D5), plus the explorer: one page that puts the exposures and the initiatives in one ranked value-creation backlog, with the cost, effort and payback of acting beside the exposure. Version 12 replaced the earlier client deck and portal with the explorer; version 18 adds the revision layer and rebuilds the deck, explorer, exposure model, matrix and initiatives page, data book, re-run guide and portal as one delivery set. Versions 8 and 9 add the ten-company rebuild: all ten portfolio companies run through one protocol (documented inputs for the six companies outside the priority four, an evidence sweep of the data room, the customer carbon-data requirement as rule R12, and the cost of responding to it as a labelled estimate). Version 9 applied the findings of its review and version 10 settles the findings left after it: the company inputs behind the exposure model sit in two tables you edit, not in code; the physical-weather lines follow one set of rules (a loss someone else bore is not the company's, a company that reports no loss is shown as reporting none, an unreported loss is derived only from the company's own files); the sweep reads its recorded judgments and its percentage ranges as ranges; every benchmark behind the cost estimate has its address and the date it was checked; and a held-out check of the sweep's reading is shipped with its labels. Everything is rebuilt by 24 Python scripts run in a fixed order. Nothing needs a Kith tool, a Kith account or a Kith person. You need Python 3 (the delivered run used 3.9.6), the two add-on packages in requirements-v1.txt, openpyxl and xlrd (python3 -m pip install -r requirements-v1.txt; they read Excel files) and your own data room.
The revision layer (steps 23 and 24). After the explorer, the work was revised and finished as one delivery set for the reader at Northwood: all ten companies, the priority four marked, no exposure line left without a figure or a stated reason, one exit timing per company, and one portal. Step 23 writes a new version of the ten-company data layer (connected dataset v4, exposure lines v6, matrix v5, ranking v6) in which gaps are estimated from published benchmarks or from the portfolio's own observed figures, marked grade C, and each estimate is cross-checked in revision-validation-v1.csv. Step 24 builds the client deck, the explorer, the exposure model, the matrix and initiatives page, the data book, the re-run guide and the portal, with copies of the data files. The method for the revision is in charter-v7-addendum-v1.md; every outside figure used is in revision-benchmarks-v1.csv with its source, date and sentence.
What you receive (the full list, with a fingerprint for each file, is handover-list-v17.csv in this folder):
requirements-v1.txt, the exact package versions used, and setup-rerun-folder-v3.py, which sets up a fresh folder for a run;my-work/week-4/pipeline/, the two helper modules the evidence sweep imports (sweep_logic_v6.py, sweep_logic_v8.py), the five helper modules the page builders import (w4_model_v1.py, w4_pages_v1.py, w4_content_v1.py, w4_deck_v1.py, w4_process_v1.py), and kit.py, the small helper that stamps each run into a log and refuses to overwrite an existing file;my-work/week-4/reference-data/ (EIA prices, FRED rates, FEMA disaster declarations, the IAC energy-saving database), each with its source and download date in the assumptions register;assumptions-register-v3.csv (A-01 onward: value, unit, source, date, who owns it, which deliverable uses it, grade A to C) g2-assumptions-v1.csv (the inputs behind the Clearview fleet estimate, labelled as an estimate) and assumptions-register-additions-v7.csv (A-44 and A-45, the day rate and effort days behind the cost-to-respond estimate; step 21 appends them to the register from step 19 to make assumptions-register-v10.csv);charter-v7.md (the rules for probability, dollar impact, bands and ranking, and for the customer carbon-data requirement, the one protocol for all ten, the evidence sweep, the cost to respond and the explorer), data-map-v1.md (which data-room file supplies each input), g2-contract-v1.md (the shape of every output file), rule-r12-v2.md (the customer carbon-data requirement rule) and d5-response-cost-method-v2.md with its inputs response-cost-inputs-v3.csv and response-cost-components-v1.csv (the components, effort ranges and day rate behind the cost estimate), and the two tables behind the exposure model: d2-source-inputs-v1.csv (every company input with its file, line and expected text) and d2-company-rubric-v1.csv (the customer-line judgments per company);sweep-commissioning-v7.csv (the tests the sweep logic passed and the fingerprints of that logic) and sweep-judgments-v4.csv (the 42 paragraphs a reviewer has judged; the sweep leaves them out of its queue). The harness that recommissions the sweep logic if you change it is test-sweep-v7.py (with test-sweep-v1.py). The held-out check of the sweep's reading is sweep-holdout-sheet-v1.csv (12 paragraphs), sweep-holdout-key-v1.csv (the script's reading), sweep-holdout-agent-v1.csv (the review agent's blind reading), sweep-holdout-labelled-v1.csv (the labels) and sweep-holdout-score-v1.csv (the comparison) and sweep-qualexist-queue-v1.csv (the twelve paragraphs the qualified-existence rule queued), with build-holdout-batch-v1.py and score-holdout-v1.py to repeat it;revision-benchmarks-v1.csv (every published figure used for an estimate, with its source, vintage and quotation), charter-v7-addendum-v1.md (the rules the revision rests on), explorer-owners-v6.csv (owners and first moves, reworded for three newly sized measures) and process-snapshot-v3.json (a reading of how the work was gated and reviewed, shown in the back-end note; it describes this delivery and is not recomputed);my-work/week-4/leave-behind/ui/ (the look of the explorer, from the Week 3 client deck);my-work/... at the paths in handover-list-v17.csv, and your data room at data/northwood-capital/.python3 my-work/week-4/leave-behind/setup-rerun-folder-v3.py <received-folder> <new-folder> --report-date YYYY-MM-DD. Use a new folder for every run (it refuses a non-empty one, and the scripts never overwrite). The setup script copies every file the scripts need, but not the delivered outputs, which stay in the received folder to compare against. It creates the empty output folders, adds the marker file CLAUDE.md (the scripts look for it to find the project root), links your data room, puts the decisions behind the delivered files (id, date, summary, decision and rationale; 129 rows, including the two pre-registration decisions the extended-data script checks) in record/decision-log-v1.csv, and writes the settings file as my-work/week-4/manifest-v1.json.manifest-v1.json is the only place the report date lives; no script has it typed in. It also holds the input pins: the fingerprint (SHA-256) of every data-room, Week 3 and reference file the work was built on. Step 2 of the run order stops if a pinned file no longer matches. Version 4 of the settings file also pins the data-room files the evidence sweep and the explorer read (including Northwood's firm overview). Use the delivered date only to reproduce the delivered numbers exactly.Run each from the new folder: python3 my-work/week-4/pipeline/<script>. Each script stops with a plain message if a table header, a period label or a cross-check no longer matches, and none will overwrite a file that exists (see "Updating" below).
| # | Script | Reads | Writes |
|---|---|---|---|
| 1 | profile-data-room-v1.py | data room | methodology/data-room-profile-v1.csv |
| 2 | extract-register-values-v5.py | reference data, data room, Week 3 ledger | methodology/register-extraction-v5.csv (register values re-read from source, for comparison) |
| 3 | build-connected-dataset-v3.py | data room finance files, Week 3 carbon, register, step 2 (stops if register N disagrees with the report date) | D1 fund-level/connected-dataset-v1.csv and its lineage file |
| 4 | build-event-table-v1.py | company questionnaires | fund-level/pooled-event-table-v1.csv |
| 5 | build-fema-frequency-v1.py | FEMA declarations, facility locations | fema-distinct-disasters-v1.csv, fema-frequency-v1.csv |
| 6 | build-simulated-baseline-v1.py | facility locations, Harvest Ridge questionnaire, the two pre-registration decisions | D3 simulated-extended-data-v1.csv (every value labelled simulated) |
| 7 | build-exposure-model-v1.py | steps 3 to 5, Week 3 exposure, register | D2 exposure-lines-v1.csv, reverse-stress-v1.csv, exposure-model-v1.html |
| 8 | recompute-sterling-v1.py | Sterling source files, steps 4 to 7 | recompute-sterling-v1.csv (an independent re-calculation of Sterling's numbers) |
| 9 | scan-data-room-measures-v1.py | data room | methodology/d5-scan-files-v1.csv, d5-scan-hits-v1.csv (which companies state a cost-and-saving energy measure) |
| 10 | build-d5-initiatives-v1a.py | questionnaires, EIA, register, step 7 | first-pass initiatives table (kept only because step 12 reads it) |
| 11 | build-d5-ranking-v1a.py | step 10 | first-pass ranking (same reason) |
| 12 | build-g2-view-v1.py | steps 7, 10, 11 | D4 matrix d4-matrix-v1.csv, d4-aggregates-v1.csv (the other files it writes are first-pass and superseded) |
| 13 | build-d5-initiatives-v3.py | questionnaires, EIA fuel prices, register, step 7 | d5-initiatives-v2.csv and methodology/g2-assumptions-v1.csv |
| 14 | build-d5-ranking-v3.py | step 13, register | D5 d5-ranking-v2.csv, d5-sensitivities-v2.csv |
| 15 | build-g2-view-v3.py | steps 7, 12, 13, 14 | d4-summary-v1.csv, g2-lineage-v3.csv, the one-page view and the four company packs |
| 16 | extract-six-values-v2.py | the data room (six companies' acquisition, board, budget, status and plan files), the spine company table | methodology/register-extraction-six-v2.csv (documented exit timing and gross margin for the six companies outside the priority four, each with its cited line) |
| 17 | build-connected-dataset-v5.py | the spine tables, Week 3 carbon, registers, steps 2 and 16 | D1, ten companies fund-level/connected-dataset-v3.csv and connected-dataset-lineage-v3.csv (a basis column: spine, register or documented) |
| 18 | sweep-portfolio-v8.py | the whole portfolio folder of the data room, sweep-commissioning-v7.csv, sweep-judgments-v4.csv, sweep_logic_v6.py, sweep_logic_v8.py | the evidence sweep: sweep-findings-v8.csv (stated values), sweep-qualitative-v8.csv, sweep-review-queue-v8.csv (paragraphs that still need a person's reading: empty in the delivered run), sweep-qualitative-coverage-v8.csv. Stops if the sweep logic no longer matches its commissioning record |
| 19 | build-exposure-model-v5.py | steps 4, 7 and 17, d2-source-inputs-v1.csv, d2-company-rubric-v1.csv, EIA prices, Week 3 exposure, register | D2, ten companies fund-level/exposure-lines-v5.csv and exposure-summary-v5.csv, late-exit-sensitivity-v2.csv (Patriot at its late exit), methodology/d2-inputs-v4.csv (every cited input, re-opened) and assumptions-register-v9.csv |
| 20 | build-d4-d5-v4.py | steps 13, 14, 17 and 19, questionnaires, the Ridgeline plan | D4 and D5, ten companies d4-matrix-v4.csv, d4-summary-v4.csv, d5-initiatives-v5.csv, d5-ranking-v5.csv, d5-value-protected-v5.csv |
| 21 | build-response-cost-v3.py | step 20, response-cost-inputs-v3.csv, response-cost-components-v1.csv, assumptions-register-additions-v7.csv, step 19 register | fund-level/d5-value-protected-v6.csv (cost to respond beside value protected, payback in days) and methodology/assumptions-register-v10.csv |
| 22 | build-explorer-v6.py | steps 16 to 21 (the D1, D2, D4 and D5 files), explorer-inputs-v1.csv, explorer-owners-v5.csv, explorer-page-corrections-v1.csv, the page assets, the data room lines those files cite | The explorer fund-level/explorer-v6.html (one self-contained page, data embedded) and explorer-v6-lineage-v1.csv (every figure to its source file and column) |
| 23 | build-revision-layer-v1.py | steps 16 to 22 (D1, D2, D4, D5 files and the simulated baseline), d2-source-inputs-v1.csv, revision-benchmarks-v1.csv, the DOE industrial assessment database and the EIA reference files, the data-room lines the estimates cite | The revision data layer fund-level/connected-dataset-v4.csv and connected-dataset-lineage-v4.csv, exposure-lines-v6.csv and exposure-summary-v6.csv, d4-matrix-v5.csv, d4-summary-v5.csv, d5-initiatives-v6.csv, d5-ranking-v6.csv, and methodology/revision-validation-v1.csv (the cross-check of each estimate) |
| 24 | build-w4-final-v1.py | step 23, the explorer builder build-explorer-v6.py (its script is read for the page logic), explorer-owners-v6.csv, explorer-inputs-v1.csv, explorer-page-corrections-v1.csv, process-snapshot-v3.json, this note, revision-benchmarks-v1.csv, the page assets | The delivery set in fund-level/delivery-v1/: 01-client-deck-v3.html, 02-explorer-v8.html, 03-exposure-model-v3.html, 04-materiality-and-initiatives-v5.html, 05-data-book-v2.html, 06-re-run-guide-v3.html, the portal kith-week4-portal-v2.html, delivery-lineage-v1.csv and a data/ folder of the data files |
Steps 16 to 21 are the ten-company rebuild and are the current set for D1, D2, D4 and D5. Steps 1 to 15 still run because the rebuild reads some of their outputs (the initiatives and ranking tables of steps 13 and 14, the pooled event table in step 4, the exposure lines of step 7). Step 22 builds the explorer from the outputs of steps 16 to 21. Steps 23 and 24 are the current set for everything the reader at Northwood receives: they supersede the explorer of step 22 with 02-explorer-v8.html, built on the revision data layer.
portco_kpis.csv and portfolio_companies.csv, the questionnaires, facility locations, supplier file, budgets) and the Week 3 carbon outputs. Each lineage file lists, for every figure, the file, line, period and grade it came from, so you can see what to swap. After swapping a file, update its pin: run shasum -a 256 <file> and put the result in inputs.sources in manifest-v1.json.reference-data/, re-pin each (shasum -a 256 <file>, then inputs.sources in manifest-v1.json), edit the typed constants for any FEMA file (see the next section), then update the matching rows in the assumptions register (value, source, source_date, period). External data carries its own vintage; it is not "stale" because it is older than the report date.g2-assumptions-v1.csv, grade C). The ranking is rerun at 8, 10 and 15 percent; a changed premium can change the order.report_date with the setup script. Remaining hold N depends on it: after step 2 of the run order, compare the N rows in methodology/register-extraction-v5.csv with row A-37 of the register and edit A-37 to match; step 3 stops until they agree (within 0.015). Then work through the typed periods below.build-simulated-baseline-v1.py.build-explorer-v6.py, not generated; the opening sentence and the totals are computed from the book selected. Read the page against the new numbers before it goes anywhere. The builder stops if the company totals it re-sums stop equalling the signed summary, if a cited line no longer carries its words, or if an owner row matches no backlog item.methodology/d2-source-inputs-v1.csv holds every input behind the exposure model: company, field, value, unit, the data-room file and line, and the text that must be on that line. For a new period, replace the rows; step 19 re-opens each line and stops if the text is not there. methodology/d2-company-rubric-v1.csv holds the judgments for the customer carbon-data line, per company: revenue type (earns today or hope to win), likelihood level (none, some, clear), whether the company can comply, and its share of revenue where it gives one.insurance_premium_YYYY and insurance_premium_2026_expected, energy_kwh and energy_therms, energy_cost_reported_usd, customer_requirement_revenue_exposed (with the share rows for Trident), own_event_property_damage_usd, the Keystone sessions_* and revenue rows, event_no_loss_statement, customer_statement_*, and late_exit_midpoint_date (the date used for the Patriot late-exit sensitivity).extract-six-values-v2.py lines 59 to 140 (acquisition dates of the six, and for every exit window and gross margin the file, line and expected text; the acquisition dates are asserted against the company master); build-d4-d5-v4.py from line 103 (the list of company-identified measures for the six: company, file, line, expected text) and the line numbers of Ridgeline's plan table (its figures are read from the file); and the client's severity and likelihood scales (SEV, PRI, BANDS) near the top of build-exposure-model-v5.py and build-d4-d5-v4.py. These are rules and citations, not company results, but they are in code.energy_cost_reported_usd rows; if you replace the Week 3 outputs, update those rows.sweep-judgments-v4.csv. A paragraph the logic cannot place appears in sweep-review-queue-v8.csv with its proposed reading. A person reads it and records one row (para_id, answer, direction, value, note, judged_by, judged_date, basis) in a copy of the judgments file saved under a new version name; change the name on the line that reads it in sweep-portfolio-v8.py and re-run. The delivered queue is empty.sweep_logic_v6.py or sweep_logic_v8.py) step 18 stops, because the logic's fingerprints no longer match the commissioning record. Run test-sweep-v7.py (it also runs test-sweep-v1.py); first give its output file a new version name, because the scripts never overwrite, then change the commissioning file name in sweep-portfolio-v8.py.response-cost-inputs-v3.csv, response-cost-components-v1.csv): the day rate and effort ranges are Kith's estimate, graded C. Replace them with your own rates and quotes.explorer-owners-v5.csv has one row per backlog item: decision-holder, delivery lead, first move and Northwood contact, each with a basis tag (company file, adjacent role, or Kith proposal) and the file, line and words that support it. Replace the roles and moves with your own; the builder re-opens every cited line and stops if the words are not there, and it stops if an item has no row.explorer-inputs-v1.csv carries the facts the explorer takes from the data room beyond the data layer (a company's term-loan balance and maturity). Replace the rows and the cited lines for a new period.explorer-page-corrections-v1.csv lists two small corrections to text the signed data layer carries, each with its evidence line. Delete a row once the data layer is fixed; the builder stops if a correction no longer finds its text.revision-benchmarks-v1.csv holds each outside figure: the Marsh US casualty rate change, the RIMS cost of risk, the McKinsey disruption interval and loss share, the EPA fleet mpg, the EV kilowatt-hours per mile and price gap, the FHWA mileage, and the Patriot exit midpoint. Refresh each row from its source before a new run; the script stops if a row lacks a source, vintage or retrieval date.d2-source-inputs-v1.csv). None is typed.build-revision-layer-v1.py, then re-run steps 23 and 24; the cross-check file shows what each one affects.w4_content_v1.py, w4_deck_v1.py and w4_process_v1.py; the figures beside them are computed, and build-w4-final-v1.py stops if a claim in the wording stops being true of the data. Read each page against the new numbers before passing it on.For the delivered run, handover-list-v17.csv lists a fingerprint (SHA-256) for every received file and every delivered output. A re-run from the same inputs and the same report_date rebuilds all 77 delivered outputs byte for byte; if one differs, an input has changed. To fingerprint a file: shasum -a 256 <file>.
Some labels and counts are typed into the scripts. A new quarter needs a person to check each against the new data; the scripts fail loudly where a count or window no longer matches.
| Script | What is typed | Change when |
|---|---|---|
build-connected-dataset-v3.py | carbon period "CY2025 (as of 2025-12-31)" and finance period "LTM to 2026-01-31" (line 37); "FY2025 actual" labels (lines 145 to 146); "spine as of 2026-01-31" (line 152) | the carbon year or the financial year-end moves; the script stops if the files lack the labels |
extract-register-values-v5.py | "FY2025 actual" labels (lines 161, 165); Sterling and Clearview exit windows in the note text (line 183) | a company's exit plan or the year changes |
build-fema-frequency-v1.py | FEMA window 2016-02-07 to 2026-02-06, 10 years (line 30); expected 141 rows and 96 distinct disasters (lines 48 to 49) | you download a newer FEMA file: set the window, the row count and the disaster count to the new file |
recompute-sterling-v1.py | the same FEMA window (line 59) | with the FEMA window |
build-exposure-model-v1.py | "LTM to 2026-01-31" and "CY2025" in the line notes (lines 151, 159, 171, 203, 235, 267) | with the financial year-end |
build-g2-view-v1.py | the same EBITDA period in the page note (line 176) | with the financial year-end |
extract-six-values-v2.py | the six companies' acquisition dates (lines 59 to 60); "FY2025 actual (period exception)" labels for NovaCare and Pinnacle gross margin (lines 95, 103) | a company is acquired or sold, or the financial year moves |
build-connected-dataset-v5.py | the same carbon period "CY2025 (as of 2025-12-31)" and finance period "LTM to 2026-01-31" (line 42); "FY2025 actual" gross-margin labels for Meridian (lines 157 to 158); "spine as of 2026-01-31" (line 171) | the carbon year or the financial year-end moves |
build-exposure-model-v5.py | "LTM to 2026-01-31" in the EBITDA period (line 152) and "CY2025" and "LTM to 2026-01-31" in the line periods (lines 227 to 381); the period text in the register rows A-38 to A-43 and A-46 to A-50 from line 466 | with the financial year-end and the carbon year |
build-explorer-v6.py | the note "twelve months to January 31, 2026" and "Q4 2025" in the page notes; the default thresholds 15 and 35 percent; company display names | with the financial year-end, the data-room date or Northwood's own scale |
build-revision-layer-v1.py | the EBITDA period "LTM to 2026-01-31" in the line notes and the water-price window "FY2016 to 2026" in one line period (lines 155, 191, 213, 251, 280, 340, 349, 574) | with the financial year-end and the vintage of the industrial assessment file |
build-w4-final-v1.py | the data-room date "January 31, 2026" and "Q4 2025" in the explorer's page notes (lines 92, 268, 274) | with the data-room date or the financial year-end |
w4_content_v1.py | the data-room date "January 31, 2026" in the delivery pages' notes (lines 136, 240, 255, 319) | with the data-room date or the financial year-end |
w4_model_v1.py | the data-room date and "Q4 2025" in the forcing-date wording (lines 191, 235, 239) | with the data-room date or the financial year-end |
test-sweep-v7.py | a judged date in a seeded test fixture (line 115) | never: it is a test fixture, not data; change it only if you change the fixture |
assumptions-register-v3.csv says the questionnaire-implied Harvest Ridge electricity price is about 15.8 cents per kWh. It should read about 13.5 cents per kWh (the A-19 electricity cost divided by the questionnaire kWh), nearly double the EIA industrial average of 7.13. No model value used 15.8: D5 computes the price from A-19 and the kWh, and the stored EIA ratio of 0.5274 matches 13.5. The register stays as delivered and this entry is the correction.reference-data/ and pinned, and the charter (rule R8) makes it a cross-check only. No cross-check rows were produced: all five quantified measures come from company questionnaires, so none is benchmarked against IAC. Adding that benchmark is a new step, not a fix to an existing one.d5-response-cost-method-v2.md; one could not be fetched directly (its figures were read from a search excerpt), two statements in version 1 that the pages did not carry were removed, and there is no independent project-fee check (A-44, grade C).d2-source-inputs-v1.csv) and that an independent check re-opens again; no check ties them to the sweep's findings (a logged decision).sweep-holdout-score-v1.csv): the agent matched 11 of 12 answers, the script 8 of 12. The script read a leading "No" as "no" where the codebook reads an informal or sized lesser fact as "partial" (items 2, 4 and 7). Sweep logic v8 now queues such answers; twelve paragraphs were queued (sweep-qualexist-queue-v1.csv) and all are judged in sweep-judgments-v4.csv (nine partial, three no). The labels for the twelve held-out items are the builder's proposals approved by the owner and the rule was written after the three misses were seen, so the held-out batch is now in-sample; the nine other paragraphs the rule queued, of which six came back partial, are the out-of-sample evidence. A check re-derives from the qualitative rows that no unjudged "no" has a sized lesser fact after its first sentence.d2-inputs-v4.csv is a byte copy of d2-source-inputs-v1.csv, written when step 19 re-opened and asserted every cited line; it adds no evidence beyond the input table.It does not make the judgments above for you, and it does not read documents it was not pointed at. A company with no stated cost-and-saving measure shows "not quantified", never a filled-in number. Figures marked grade C or PROXY stay marked until a company supplies its own number.
This note is for whoever audits or maintains the work. It shows what each part of the process does and how the parts link, without opening a single script. Counts are the record as at 11 October 2026, before the final (G7) freeze.
The charter's 16 rules say what must be true: units, scenarios, bands, missing data, ranking, simulated data and the customer data requirement. Nothing on a page departs from them unless a dated decision says so.
24 run-order steps (87 script versions are kept) build every file from the data room and the reference data. They stop with a plain message if an input, header or period no longer matches, and never overwrite.
Gate checks re-derive figures from source and fail on a defect; each is proved with seeded failures before it is trusted (33 test files). A check that passes is stronger evidence than a reviewer's opinion.
Reviewer agents, each read-only and given one question, work from the same packet: Evidence review, Audience read, Presentation review, Method review, Process review. They raise findings; they cannot change a file.
180 decisions are logged with the date and channel, and the owner's words wherever the owner decided. A builder's proposal is marked proposed until the owner ratifies it.
289 entries are linked to one another, so an earlier entry cannot be altered without breaking the chain. 259 journal entries say what was done, why, and what was left open.
Each gate froze the files it covered. Where a check failed or a reviewer raised a must-fix finding, the work went back, was versioned and re-run. Dates are when each gate was frozen; findings are those raised at that gate.
| Gate | Closed | Checks | Reviewers | Must-fix raised | Should-fix raised | Files frozen |
|---|---|---|---|---|---|---|
| G0 Foundations | 2026-10-09 | 10 | Process review | 22 | 43 | 78 |
| G1 Data and models | 2026-10-09 | 25 | Method review, Evidence review | 4 | 9 | 100 |
| G2 Outputs | 2026-10-09 | 20 | Evidence review, Presentation review, Audience read | 5 | 26 | 104 |
| G3 Close | 2026-10-09 | 14 | Process review | 8 | 6 | 103 |
| G4 Rebuild | 2026-10-10 | 22 | Evidence review, Method review, Process review | 9 | 24 | 250 |
| G5 Explorer | 2026-10-11 | 10 | Evidence review, Audience read | 3 | 17 | 176 |
| G6 Handover | 2026-10-11 | 12 | Process review | 3 | 6 | 175 |
| G7 Revision and final delivery | signed and frozen 11 October 2026 | 13 | Method review, Evidence review, Audience read, Process review | 38 findings, all fixed | 52 | |
Gate G7 covers the revision of this delivery set after G6: the decisions logged after G6, a delivery check with seeded failures, and a reviewer round on method, evidence, audience and process before it was frozen. What was not reviewed: there was no Presentation-lane read of the final pages; the counts in this note are the record at the date shown and are not recomputed; and fixes made after the G7 round were re-run through the delivery check and the re-run test, not re-reviewed.
Reviewers worked from the same packet, read-only, with one question each. These are examples of what they caught, in plain terms.
Caught: A five-year forward hold was applied to every company, but Sterling is already 5.7 years in and Meridian exits in the first quarter of 2027.
Done: Hold years are now set per company from its documented exit plan.
Caught: Clearview's weather events were counted over one year when the company lists three, which overstated how likely they are.
Done: The window is now the three years the company reports.
Caught: Ridgeline's growth-plan investment was stated in its own plan, but the model said it was not stated.
Done: Quantified from the plan's own investment table and shown as a company plan, not capitalised.
Caught: Ridgeline's weather impact had been taken as a property owner's cost, not Ridgeline's own.
Done: Carried as Ridgeline's own small event; the owner-borne losses are shown as context.
Caught: Pinnacle's largest event had combined two storms, lifting its severity band.
Done: Apportioned by closure days; the combined figure is shown only as an upper bound.
Caught: Exit dates were labelled 'planned exit' though they are Kith's model, not a Northwood plan.
Done: Relabelled 'modelled exit', with floors marked as the earliest modelled date.
Caught: Paybacks in days and exit values read as sized benefits though they rest on a what-if.
Done: Labelled 'if the half-lost case happens' and 'what-if, not likelihood-weighted'.
Caught: The decision list shipped to the client was missing most decisions its own files cite.
Done: Rebuilt from the record so every cited decision is present.