Omission as Structured Evidence

1. Core Idea

Most systems record what happened. Janus also records what should have happened but did not.

In Janus, omission is not silence. Omission is structured evidence.

2. Classical Model vs Janus Model

Classical systems:

• positive event recorded
• absence remains silent

Janus:

• E+ = evidence explicitly recorded in a system of record
• E− = verified omission evidence satisfying every condition in Core §5
• governance outcomes are evaluated against explicit expectations

3. Why This Matters

Omissions are often the most critical failures in socio-technical systems. Examples:

• missing validation
• missing human decision
• missing required review
• missing protocol step

4. Canonical Janus Expression

E+ = explicit evidence; E− = verified omission evidence under Core §5.

For governance-required activity:

A governance evaluation may produce E+ or E− when the applicable Core conditions are met.

If an expected event is absent and all conditions in Core §5 are satisfied, the system records structured omission evidence as specified by Core §6.

5. Runtime Illustration

The reference runtime demo (Node) illustrates omission detection for its generated dataset. It does not prove the general formula or establish conformity with the Core.

Use this example:

1000 CHANGE_PROPOSED → 464 HUMAN_DECISION_REGISTERED → 536 OMISSION_DETECTED (E−)

Dataset accounting: 464 + 536 = 1000.

HUMAN_DECISION_REGISTERED is a runtime-specific label associated with the open technical divergence R1-011. The only canonical human-authority event is HUMAN_DECISION.

6. Principle

What did not happen, when it was required to happen, is part of system truth.