Record
What the format captures about a decision prepared with AI: the project, the report, the follow-up and the decision, and the proof. An image: a sealed envelope; inside, the project, the report and what you did with it; on the flap, the issuer’s seal.
Record file
The complete record, texts included, in a JSON file. It is kept on the computer or in a shared folder on the organisation’s server. A record is checked on its record file, never on a PDF alone.
Follow-up
What the person who signs checked themselves, the open questions and who owns them, their decision and its conditions. Filled in by a person, never by a model.
Signer’s signature
The signature drawn or typed on screen, in the follow-up: a simple electronic signature, under the declared name. Planned: sign-in with the organisation’s account; an advanced or qualified signature from a recognised provider.
Proof
The part of the record that lets it be checked: fingerprint, seal, signature, time stamp.
Fingerprint
A code computed from the texts (SHA-256). Changing a single character gives a different fingerprint. It lets you confirm a text you already have, without containing it.
Seal
The code the issuer computes over the ID and the fingerprint with its secret key. The issuer is the one who checks it.
Issuer signature
The Ed25519 signature the issuer computes over the same message as the seal, with its private key. Anyone can check it with the published public key, without going through the issuer.
Public key
The publishable part of the signing key. riftveil.ai’s public keys are published in three places: riftveil.ai/keys.json, GitHub and attestscope.ai. No key is removed from the list; a compromised key stays on it, marked and dated.
Final document
The document that actually goes out after the decision: a memo, a contract, a deck. The follow-up can keep the document’s fingerprint, computed on the signer’s device; the document itself is never sent.
Riftveil time stamp
The date and time from the riftveil.ai clock, sealed and signed with the record.
Qualified time stamp
The date and time signed by a qualified trust service provider of the European Union (an RFC 3161 token). At Riftveil: an option planned with AttestScope traceability. An organisation will also be able to use its own authority (planned).
Third-party time stamp
The date and time signed by an authority independent of the issuer: a qualified time stamp in the European Union, or a time stamp issued by a recognised provider in your country (in the United States, for example). At Riftveil: an option planned with AttestScope traceability.
Register entry
The record without the texts (project, context, report). Planned for version 0.2.
Organisation register
Where an organisation will keep its register entries, on its own servers. Planned for version 0.2; until then, a shared folder on its server.
Audit trail
All the records of an organisation.
Log
The public log planned for version 0.2, which can only be appended to, with no text or name.