CDE hierarchy
A regulatory report line is rarely one field. It is a ratio built from inputs, which are built from other inputs, down to source columns in your systems. The hierarchy shows that whole tree for each CDE, with evidence at every level, so you can answer where a number came from at whatever depth the question is asked.
Each report line is fully decomposed, from the published figure through each intermediate calculation to the source columns underneath.
Evidence sits at every level: each parent-child link in the tree comes from parsed code and lineage, with the proof attached to the link.
Trust rolls up: standing at each level is derived from the levels below, so a weak input weakens everything above it, and nothing is set by hand.
Drill-down handles exam questions: start at the report line an examiner points to and walk to the exact source columns, with evidence at each hop.
Shared inputs are made visible: one source column feeding many report lines shows up once with all its dependents, so concentration risk in your data is plain to see.
A missing link shows as a break in the tree and is flagged as a finding rather than being papered over.
Decompose
Each CDE is broken into its inputs using parsed calculation logic and lineage.
Attach
Evidence is pinned to every link: the query, the pipeline, or the mapping that proves it.
Roll up
Trust standing at each level is computed from the levels beneath it.
Walk
Start from a report line or a source column and traverse the tree in either direction.
“Where did this number come from?”
Start at the published figure and walk down through each intermediate calculation to the exact source columns underneath, with evidence at every hop. Each link in the tree is proven by parsed code and lineage, so the answer holds at whatever depth the question is asked.
“If this source column goes bad, which report lines move?”
Traverse the tree upward from the source column and you see every report line that depends on it. Shared inputs appear once with all their dependents, so a column feeding many report lines is plain to see.
“How is this ratio actually calculated across systems?”
The hierarchy decomposes the ratio into its inputs using parsed calculation logic and lineage, level by level down to the source columns. Every parent-child link carries the query, pipeline, or mapping that proves it.
Start with proof, not a promise.
There are three ways in, and each one earns the next. You approve the exit criteria before we spend any more of your time or budget.
A 60-minute working session
Bring one report that is expensive to prove. We walk the mechanism against it. Nothing is required from your side.
A two-week guided sandbox
Your team works hands-on against a synthetic sample bank. It requires zero access to your systems and zero procurement.
A six-week proof on your systems
We use read-only metadata across five systems and one priority report, scored against criteria both sides sign first. The decision it produces is yours.