REMISHow REMIS seals an event.
A minimal pipeline : six steps, one cryptographic primitive per step, no payload storage.
The steps, in this order, without exception.
The order is material : reversing a step breaks the evidentiary chain. This is why REMIS enforces a fixed, versioned and auditable pipeline.
Capture at source
A lightweight hook captures the event at the moment it occurs, within the operator's system. No rewriting, no deferral.
Versioned taxonomy
The event is qualified against a published, versioned and tamper-evident taxonomy. Meaning is fixed together with the data.
Cryptographic fingerprint
A fingerprint (SHA-2/3) is computed over a canonical representation of the event and its qualification.
Digital signature
Ed25519 signature by a key bound to a certificate identifying the operator. Authorship is established (art. 1366).
Qualified eIDAS TSA
A qualified timestamping authority affixes an enforceable date, independent of the operator.
Proof package
The whole is consolidated into a package.remis artifact, archivable and verifiable offline.
We seal the fingerprint, never the data.
The business data stays with the operator. Only its cryptographic fingerprint transits - sufficient to prove integrity and qualification, insufficient to reconstruct the payload. This is an architectural choice, not a configuration option.
in business event (stays internal) ↓ canonical representation hash sha256:9d8c2…f31a ↓ signature sig ed25519:64A0F3…7BA1 ↓ eIDAS-Q timestamping tsa 2026-05-21T14:32:09Z ↓ sealing out package.remis (12 KB)
The operator can thus prove that an event of a given type took place on a given date, without ever publishing the content.
A third party verifies offline, without accessing the source system.
The package is self-contained. Regulator, auditor, judge : each has a standard command and a public-key ring to verify integrity, anteriority and authenticity.