Attestations
A sign-off is a decision, and the platform treats it like one. Every attestation records who signed, what they were looking at, and when, sealed on the hash-chained ledger. A year later you can reconstruct exactly what the signer saw on the day they signed, and that is the difference between an attestation and a checkbox.
Attestation campaigns run by CDE, report, control, or policy, on whatever cadence each obligation demands: quarterly, annual, or event-driven.
Each attestation captures a sealed reference to the evidence in front of the signer at the moment of signing, so what they saw is on the record.
Lapsed and overdue attestations show as lapsed. Nothing stays green on memory, because absence is failure.
Delegation and escalation keep the trail intact: who was asked, who actually signed, and who was skipped and why are all recorded.
Pick any date and you can reconstruct who had attested to what, with the state of the evidence at that moment.
If the underlying evidence degrades after signing, through a lineage break or a failed quality check, the attestation is flagged for re-affirmation instead of left standing.
Schedule
Campaigns run on the cadence each obligation requires, with signers drawn from the ownership registry.
Present
The signer sees the live evidence, and a sealed reference to exactly what they saw is captured with the signature.
Seal
The sign-off lands on the hash-chained ledger, where it can be superseded but never edited.
Watch
Lapses and evidence changes flag automatically, so a stale attestation never passes as current.
“Who signed off on this number, and what did they see when they signed?”
Every attestation records the signer, the time, and a sealed reference to the exact evidence in front of them at the moment of signing. You can reconstruct that view a year later, because it lives on the hash-chained ledger.
“Which attestations are overdue right now?”
Lapsed and overdue attestations show as lapsed automatically, because nothing stays green on memory. Absence is failure, so the overdue list is always current, across every campaign by CDE, report, control, or policy.
“Can you prove this was attested before the filing date?”
Yes. The sign-off is sealed on the hash-chained ledger at the moment of signing, where it can be superseded but never edited. Pick the filing date and reconstruct who had attested to what, with the evidence as it stood at that moment.
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.