Auditable records of human decisions

Most organizations can already reconstruct what a system did. Far fewer can reconstruct what a human decided, and be believed when they describe it. An evidence trail for human authorization is what closes that distance.

What a record has to hold

• The action, described in the plain language the person actually saw — not an internal transaction code.
• The confirmation they gave, and the form it took.
• The time and context of that confirmation.
• The rules that were applied and who attested that the exchange took place as recorded.
• A form that can be checked later without trusting the system that stored it.

That last point is the one that changes the design. A record that can only be read back from the database that wrote it is an assertion. A record that a third party can independently examine is evidence.

Who might rely on it

• Dispute and complaints teams, who need to reconstruct a decision months later.
• Auditors and examiners, who ask how authorization was captured rather than whether policy exists.
• Risk and compliance functions, which set the thresholds at which confirmation is required.
• Counterparties, who need assurance about a record they did not create.

Constraints worth taking seriously

• Privacy minimisation — a record should hold what proves the authorization, not a copy of everything around it.
• Retention — evidence has a useful life, and a record kept past it becomes a liability.
• Portability — verification should not force every party into the same vendor relationship.
• Usability — a confirmation nobody genuinely read proves less than it appears to.

From timeless notarization to programmable trust: verification that's built into every digital interaction.

The notary analogy is useful precisely because it is modest. A notary does not decide whether a contract is wise, or whether a party should have signed. The notary attests to what happened at the moment of signing, and the record of that attestation outlives the conversation. Bringing that same modesty to software means building verification that stays in its lane and still holds up under examination.