OMEGA · replay challenge

Replay challenge

A refund was committed six weeks ago. An auditor is not asking whether it ran. They are asking whether you can replay who allowed it, what evidence was on hand, and whether the record has been changed since.

Live seal check

This runs in your browser. It recomputes the record's SHA-256 content hash over the RFC 8785 canonical form and compares it to the stored seal, the same record and hash as omega-demo/examples/refund-escalation.json. Editing any field changes the recomputed hash, so it no longer matches.

omega-record/2026-05-14/cs-agent-refund-1187442

Authority: Sarah Okafor, Senior Customer Operations Manager (badge ops-2218), Tier C escalation. Autonomous limit £2,500.
Evidence: Order O-2026-04471 valued £4,820; three photographs; channel count and output gain inconsistent with the order specification; 30-day quality-assurance window applies.
Expected outcome: Full £4,820 refund to the original payment method, return collection booked, £120 goodwill credit, settlement in 3-5 business days.
Confirmation: Identity verified by SSO plus hardware key; a signed approval token was issued and consumed once at commit.
Traceability: Sealed with the record's SHA-256 content hash. Recomputing it shows whether the stored record still matches what was committed.

Stored seal e747c3fdcb29…

Recomputed recomputing…

Recomputing the hash in your browser…

Worked example (JavaScript disabled). The record's committed seal is e747c3fdcb29…. Recomputing SHA-256 over its canonical form reproduces that value: the record is intact. Editing authority.limit from £2,500 to £10,000 and recomputing yields b2e3c3e7d1af…. A different hash. The edit cannot be hidden: the recomputed fingerprint no longer matches the seal.

What replay surfaces

Six weeks later an auditor asks five questions. A typical log answers only the first, and only barely.

Who approved this? The authority field names the approver, role and limit.
Show the evidence. The evidence considered at commit time, reviewed independently of the agent.
Was approval required? The confirmation field records the one-time token and the gate.
What outcome was expected? The expectation field, written down before the action ran.
Has the record changed? The seal check above answers this cryptographically.

OMEGA does not establish that the decision was correct. It preserves the context required to replay and challenge it.

Back to OMEGA