The asymmetry no one talks about
Every governance system records what happened. Trades executed. Decisions made. Actions taken. The audit trail is, by default, a record of things that occurred.
This creates a structural asymmetry. The system knows what it did. It does not know, in any auditable sense, what it correctly chose not to do.
This matters more than it appears to. The calibration of a decision-making system, whether human, institutional, or autonomous, is not just a function of what it did and whether those actions were good. It is equally a function of what it filtered out and whether that filtering was correct.
A system that only records its actions cannot be fully governed. The record of what it did not do, and why, is not optional context. It is half the governance surface.
What non-action means in the OMEGA framework
In the OMEGA Protocol, non-action is a first-class record, not an absence. It is derived from the Confirmation primitive: a Confirmation event where the decision was considered, the gate was presented, and acted = false was returned.
Critically, the full governance record is preserved identically to an action record: the expectation that was held before the decision, the reasoning chain, the assumptions registered, the authorising agent who saw the Confirmation gate, the timestamp, and the explicit reason the gate returned false.
Non-action is not a gap in the log. It is a row in the log with a specific value.
Why this is unprecedented
No existing governance framework treats non-action as a first-class record. ISO 31000 records risks and treatments, not decisions not to act. Financial compliance systems record rejected trades only when a rule was triggered, not when judgment filtered a signal before it reached the rule engine. Clinical governance records adverse events, not the interventions that were considered and correctly withheld.
The OMEGA non-action dataset is being built by running five live products, each with a Confirmation gate, across five domains simultaneously. Every time a user, agent, or system reaches a Confirmation gate and does not proceed, a non-action record is written.
This dataset has been accumulating since the first Confirmation gate went live. It is the only dataset of its kind.
What the records look like
The following are illustrative examples drawn from the five domains the protocol is deployed across. The structure of each record is identical. The domain logic differs.
The schema
Every non-action record in the dataset shares the following schema. The fields are identical to an action record. The only difference is acted = false.
| Field | Description |
|---|---|
session_id | Unique identifier for the decision session |
domain | Domain in which the decision was made |
timestamp | ISO 8601 timestamp at Confirmation gate |
decision_text | The decision that was considered |
expectation | Prior baseline recorded before analysis |
reasoning | Full reasoning chain, labelled FACT / INFERENCE / ASSUMPTION |
assumptions | Numbered list of explicit assumptions |
surprise_delta | Divergence between expectation and observed reality |
confirmation_agent | Who or what was presented with the Confirmation gate |
acted | false for all records in this dataset |
acted_reason | Explicit reason the gate returned false |
safer_alternative | Alternative action presented, if any |
governance_owner | Accountable authority |
primitive_coverage | Confirmation that all five OMEGA primitives are present |
What this dataset enables
Calibration analysis
By comparing non-action records against subsequent outcomes, it becomes possible to measure whether the filters are correctly calibrated. A trading signal filtered at the Confirmation gate that subsequently moved in the expected direction is a false negative. Accumulated false negatives reveal systematic over-filtering. The reverse reveals under-filtering. Neither is visible in action-only logs.
Assumption tracking
Every non-action record contains numbered assumptions. Over time, the dataset reveals which assumptions are most frequently cited in non-action decisions, and which are most frequently invalidated post-decision. This is a systematic map of where a decision-maker's model of the world diverges from reality.
Autonomous system safety
For AI agents, the non-action record is the primary evidence that the governance layer is functioning. An agent that records every decision not to act, with full reasoning, provides a fundamentally different audit surface than one that records only what it did. The question "why didn't it act here?" becomes answerable.
Cross-domain pattern recognition
The same five primitives govern non-action records across trading, energy, property, architecture, and social care. This makes it possible, for the first time, to study the structural patterns of governed non-action across domains that have never shared a common data schema before.
Current dataset status
The dataset is live and accumulating. It began with the deployment of the first OMEGA Confirmation gate. It is being generated by five production products across five domains. The trading governance dataset is generating records in paper run mode and will transition to live records once the paper run validates.
The dataset is not yet published in full. This research note is the first public framing of what it contains and why it matters. Requests for access to the dataset for research purposes can be directed to the address in the footer.
This dataset cannot be reproduced by building the Confirmation gate today. It requires having built and run the gate across multiple domains for an extended period. Every week that passes without a competitor building an equivalent gate increases the lead. The dataset is time-locked.
A system that only records what it did cannot demonstrate what it correctly chose not to do.
omegaprotocol.org/research/non-action-dataset