How it works
Every statement on this site traces to a page of an issuer's PDF. This page shows how: what is recorded for each passage, a trace from a governance question to the source page, the checks run on every build, and what a new edition of a source would affect.
What is recorded
From source file to reading productEach layer keeps a reference to the one before it, so any digest or mapped passage can be followed back to a page of an issuer's PDF.
Trace a passage
From a governance question to the source pagePick a crosswalk theme and one of its mapped passages. The trace shows the question it answers, the digest passage, the source page and its file, and where else the passage is used.
The theme mappings were curated by hand, not inferred automatically; the build checks that each mapped passage still exists as recorded. A mapped passage is a reading aid, not evidence of compliance.
The same method for data
How this record maps to data lineageThe site keeps provenance for documents. The same chain, with the same checks, is what data lineage needs: each element on the left has a counterpart in a data estate.
| On this site, for documents | In a data estate | What it answers |
|---|---|---|
| Source PDF with a recorded fingerprint | Source system or file, with its schema version | Has the origin changed since we last relied on it? |
| PDF page | Table or dataset | Where does the content sit? |
| Digest passage with its paragraph label | Column or critical data element, with its definition and owner | What exactly are people relying on? |
| Mapped passage in the registry | Lineage link from a report field back to a source column | Can a reviewer follow it end to end? |
| Theme and the question it answers | Report, decision or control that uses the data | Why does this data matter? |
| Build check that stops on a mismatch | Data quality rule and reconciliation at each hop | Does a break show up at once? |
| "If a source changes", below | Change-impact assessment | How long to say what a change affects? |
What the site shows is the discipline, applied to documents and passages. It is not column-level or transaction-level lineage: that needs metadata harvested from the systems themselves and validated by the people who own the data.
Checks
Run on every build and before each releaseResults are counts, not scores. The build stops with a clear message if a source file's fingerprint or a mapped passage fails. Link and acceptance checks run before each release.
| Check | Result | What it means |
|---|
By source file
| Document | Pages | With text | Digest passages | Mapped | Fingerprint (first 12) | Checked |
|---|
If a source changes
IllustrationPick a source to see everything on this site that depends on it and would need rechecking against a new edition. Nothing has changed: this is the dependency trail. The Change desk shows the firm's side of a change.