CDE identification
Keeping a CDE inventory complete is genuinely hard, because criticality lives in the code that feeds your reports. Here, candidate critical data elements are surfaced from evidence: the platform sees which fields actually feed your regulatory reports and material calculations, and it scores each one on how much rides on it. Your stewards make the final call on every promotion.
Candidate CDEs are surfaced from lineage: every field that feeds a regulatory report or a material model appears as a candidate, including fields no team has nominated yet.
Each candidate carries an evidence-backed criticality score covering which reports consume it, how many downstream calculations touch it, and where it sits in the flow.
Your existing CDE lists are imported as claims and checked against what the evidence shows, and both gaps and overreach are flagged for a decision.
A person decides every promotion: agents propose candidates, your stewards confirm or reject them, and each call is sealed on the ledger.
Fields the evidence says are critical but no one has yet nominated are brought forward early, so they enter the inventory before an examiner is the first to ask about them.
Every score is traceable to its inputs, so you can show an examiner why a field made the list and why a neighboring field did not.
Discover
Connectors read metadata from the systems behind your reports, and lineage identifies every field that feeds a regulatory report or material calculation. Only metadata is read, and nothing is copied.
Score
Each candidate is scored from the evidence: the reports that consume it, the reach of its downstream dependents, and the materiality of the use.
Review
Stewards confirm or reject each candidate through the decision door. The platform proposes, and a person decides.
Seal
Every promotion decision is sealed on the hash-chained ledger with the evidence that supported it.
“How do we know our CDE list is actually complete?”
Completeness is checked against lineage rather than asserted. Every field that feeds a regulatory report or material calculation surfaces as a candidate automatically, and your existing lists are reconciled against that evidence, so any gap or overreach is flagged for a steward's decision.
“Why is this field a CDE and that one not?”
Every criticality score is traceable to its inputs: the reports that consume the field, the downstream calculations that depend on it, and the materiality of that use. You can show an examiner exactly why one field made the list and a neighboring field did not.
“Who decided this element was critical, and on what basis?”
A named steward confirmed or rejected every promotion through the decision door, and each call is sealed on the hash-chained ledger together with the evidence that supported it. The record shows who decided, when they decided, and what they saw.
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.