Northwood Capital · Carbon inventory · Evidence view

Start from any number and see exactly where it came from

Every figure in the inventory is built from calculation lines. Each line cites the company's submitted row, the published emission factor, the rules that applied and the decisions behind them. Everything below is read from the project record, and the page re-checks the arithmetic and the audit trail in your browser.

Start from a number

Click any figure (tonnes of CO2e, 2025) to see the calculation lines behind it. Click a line to see its evidence.

The site list column marks companies where more than half of base emissions sit on rows that the company's own records cannot test, so their roster could not be checked at site level (rule R1, as amended by D-R1-A1).

What this view proves, and what it does not

Look up a dashboard number

Every number on the dashboard has a figure ID, or is a company, scope or scenario you can search for. Type part of an ID or a word, such as "exposure" or "sterling". Stored values are kept to six decimal places, so a recomputation agrees to within a few millionths of a tonne.

Decisions and findings

Every judgment that shapes a number is a numbered decision with its reasons, who made it, what would overturn it and what it governs. Every reviewer finding is recorded with how it was settled.

Reviewer findings

Audit trail

Every script run is written to a log in which each entry carries a fingerprint of the one before. Changing any past entry breaks every fingerprint after it. At each gate the log's fingerprint was recorded outside the log when it was signed.

Check the whole log now

This recomputes every fingerprint from the first entry in this page.

Portfolio edition: one local folder path in log entry 215 was shortened to its file name for privacy. That entry therefore no longer recomputes, so the check stops there; the entries before it recompute as recorded.

Sources and limits

Outside data the inventory relies on

Each file's fingerprint is recorded so a changed file is detectable.

Known limits, stated plainly

The notes, verified

Check it yourself, without Kith

Everything above can be re-checked outside this page, using only what is left behind.

  1. Fingerprint of the ledger. The calculation ledger file calculation-ledger-v2.csv has SHA-256 065fdf73646bb4aa0c9faa8e6dce81a0d7aed0814a47629dfbfae41126c9a9cd; the dashboard figure table g34-figures-v6.csv has 45f0634bb51317057762a067a13e6ac6b3933a761d4d1effb009d7ad4812caa1.
  2. The audit log. The log's newest entry when this page was built was number 223, fingerprint b017632796fb043804aac94cd36ec415f4978a0dc535cea9f3a7c885154daf35. From the pipeline folder: python3 -c "import pipeline_common as pc; print(pc.verify_chain())"
  3. Reproduce the figures. The re-run note, step 2, repeats the calculation on the unchanged data and compares all 320 ledger figures; they match.
  4. Reference data. python3 verify-reference-pack-v1.py confirms every outside file is unchanged.
  5. This page. It was built by build-evidence-view-v5.py and verified by a separately written check, check-evidence-view-v1.py, which rebuilds the same facts from the source files.