Portfolio edition: Kith Climate cohort case, fictional client. In the case, this page is internal: the page and the pack name portfolio companies. Neither goes to LPs. Option B: a static page plus a pack Sarah loads into her own Claude. The v1 files in this folder (and the query-pack/ folder) are kept as frozen; use the v2 files.
| File | What it is |
|---|---|
northwood-climate-dashboard-v2.html | One self-contained page (about 44 KB, no external files): overview (now with Scope 3, financed emissions and the exposure by fund), companies, coverage and gaps, applicability, the 16 data requests, how to update, limits, framework verification dates. Opens in any browser; works on a phone |
dashboard-data-v2.json | Every number and text on the page. The page embeds this same JSON; nothing on the page is typed |
query-pack-v2/ | JSON files, index.json (what each holds) and CLAUDE.md (the rules for Sarah's Claude: answer only from the files, cite the row, never turn unknown into no, never say requests were sent, say "estimated" for the grade C Scope 3 figure, use names only for internal answers) |
check_dashboard.py | Eight checks that re-derive the page from the case files and compare |
my-work/week-6/fund-level/rerun-note-v2.md.python3 -I my-work/week-6/pipeline/build-d4-v1.py <repo-root> writes the JSON, the page and the pack. The page layout is my-work/week-6/pipeline/dashboard-template-v2.html; the pack rules are my-work/week-6/pipeline/query-pack-instructions-v2.md.python3 -I my-work/week-6/fund-level/dashboard/check_dashboard.py <repo-root> must print DASHBOARD PASS. python3 -I my-work/week-6/fund-level/tests/test_dashboard.py <repo-root> proves each check can fail.query-pack-v2 folder in Claude, as the project folder or as an attached folder, and ask questions.The pack includes the decision log and dispositions, so rebuild it after any new decision, or the clean re-run check will report a difference.