Technical documentation
Ten briefs, one per module. Each says what the module does, against which threats, who is responsible for what, and — less commonly — what it does not yet guarantee.
These briefs describe the conceptual operation communicated publicly. They replace neither an API specification, nor a cryptographic analysis, nor an independent security audit. Each brief carries its own « Points to confirm before integration » section, and that section is deliberate: documentation that pretends to be a specification wastes the time of the team integrating it.
01 · Seal Standard
Point-in-time verification of a person associated with an organisation using a live code renewed every 60 seconds.
Read the brief →02 · Seal Sequential
Continuity-of-presence evidence based on successive surprise checks, without GPS or cameras.
Read the brief →03 · Seal Badge and domain protection
Public authentication of an official website using a live seal and a six-digit code bound to the displayed domain.
Read the brief →04 · Multi person authorisation and data protection
Adaptive control of sensitive operations requiring simultaneous codes from two to five verified people.
Read the brief →05 · The Vault and encrypted archives
Continuously encrypted archive vault whose opening requires multi-person authorisation and a client-held share.
Read the brief →06 · Document and invoice verification
Local fingerprint verification of a document to confirm its sealing and declared provenance before a sensitive action.
Read the brief →07 · Seal Media
Evidence of who published an audio or video work and verification of its integrity, including after platform re-encoding.
Read the brief →08 · Sealed ticketing
Dynamic tickets designed to limit duplication, support offline admission checks and govern resale.
Read the brief →09 · Attested erasure
Make a person permanently unreadable in retained records, without deleting a row, and issue an attestation a third party can verify.
Read the brief →10 · Email verification
Verify an email without clicking: a recipient-bound code, a secret only the recipient holds, a single possible verification, and the email’s signature compared in the recipient’s browser.
Read the brief →Briefs are served in the languages where they are COMPLETE, and in French otherwise. A language is added only once all nine briefs exist in it: a half-translated brief is worse than one honestly left in French.
