Fictional scenarios.
Real seals.

Each record below was sealed on Verdict’s public sandbox and logged on Sigstore Rekor, a public log Verdict does not run. Open one, verify it in your browser, and read from the log when it existed. No company, person or transaction in them is real.

• Cyber insurance · claimsAn accounts-payable agent pays a lookalike vendorWhether the money left before anyone approved it, and in what order the insured, the triage system and the handler acted.verdict.systems/s/cyb-7730 · 3 records →
• Cyber · incident responseA helpdesk agent stops a social-engineering runWhen the attack was detected and when it was reported. Breach-notice clocks run from those moments.verdict.systems/s/inc-5528 · 2 records →
• Digital-asset custodyA multisig signer approves what the screen showedWhat the signer was shown at the moment of signing, fixed before any later dispute over the transaction.verdict.systems/s/cus-5118 · 1 record →
• Third-party riskA vendor's support agent exports more than the contract namesWhen the export happened, measured against the contract and the date the customer was told.verdict.systems/s/tprm-1013 · 1 record →
• Banking · consumer lendingA credit model's withdrawal goes to a lending officer firstThat a person reviewed the model's recommendation before any message went to the customer.verdict.systems/s/ln-30417 · 2 records →
• Life sciences · clinical trialsAn investigator overrules an AI pre-screenThat the investigator's decision came before the consent visit, and on which version of the protocol.verdict.systems/s/trial-2210 · 2 records →

A sealed record proves its content has not changed since it was logged, and the log’s time proves when that was. It does not prove the event happened as described, or who made the record. What Verdict proves, and what it doesn’t →