← Week 6 portalMaster file in the engagement folder:
my-work/week-6/fund-level/lp-report/README-v2.md

D3: anonymised LP climate report (v2)

Portfolio edition: Kith Climate cohort case, fictional client. Final version. Nothing here has been sent: Investor Relations reviews the report before it reaches LPs (protocol LP Disclosure rule 4), and sending is Northwood's decision. The v1 draft files in this folder are kept as frozen; use the v2 files.

Files

FileWhat it is
northwood-lp-climate-report-v2.mdThe report in TCFD order: Basis of preparation (with the protocol's qualification sentence), Governance, Strategy, Risk management, Metrics and targets, aggregate data rows
content-index-<framework>-v2.csvFor IFRS S2, ESRS E1, SFDR PAI and EDCI: each requirement, whether this report meets it, and where
qa-result-v2.mdThe 22 QA checks on this version (18 pass, 4 not applicable, none fail)

The sign-off list and the company-level data table are internal. They are written to the case's out/ folder (internal-signoff-v2.md, internal-data-table-v2.md) and are never copied here. The builder refuses to copy if QA fails or if any company name, slug, first word or internal id appears in a copied file.

What changed from v1

How it is made

Figures and counts are tokens resolved from the data table, never typed: {{fig:<concept>}}, {{count:<concept>=<answer>}}, {{range:<concept>}}, {{row:<id>}}. The narrative is a reviewed file (my-work/week-6/pipeline/narrative-v2.json); descriptors are in my-work/week-6/pipeline/descriptors-v1.csv (a Fund I portfolio company, four; a Fund II portfolio company, six; minimum group size 3). Where a fund roll-up row exists the report uses it and does not add the company rows to it (QA Q22). By-fund rows are fund-only concepts named in the settings, so they are never summed with company rows. The Scope 3 and PCAF method is my-work/week-6/fund-level/library/methodology/scope3-pcaf-method-v1.md.

Re-run next year (no Kith)

Follow my-work/week-6/fund-level/rerun-note-v2.md: intake, engine, applicability, QA, then my-work/week-6/pipeline/build-d3-v1.py. Edit the narrative only in the narrative file; change a descriptor only with the group-size rule in mind (QA Q21 checks it); set the report date in the manifest.

What the report says plainly, and what remains open