Dashboard Lineage Audit

Every number on a trading dashboard implies a chain: a component rendered it, a loader fetched it, an artifact stored it, a publisher wrote it, a computation produced it. On most desks nobody has ever walked that chain end to end — the dashboard’s numbers were checked by looking plausible. The Dashboard Lineage Audit is a service engagement that walks the chain for every number on the glass, and reports what it finds in a vocabulary that includes the finding most audits are too polite to name: FABRICATED.

We did not invent this method for clients. We invented it for ourselves, and we have executed it twice on our own cockpit. Both passes caught real fabrications — hardcoded statistics presented as computed values, and telemetry generated from random numbers rather than from the system it claimed to describe. A method that has never caught anything is a ritual; this one has caught our own.

What it does

• A full inventory of the display surface. Every number, gauge, and status indicator on the audited UI is enumerated. Nothing is sampled, because fabrications do not distribute themselves conveniently across a sample.
• A five-hop trace per number. Each displayed figure is traced through component → loader → artifact → publisher → computation. The trace terminates either at a real computation over real inputs, or at the point where the chain breaks — and the break point is itself the finding.
• Findings with honest statuses. Each number receives a status. VERIFIED means the chain closed. The statuses short of that are stated plainly, and FABRICATED — a value that is hardcoded, generated, or otherwise not produced by the computation it claims — is a first-class outcome, never softened into “requires further review”.
• The deliverable: a lineage ledger. The engagement produces a per-number ledger of the traced chain and its status — a document your risk function, your allocator, or your next audit can pick up and re-walk. Findings from client engagements: NOT YET PUBLISHED, and individual client results stay private to the client.

What it does not do

It does not certify a dashboard whose chains it could not close. A number whose lineage terminates in a broken hop is reported as exactly that — unverifiable — not granted the benefit of the doubt because the rest of the panel checked out. And the audit does not issue a clean bill of health as a summary judgment: the deliverable is the per-number ledger, and the dashboard is as honest as its worst-traced number.

Who it is for

Desks that inherited a dashboard nobody fully understands; teams whose UIs were built quickly, by contractors, or by agents; allocators and risk functions who want “where does this number come from?” answered with a trace instead of an assurance.