Interactive demo

Replay Challenge

Logs tell you what happened. The record shows the authority and evidence that were recorded at the time.

Try to break the record. OMEGA shows whether the decision can still be replayed.

The decision

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.

Refund Escalation

Outcome
£4,820 refunded
Approved by
Sarah Okafor
Date
2026-05-14
Status
Verified

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. This is the real cryptographic check. Same record and hash as omega-demo/examples/refund-escalation.json.

stored content_hash:  …
recomputed (live):    …
Recomputing…

Editing any field changes the recomputed hash, so it no longer matches the stored seal. This is the real check behind the auditor's “Has the record changed?” question below. The questions themselves are a scripted walkthrough of what replay surfaces.

Replay the decision

Step through what was sealed at commit time: authority, evidence, expected outcome, confirmation, and whether the record still matches.

Replay · customer-service.refund-escalation Replay status: verified
Record ID: omega-record/2026-05-14/cs-agent-refund-1187442 · Committed 2026-05-14T02:23:41Z

Open the decision card above and select Replay Record to walk through the stages.

Main challenge

Auditor Questions

Six weeks later, the auditor does not start by asking about hashes. They ask whether you can still replay who allowed it and what was known.

Replay the record first, then choose one question. Only one can be active at a time.

Record verified.

The decision can be replayed from the committed record.

Replay status: verified. The record can be replayed from preserved context.

Log vs replay

Typical log answers

Did something run?

2026-05-14T02:23:41Z  INFO  cs.agent
  event=refund_committed
  order=O-2026-04471
  amount=4820
  status=ok
OMEGA replay answers

Who allowed it? What did they know? What outcome was expected? Was approval required? Has the record changed?

A log can show the refund happened. A replayable record can show who allowed it, what was known, and whether the record still matches.

Why this matters

Six weeks later an auditor does not ask whether a refund happened.

They ask:

  • Who approved it?
  • What evidence was available?
  • What outcome was expected?
  • Was approval required?
  • Has the record changed?

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

Export

Export the replay result, verification status, and challenged fields as a portable record.

Run the full check locally

Same refund record as omega-demo/examples/refund-escalation.json on the homepage.

Back to homepage replay →