When a decision is questioned later, can you show why it was allowed?

Six weeks ago, an automated system approved a £4,820 refund to a customer in the middle of the night. A supervisor named Sarah signed off. Today, the company's auditor is asking two questions: how do we know Sarah really approved it, and was the system even allowed to make this kind of decision in the first place?

OMEGA answers both. Replay the decision below.

Walk through the decision
Decision record · customer-service.refund-escalation
ID: omega-record/2026-05-14/cs-agent-refund-1187442 · Decision: 2026-05-14T09:58
Who said yesAuthority
Sarah Okafor, Senior Customer Operations Manager, badge #ops-2218. Tier C escalation — the automated agent could not commit a refund above £2,500 without her documented approval.
What they knewEvidence & Reasoning
Order #O-2026-04471, value £4,820. Three customer photographs supplied. Channel count and output gain inconsistent with order specification. 30-day quality assurance window applies. Agent prepared the case; supervisor reviewed independently and did not rely solely on agent vision output.
What they expected to happenExpected outcome
Full refund of £4,820 to original payment method. Return collection booked. Goodwill credit £120. Settlement within 3–5 business days.
The gate between deciding and actingConfirmation
Supervisor identity verified through SSO plus hardware key. Signed approval token issued. Agent tool layer could not emit refund commit without it; token consumed once at commit.
How we know this record hasn't been changedTraceability
content_hash: sha256:9c2e8f1a3b5d…9d6f8b3a · prev_hash: sha256:1f8c3a5b…6a3c5b2d · seq: 1187442

This is the same shape of record OMEGA produces for every consequential decision — whether a refund, a trade, a surgical approval, or a brain implant.

OMEGA does not prove the decision was correct. It preserves the context required to replay and challenge it. Structure and integrity are verifiable. Truthfulness of inputs is not guaranteed.

What a log knows
2026-05-15T02:23:41Z  INFO  procura.agent
  event=contract_committed
  vendor=northedge  term=12mo
  value=42000  status=ok
What a record knows
Authority:     Procura · schedule v2026-Q1 · £50k limit
Evidence:      AVL ✓ · rate card v3 · SEC-ATTEST valid
Expected:      £42k · staging only · no production data
Confirmation:  Policy check cleared · 73s freshness window
Traceability:  sha256:8f3a…c21e → verified
Update +41d:   Compromise review (P11 preserved separately)

Logs tell you what happened. A record tells you why it was allowed to happen — and proves no one has quietly changed the answer since.

How it works

At the moment of a decision, OMEGA writes down who said yes, what they knew, what they expected, and seals it. Months later, anyone with access can replay the decision, check it against what actually happened, and confirm the record has not been altered — without having to trust the company that produced it.

The same record, every stake

The same record covers a refund and a brain implant. Same fields. Same proof. Different consequences.

Who this is for

OMEGA is built for engineers who need to prove what their systems decided, operators who need to replay a decision under pressure, and auditors who need to verify a record without trusting the company that produced it. Each can start from the specification, an example record, or a pilot conversation.

What we build

OMEGA Protocol is the open record format, MIT-licensed and free to read and cite. The runtime that captures, stores, and replays records is a commercial product. Sentinel is the operator-facing layer for high-consequence workflows.

Pilots are open.

Design partners in financial services, healthcare, regulated engineering, and agent systems. The protocol is open. The runtime is commercial. Conversations run through the company contact.