A cryptographic fingerprint for the moment an official decision gets made. One engine, reusable for any certificate, licence, or approval that starts with a form.
An officer reviews a form and signs off. That single moment is the entire basis for everything the certificate later claims.
Weeks or years on, a college, an employer, or a court needs to know: is this genuine, and who actually approved it?
In most systems, nothing independent stops that record from being quietly edited after the fact, or proves that it wasn't.
Nothing here replaces the officer, the form, or the department's own system. Touchstone fingerprints the one moment that matters, so that fingerprint can be checked by anyone, at any time after, without trusting a database alone.
Two genuinely different certificate types already run on the exact same, unmodified core. The second one was added without touching the fingerprinting, the tamper detection, or the human-decision rule at all. That's the point: any process with a form, a decision, and a need for later proof can plug in the same way: a licence, a permit, an inspection sign-off, a training record.
The system can flag something for a reviewer to check. It cannot approve, reject, or issue anything on its own. That limit is enforced in code, not left to a workflow habit.
Only a cryptographic fingerprint of the decision is stored, never the personal data itself, so tampering is detectable without creating a new place sensitive information can leak from.
A verifier sees status and the handful of fields the issuer chose to make public, never a date of birth, address, or other detail behind that decision.
Touchstone sits next to the system already in place. No rip-and-replace, no new system of record, no retraining an entire department.
Simplified previews, not screenshots. The interactive prototype is still in development.
A live, interactive prototype is being built. This page will carry a link to it once it's ready to share.
In development