Every compliance regime in Europe now demands the same impossible artifact: proof that a person actually read the document. Directors sign board packs under personal liability. Procurement teams attest to due diligence. Deployers of AI systems must ensure staff AI literacy and that instructions for use were actually followed.
The only artifact anyone has is a click-through: a checkbox that says "I have read and understood this." Everyone knows it proves nothing. The company carries the liability anyway.
The signature proves intent at one moment. Nothing in existence proves the twenty minutes before it. That is the missing layer, and this is it.
Diligence is the first workplace behavior that can be proven rather than asserted. Three products, one spine.
Engagement sealed as a hash chain. Minutes in the document, coverage of the document, exact version read, reader identity, all tamper-evident from a cryptographic root.
Rotating probes drawn from the document's own claim set, judged by an adversarial multi-model consensus engine. Five of seven independent models must agree on the verdict.
Multiple readers on one shared artifact. Each reading chain joined under a coordination seal: who worked, on which version, in what order.
The spine is the same GENESIS hash-chain protocol that powers the Proof of Operator registry and its public verification ledger.
This runs on the same server infrastructure as the Proof of Operator registry. The chain root is DIL-GENESIS. Nothing about your document leaves this page except its hash: the text itself is never stored or transmitted.
Demo seals one tick every 10 seconds. Production seals every 60 seconds. The demo interval is the only difference.
Proves: the labeled reader engaged with this exact document version for the sealed duration, reached the sealed coverage, and the record is tamper-evident from the DIL-GENESIS root. Anyone can verify it without an account, forever.
Does not prove: understanding. Understanding is a mental state; no honest product claims to measure it. Comprehension evidence comes from the probe layer, which seals witnessed responses, not thoughts. The seal is independent evidence of engagement. It is not a regulatory attestation and not legal advice.
Now: reading sessions, seals, public verification. What you just used.
Next: comprehension probes via the seven-witness consensus engine, rotating question pool, per-document claim sets.
Then: multi-party cooperation seals for teams, and a dedicated attestation device for signature ceremonies: hardware-grade observation evidence sealed next to the signature, specified per customer requirements.