Record ids. D-6-n is a Week 6 decision, J-n a journal entry, F-0n a review finding, DR6-n a data request, A-n an assumption; all are in the engagement record.
Portfolio edition: Kith Climate cohort case, fictional client. In the case, this page is internal: it names companies. The LP report (D3) is the anonymised document. The v1 files in this folder are kept as frozen; use the v2 files.
| File | What it is |
|---|---|
master-register-v1.csv | The 32 disclosure concepts in four pillars, each linked by script to the framework requirements that need it. register-schema-v1.md explains the columns |
northwood-evidence-map-v2.csv | Concept by entity (ten companies and the fund): state (covered, partial, gap, none exists), the evidence, the data-table rows behind it, the basis (read, derived, not asked, decided) and the data request that would close the gap |
northwood-data-requests-v2.csv and .md | Sixteen requests to Northwood and its companies, each with who is asked and why it matters to EBITDA, deal risk or exit readiness. Nothing has been sent; Northwood decides which to send (D-6-60) |
northwood-coverage-matrix-v2.csv | Concepts against the four Tier 1 frameworks |
northwood-content-index-<framework>-v2.csv | For IFRS S2, ESRS E1, SFDR PAI and EDCI: every requirement, its status and where the report meets it |
northwood-filled-register-v2.csv | The engine's computed status per concept |
northwood-applicability--v2. | The screen: 104 entity-by-framework answers (yes, no, unknown, monitor) with the rules and missing facts behind each |
filled-register): 14 of 32 concepts read covered. The engine counts a narrative concept only when the LP report addresses it, and a figure concept only when the data table has a row for every company.my-work/week-6/pipeline/questionnaire-reads-v1.csv.my-work/week-6/fund-level/rerun-note-v2.md up to my-work/week-6/pipeline/build-d2-v1.py.my-work/week-6/pipeline/evidence-rules-v2.csv (one row per concept: the state and evidence for companies and for the fund, with the basis). Change a rule only with a recorded reason; a rule's state is overridden by data-table rows where they exist.my-work/week-6/fund-level/library/applicability/applicability-rules-v2.csv; framework facts and their verification are in library/standards/ and the verification log.The report date is the manifest setting (not typed anywhere). Data period is calendar 2025; revenue and the Scope 3 spend are LTM to 31 January 2026 (Week 3 rule R4). Each framework row carries its retrieval date; none is flagged stale unless its re-check date has passed.