Week 5 · Physical climate risk

Portfolio edition: Kith Climate cohort case, fictional client. Report date 16 October 2026.

Hand-off and re-run

Small grey tags are references to the project record: A- an assumption (assumption ledger, page 08), DR- a data request (page 11), D-5- a decision, DP- a data-plan item.

Re-running the physical-risk analysis next quarter (v1)

This note is for an analyst at Northwood with no Kith access. It covers what to update, the order to run the scripts in, and how to check the result. The method is in my-work/week-5/fund-level/leave-behind/method-note-v1.md.

What you need

What to update each quarter

InputWhereWhy it matters
Revenue, EBITDA, debt, exit multipledata/northwood-capital/_data/spine/csv/portfolio_companies.csv and portco_financials.csvEvery dollar figure, the covenant headroom and the exit-value lines
Exit timingmy-work/week-4/fund-level/exposure-lines-v6.csv (n_years)Hold years, lever timing
Report dateManifest setting report_date (set with kit_tools.py bump-manifest)Hold periods. While it is unset, outputs are marked provisional
Premiums and insurance schedulesData request DR-1; then the premium history in my-work/week-4/methodology/d2-inputs-v4.csv and the programme rules A-17 to A-21 in my-work/week-5/methodology/engine-parameters-v1.csvInsured, retained and renewal split; recurring premium cost
New weather events the companies reportAdd a row to my-work/week-5/methodology/calibration-events-v1.csv with its file, line and verbatim quoteKeeps the calibration current
Answers to data requestsmy-work/week-5/fund-level/leave-behind/data/data-requests-v2.md here; the live list is my-work/week-5/fund-level/data-requests-v2.mdNarrows the ranges
Assumptionsmy-work/week-5/methodology/engine-parameters-v1.csv (numbers) and assumptions-register-v2.csv (basis)Change a number only with a recorded decision, and keep low ≤ central ≤ high by loss

Public hazard data only needs re-fetching when its source publishes a new release. The vintages are in my-work/week-5/fund-level/inputs/fetched/fetch-log-v1.csv, climate-fetch-log-v1.csv and downloads-log-v1.csv; the last of these lists each download's link and sha256.

Order of the scripts

All scripts are in my-work/week-5/pipeline/.

StepScriptWrites
1fetch-public-sources-v2.py, fetch-climate-cmra-v1.py (only for a new data release)my-work/week-5/fund-level/inputs/fetched/
2extract-downloads-v1.py, extract-hazus-valuation-v1.py (only after new downloads; pass the download folders as arguments, and run with python3 -I)NOAA, Hazus and FAST extracts
3build-join-key-map-v1.py, build-site-flood-status-v2.pyJoin keys, flood status by site
4build-synthesis-v1.pySite exposure, supplier layers, logic notes
5build-register-v1.pyVulnerability register, regions, plausibility
6engine-v1.pyGrid, presets, stack, expected loss, register v2 (ranked)
7replay-calibration-v1.pyCalibration replay and groups
8levers-v1.pyLever results, captive flag, Target B screen
9sensitivity-v1.pymy-work/week-5/fund-level/leave-behind/sensitivity-v1.csv
10build-dashboard-v1.pymy-work/week-5/fund-level/physical-risk-dashboard-v1.html and its data file
11build-leave-behind-v1.pyAssumption ledger, reference-data index, data/ copies, lineage

If only financials, the report date or assumptions changed, start at step 6.

How to check the result

  1. Run the checks for the Results gate:
    python3 my-work/framework/kernel-v2/kit_tools.py --week-dir my-work/week-5 check --gate G2 --dry

These checks matter most:

  1. Run the seeded tests:
    python3 my-work/week-5/pipeline/test-calibration-band-v1.py
    python3 my-work/week-5/pipeline/test-page-checks-v1.py

Each must end "ALL SEEDS CAUGHT". They show the checks still catch a corrupted input or output.

  1. Open the page in a browser. Check that the draft banner is gone once the report date is set.
  2. Record what changed in the week's record:
    • each run cited in a journal entry;
    • each decision in the decision log, in the decider's words;
    • each in-place edit in my-work/week-5/record/changelog-v1.csv.

When a check fails

Provenance: rendered for reading from my-work/week-5/fund-level/leave-behind/re-run-note-v1.md (frozen at G2/G3 on 16 October 2026; sha256 4662c80fb25a), with the portfolio wording fixes listed in the portfolio changelog. Raw file: data/re-run-note-v1.md.