OOF™ Origin Open Foundation™

Independent Methodological Authority

Architecture Ecosystem: Structured Reality Standards™
Architecture Family: TREGA™ — Tax-Relevant Event Governance Architecture™
Parent Standard: TRECLS — Tax-Relevant Event Lifecycle & Continuity Standard
Module: ESPM — Event Supersession Module
Operational Layer: Event Supersession Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Core Module
Governed Space: Event Supersession
Primary Governed Object: Governed Event Supersession State
Origin ID: TREGA-TRECLS-ESPM-004
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 3 September 2026
AI-Readable: Yes
Authority: OOF®
Protection: MIP® — Methodological Intellectual Property
Canonical Language: UCL — Universal Canonical Language

Canonical Definition

The Event Supersession Module (ESPM) governs how a prior governed
Tax-Relevant Event state or Event Record representation is
replaced as the current effective state by a later governed state
while preserving historical continuity, predecessor-successor
relationships, prior-state reconstructability, and the
distinction between Event Supersession and New Event Formation.

Its principal transition is:

Governed Event Correction State / Current Governed Event State

↓

Event Supersession Governance

↓

Governed Event Supersession State

ESPM establishes which governed state is currently effective
without deleting the state that preceded it.

Its foundational distinction is:

Supersession ≠ Historical Deletion.

Operational Role

A Tax-Relevant Event may accumulate multiple governed states over
time.

A later state may need to become authoritative for current
lifecycle use because of: Amendment; Correction; reconsideration;
Record replacement; Merge/Split consequences; schema or
representation change; improved governance state; or another
legitimate lifecycle transition.

ESPM answers:

Which governed Event state now replaces the prior effective
state, what exactly was superseded, why, and what historical
relationship must remain preserved?

Its purpose is to prevent: competing current states; silent
replacement; historical erasure; ambiguous predecessor-successor
chains; accidental creation of new Events; and confusion between
Record replacement and Event replacement.

Internal Module Flow

TRECLS operates through:

ECOM — Event Continuity

↓

EADM — Event Amendment

↓

ECRTM — Event
Correction

↓

ESPM — Event Supersession

↓

ECLM — Event Closure

↓

Jurisdiction-Ready Tax-Relevant Event

ESPM receives the applicable current governed Event state and
produces:

Governed Event Supersession State

for Closure Governance.

Operational Transition

The canonical transition is:

Current Governed Event State

↓

Supersession Trigger

↓

Predecessor
Identification

↓

Successor Identification

↓

Supersession Basis

↓

Effective-State Transition

↓

Governed Event Supersession State
Operational Space

ESPM governs: Supersession Trigger identification;
predecessor-state identification; successor-state identification;
supersession eligibility; supersession scope; supersession basis;
Event-state supersession; Record-state supersession;
effective-state transition; predecessor-successor relationship;
supersession materiality; partial supersession; full
supersession; supersession qualification; supersession ambiguity;
supersession conflict; supersession chain; supersession reversal;
supersession withdrawal; continuity impact; upstream
reassessment; historical-state preservation; and supersession
handoff.

Operational Scope

ESPM may govern supersession in: physical Events; digital
transactions; commercial Events; financial Events; platform
activity; AI-agent Events; autonomous systems; machine-to-machine
Events; distributed systems; digital assets; industrial activity;
cross-border Events; multi-party Events; long-running Events; and
future machine economies.

The module remains technology-neutral and jurisdiction-neutral.

Supersession Object

The Supersession Object is the prior governed Event state or
governed Event Record representation that is proposed to be
replaced as the current effective state.

The object being superseded may be: Event state; lifecycle state;
corrected state; amended state; Record representation;
Determination-linked state; qualified state.

Superseded State ≠ Deleted State.

Supersession Trigger

A Supersession Trigger may arise from: validated Amendment;
established Correction; revised Determination; successor Record
creation; schema migration; representation replacement;
Merge/Split result; continuity decision; governance
reconciliation; reopening; or other lifecycle transition.

Not every change requires formal Supersession.

Supersession Eligibility

A state is eligible for Supersession where: a valid predecessor
state exists; a valid successor state exists or is being
established; the successor legitimately replaces the predecessor
for current use; the predecessor remains reconstructable;
continuity remains valid or appropriately governed; and the
transition does not improperly conceal New Event Formation.

Predecessor State

The Predecessor State is the governed state that was current or
materially effective before Supersession.

It must remain identifiable.

A system should be able to answer: what the predecessor was; when
it was effective; why it ceased to be current; and what replaced
it.

Successor State

The Successor State is the governed state that becomes current
after valid Supersession.

It may result from: Amendment; Correction; reconsideration;
Record replacement; or other lifecycle governance.

Successor State ≠ New Event by default.

Effective-State Transition

Supersession governs the transition:

Prior Effective State

↓

Supersession

↓

New Effective State

The transition shall preserve both lifecycle meaning and
historical reconstructability.

Event-State Supersession

Event-State Supersession occurs where a later governed state of
the same Event replaces an earlier state as current.

Examples include: corrected Location state; revised Participation
state; amended Value Association; reconsidered
Determination-linked lifecycle state.

The Event may remain the same Event.

Record-State Supersession

A Record representation may be superseded while the Event remains
unchanged.

Examples include: schema replacement; canonical Record version
replacement; corrected Record structure; migrated Record
representation.

Record Supersession ≠ Event Supersession by default.

TREGS remains authoritative over Record Governance.

Event Supersession vs New Event Formation

Supersession must not be used to hide a genuinely new Event.

If the successor represents a materially different operational
occurrence, Continuity must be reassessed.

Supersession ≠ Permission to Replace One Event with Another Under
the Same Identity.

Full Supersession

Full Supersession occurs where the prior governed state is no
longer current in its entirety.

The prior state remains historical.

Partial Supersession

Partial Supersession occurs where only part of the prior state is
replaced.

The remaining unaffected components may continue as current.

Partial Supersession ≠ Full State Replacement.

Supersession Scope

The supersession scope should identify exactly what is being
replaced.

Possible scopes include: full Event state; one Event component;
one lifecycle state; one Record representation; one
Determination-linked state; one downstream representation
reference.

Supersession Basis

A valid Supersession should possess an identifiable basis.

Examples include: Correction result; Amendment result; TREDS
reconsideration result; Record Governance outcome; upstream
governance revision; Merge/Split consequence; continuity
decision.

The basis should remain reconstructable.

Supersession Effective Time

Where materially relevant, the system should distinguish:
predecessor effective period; successor establishment time;
supersession decision time; successor effective time.

These governance timestamps do not establish legal tax timing.

Current Effective State

After valid Supersession, the successor becomes the current
effective state.

The predecessor remains historical.

Current Effective State ≠ Only Historically Valid State.

Historical Preservation

ESPM shall preserve materially relevant predecessor states.

The canonical principle is:

Supersession Replaces Current Effect — Not Historical Existence.

Supersession Chain

An Event may undergo multiple Supersessions:

State A

↓

State B

↓

State C

↓

State D

The chain should remain reconstructable.

The system should identify: immediate predecessor; immediate
successor; current state; historical supersession path.

Broken Supersession Chain

A Broken Supersession Chain exists where one or more
predecessor-successor relationships cannot be reconstructed.

A materially broken chain may prevent reliable lifecycle closure
or jurisdiction readiness.

Supersession Conflict

Conflict exists where multiple successor states claim to
supersede the same predecessor without clear governance priority.

Examples include: two corrected states; competing
jurisdiction-neutral Record versions; incompatible upstream
governance results.

Conflict shall remain explicit.

Supersession Ambiguity

Ambiguity exists where it is unclear: whether Supersession
occurred; which state was superseded; which successor is current;
whether replacement is partial or full; whether continuity
remains valid.

Supersession Qualification

A Supersession may be qualified where: some predecessor
information remains partially current; successor state remains
incomplete; one upstream governance issue is unresolved;
downstream use requires limitation.

Qualification shall remain visible.

Supersession Reversal

A Supersession may later be reversed where the successor is
invalidated and a prior state becomes current again or another
successor is established.

Reversal shall not erase the intermediate state.

A valid pattern may be:

State A

↓

State B

↓

Reversal

↓

State A Reinstated

or:

State A

↓

State B

↓

State C State Reinstatement

A prior state may be reinstated where governance establishes it
as current again.

Reinstatement does not mean the intervening lifecycle history
never occurred.

Reinstatement ≠ Historical Reset.

Supersession Withdrawal

A proposed Supersession may be withdrawn before becoming
effective.

Materially relevant withdrawal history should remain
reconstructable.

Supersession Replacement

A pending Supersession may itself be replaced by a superior
successor decision.

The latest valid governance result should remain clearly
distinguishable.

Supersession and Amendment

An Amendment may create a new current Event state.

ESPM may then govern its replacement relationship to the prior
state.

Amendment ≠ Supersession by default.

Supersession and Correction

A Correction may create a corrected successor state.

ESPM may establish that corrected state as the current effective
state.

Correction ≠ Supersession by default.

The mechanisms remain distinct.

Supersession and Continuity

Supersession assumes that Event Continuity remains valid unless
explicitly broken.

Where successor state materially challenges Event identity, ECOM
must reassess Continuity.

Valid Successor State ≠ Automatic Same-Event Continuity.

Supersession and Closure

Before an Event is closed, ECLM should be able to identify which
state is currently effective.

ESPM provides that effective-state clarity.

A Superseded state should not be mistaken for the state being
closed.

Supersession and Reopening

A reopened Event may create a successor to the previously Closed
state.

The prior Closure remains historically reconstructable.

Supersession and Event Relationships

TRERLS owns Merge and Split.

ESPM governs whether valid Merge/Split results supersede prior
lifecycle states or require predecessor-successor relationships.

Merge Supersession

A Merge may cause prior Event states to cease being current in
favor of a merged successor Event.

Where that successor is a new Event, Formation remains upstream.

Merge Supersession ≠ Merge Formation.

Split Supersession

A Split may supersede one prior Event state with multiple
successor Event states.

Event identity implications require ECOM and TREFS where
appropriate.

Cross-System Supersession

Different systems may hold different versions of one Event
Record.

ESPM helps establish which canonical state is current.

Most Recent Technical Record ≠ Current Governed State by default.

Cross-Organization Supersession

Organizations may independently produce successor candidates.

Canonical Supersession requires governed authority and basis.

Later External Record ≠ Canonical Successor by default.

Cross-Border Supersession

Different jurisdictions may maintain different tax assessments
based on different Event Record versions.

Those legal states do not determine canonical TREGA™
Supersession.

Jurisdictional Tax Replacement ≠ Event Supersession.

Machine-Generated Supersession

Autonomous systems may continuously emit newer state
representations.

A later timestamp or version number does not automatically make a
state the governed successor.

Newest Machine State ≠ Canonical Successor by default.

High-Frequency Supersession

In high-volume systems, frequent technical state replacement
should not generate unnecessary canonical Supersession events.

Formal Supersession is required only where current governed Event
meaning materially changes.

Version Supersession

A newer technical Record version may supersede an older version.

Version Supersession remains distinct from Event Supersession.

Record Version Change ≠ Event State Change by default.

Semantic Supersession

Where a successor materially changes the canonical meaning of the
Event state, the change should be governed substantively rather
than treated as simple version replacement.

Supersession and Traceability

Material Supersession shall remain traceable through
predecessor-successor relationships.

ERTM owns Record Traceability.

ESPM owns lifecycle supersession meaning.

Supersession and Interoperability

The current effective state should propagate across systems
without semantic drift.

ERINM owns Interoperability.

ESPM identifies which governed state should be treated as
current.

Supersession and Tax Law

A successor Event state may produce a new downstream tax outcome.

ESPM does not determine: reassessment; amended filing; tax
adjustment; refund; additional Tax Liability.

These remain jurisdiction-specific.

Event Supersession ≠ Tax Assessment Supersession.

Governance States

ESPM may represent:

Supersession Governance Not Initiated

Supersession Trigger Identified

Predecessor State Identified

Successor Candidate Identified

Supersession Eligibility Under Review

Supersession Eligible

Supersession Scope Defined

Partial Supersession

Full Supersession

Supersession Under Governance

Supersession Qualified

Supersession Ambiguous

Supersession Conflicted

Continuity Reassessment Required

Upstream Review Required

Supersession Rejected

Supersession Withdrawn

Successor State Established

Predecessor State Preserved

Current Effective State Established

Governed Event Supersession State
Established

Ready for Closure Governance Governance
Requirements

ESPM implementations shall ensure that: a valid current governed
Event state exists; predecessor state is identifiable; successor
state is identifiable or governably proposed; Supersession
remains distinct from Amendment and Correction; Record
Supersession remains distinct from Event Supersession;
Supersession does not conceal New Event Formation; supersession
scope is explicit; partial and full Supersession remain
distinguishable; predecessor state remains reconstructable;
successor state becomes current only through valid governance;
supersession basis is identifiable; predecessor-successor
relationship remains traceable; current effective state is
unambiguous where possible; Supersession Conflict remains
explicit; Supersession Ambiguity remains explicit; qualified
Supersession remains distinguishable from complete Supersession;
reversal and reinstatement preserve lifecycle history;
Merge/Split ownership remains with TRERLS; Continuity is
reassessed where Event identity is materially challenged;
technical recency is not treated as canonical authority;
downstream tax replacement remains outside ESPM; and the
resulting state is suitable for Event Closure Governance.

Governance Logic

IF no valid predecessor state exists, THEN ESPM shall not
establish canonical Supersession.

IF no valid successor state exists, THEN Supersession shall
remain pending or unresolved.

IF a successor merely adds information without replacing the
current state, THEN EADM may remain the relevant mechanism.

IF the successor primarily corrects error, THEN ECRTM shall
establish the corrected state before ESPM establishes
Supersession where needed.

IF the replacement affects only technical Record representation,
THEN Event Supersession shall not be assumed.

IF successor and predecessor represent the same Event and
continuity remains valid, THEN Supersession may proceed.

IF successor state materially represents a different occurrence,
THEN ECOM Continuity reassessment and potentially TREFS New Event
Formation shall be required.

IF multiple successor candidates conflict, THEN no single current
state shall be silently selected without governance basis.

IF the Supersession is partial, THEN unaffected predecessor
components may remain current.

IF a valid successor is established, THEN the predecessor shall
cease to be current but remain historically reconstructable.

IF a later valid governance result reverses Supersession, THEN
the reversal shall preserve the supersession history.

IF the current effective state is clear, historically
reconstructable, and continuity remains governed, THEN ESPM shall
establish the Governed Event Supersession State.

Minimum Implementation Framework

A minimum ESPM implementation should support:

Supersession Governance ID Stable identifier for the ESPM
governance process.

Canonical Event Reference The Event under Supersession
Governance.

Current Governed Event State Reference The state existing before
Supersession.

Supersession Trigger Type Amendment, Correction, Reconsideration,
Record Replacement, Merge/Split, Reopening, Technical Migration,
or other governed trigger.

Predecessor State Reference The state proposed to be superseded.

Successor State Reference The proposed or established successor.

Supersession Scope Full Event State, Partial Event State, Record
State, Lifecycle State, or other governed scope.

Supersession Type Full, Partial, Record-Level, Event-Level,
Qualified, Reversal, Reinstatement.

Supersession Basis Reference The governance result supporting
replacement.

Supersession Materiality State Non-Material, Material, Critical,
Unresolved.

Supersession Eligibility State Eligible, Qualified, Ineligible,
Unresolved.

Predecessor Effective State The prior effective status.

Successor Effective State The new effective status.

Supersession Effective Time Reference Where materially relevant.

Predecessor Preservation State Whether prior state remains
reconstructable.

Predecessor-Successor Link Reference The governed relationship
between states.

Supersession Qualification Any limitation attached to
replacement.

Supersession Ambiguity State Whether the replacement remains
uncertain.

Supersession Conflict State Whether competing successors exist.

Continuity Reassessment State Whether ECOM reassessment is
required.

Upstream Review Reference Any referral to another TREGA™ Parent
Standard.

Supersession Withdrawal State Whether proposed Supersession was
withdrawn.

Supersession Reversal Reference Any later reversal.

Reinstatement Reference Any prior state restored as current.

Historical Supersession Chain Reference The sequence of
materially relevant predecessor-successor states.

Current Effective State Reference The state current after
Supersession.

Governance State The current ESPM governance state.

Supersession Outcome Superseded, Partial, Qualified, Rejected,
Withdrawn, Reversed, or Unresolved.

Handoff State Whether the Event is ready for ECLM Closure
Governance.

Governance Outputs

ESPM may produce: Supersession Trigger State; Predecessor State;
Successor State; Supersession Scope; Supersession Type;
Supersession Basis; Supersession Materiality State; Supersession
Eligibility State; Partial Supersession State; Full Supersession
State; Predecessor-Successor Relationship; Predecessor
Preservation State; Current Effective State; Supersession
Qualification; Supersession Ambiguity State; Supersession
Conflict State; Continuity Reassessment State; Supersession
Reversal State; Reinstatement State; Historical Supersession
Chain; and the principal output: Governed Event Supersession
State.

Critical Distinctions

Supersession ≠ Historical Deletion.

Superseded State ≠ Deleted State.

Successor State ≠ New Event by default.

Record Supersession ≠ Event Supersession by default.

Supersession ≠ Permission to Replace One Event with Another Under
the Same Identity.

Partial Supersession ≠ Full State Replacement.

Current Effective State ≠ Only Historically Valid State.

Supersession Replaces Current Effect — Not Historical Existence.

Reinstatement ≠ Historical Reset.

Amendment ≠ Supersession by default.

Correction ≠ Supersession by default.

Valid Successor State ≠ Automatic Same-Event Continuity.

Merge Supersession ≠ Merge Formation.

Most Recent Technical Record ≠ Current Governed State by default.

Later External Record ≠ Canonical Successor by default.

Jurisdictional Tax Replacement ≠ Event Supersession.

Newest Machine State ≠ Canonical Successor by default.

Record Version Change ≠ Event State Change by default.

Event Supersession ≠ Tax Assessment Supersession.

Enterprise Application

ESPM gives organizations a controlled way to determine which
Event state is current when several valid historical states
exist.

The operational pattern is:

Prior Governed Event State

→ Amendment / Correction / Reconsideration / Replacement

→ Successor Candidate

→ Supersession Governance

→ Current Effective State

→ Historical Predecessor Preserved

→ Governed Event Supersession State

This enables downstream systems to consume one clear current
Event state without losing the Event’s lifecycle history. Use
Case 1 — Corrected Event State Replaces Prior State Across
Multiple Tax Systems

A cross-border Event has been consumed by several downstream
systems.

Later, ECRTM establishes a valid corrected Location and
Participation state.

ESPM identifies: the prior effective Event state; the corrected
successor state; the correction basis; the predecessor-successor
relationship.

The corrected state becomes current.

The earlier state remains reconstructable as superseded.

Downstream jurisdictions may reassess their own tax outcomes
independently.

TREGA™ maintains one Event lifecycle.

One current state replaces another without rewriting Event
history. Use Case 2 — Autonomous Platform Generates New Record
Version After System Migration

An autonomous platform migrates its canonical Event Records into
a new infrastructure.

A new Record version is created with different schema, local
identifiers, and storage architecture.

The underlying Event remains unchanged.

TREGS establishes valid Record Governance and interoperability.

ESPM determines that the new Record representation supersedes the
prior technical representation for current use while the Event
itself remains continuous.

The result is:

Prior Record Representation

↓

Successor Record Representation

↓

Record Supersession

↓

Same Governed Event

The technical successor does not become a new Tax-Relevant Event.

Canonical Boundary

ESPM owns the governance of Event and Record Supersession state,
predecessor identification, successor identification,
Supersession eligibility, scope, basis, full and Partial
Supersession, current effective-state transition,
predecessor-successor relationships, historical preservation,
Supersession qualification, ambiguity, conflict, reversal,
reinstatement, withdrawal, Supersession chains,
Continuity-reassessment triggers, and establishment of the
Governed Event Supersession State.

ESPM does not own Event Continuity; ECOM does.

It does not own Amendment; EADM does.

It does not own Correction; ECRTM does.

It does not own Closure; ECLM does.

It does not independently govern Merge or Split; TRERLS does.

It does not create New Events; TREFS governs Event Formation.

It does not determine Event Record identity, structure, linkage,
traceability, or interoperability; TREGS governs those spaces.

It does not determine legal Taxability, Tax Jurisdiction,
taxpayer status, tax nexus, legal tax point, Tax Period, Tax
Base, Tax Rate, exemption, deduction, Tax Liability, filing,
reassessment, payment, collection, or enforcement.

Its governance begins when a valid predecessor state and a
legitimate successor candidate exist.

Its governance ends with:

Governed Event Supersession State

and a clearly identifiable:

Current Effective Event State

ready for Event Closure Governance.

Canonical Handoff

ECRTM / Current Governed Event State

↓

ESPM — Governed Event
Supersession State

↓

ECLM — Event Closure Governance

Where Event identity becomes materially uncertain:

ESPM

↓

ECOM — Continuity Reassessment

Where a materially different occurrence is identified:

ESPM

↓

ECOM

↓

TREFS — New Event Formation Review

Canonical Closing Statement

ESPM establishes which governed Event state is current without
allowing the state it replaces to disappear from history.

Supersession gives lifecycle governance a clear present while
preserving a reconstructable past.

Supersession ≠ Historical Deletion.

Successor State ≠ New Event by default.

Current Effective State ≠ Only Historically Valid State.