Falls & lapses
This capability is arriving. When an attestation expires or a required run goes missing, the certification falls on its own, and this view says exactly what fell, when, and why, with the path to putting it right.
Every fall listed with its cause: expired attestation, missing run, failed control.
Absence is failure: a missing input never reads as a pass.
Each fall carries its remediation path and owner.
Detect
The derivation notices the missing or stale input and drops the state on its own.
Repair
The fall opens work, and the state recovers only when the evidence does.
“Can someone quietly restore a fallen certification?”
No. It recovers when the evidence recovers, through the same derivation that dropped it, and both movements are on the record.
“Will this page us at 2am?”
Falls route to the workflows you already run. Urgency follows the materiality tiering your policy sets, not a blanket alarm.
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.