OOF™ Origin Open Foundation™

Independent Methodological Authority

Architecture Ecosystem: Structured Reality Standards™
Architecture Family: TREGA™ — Tax-Relevant Event Governance Architecture™
Parent Standard: TREPS — Tax-Relevant Event Participation Standard
Module: EPCM — Event Participation Continuity Module
Operational Layer: Event Participation Continuity Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Core Module
Governed Space: Event Participation Continuity
Origin ID: TREGA-TREPS-EPCM-005
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 1 September 2026
AI-Readable: Yes
Authority: OOF®
Protection: MIP® — Methodology Intellectual Property Protection
Canonical Language: UCL — Universal Canonical Language

Canonical Definition

The Event Participation Continuity Module (EPCM) governs how
participation in a Tax-Relevant Event is preserved, updated,
qualified, and traced when participants, roles, associations,
machine or autonomous actors, or participation states change
during the lifecycle of the same governed event.

EPCM determines whether changes in participation represent
continuity within the same event or indicate a material
transformation that must be referred back to the appropriate
upstream TREGA™ governance layer.

Its principal task is: Governed Participation Structure

↓

Governed Participation Continuity

EPCM does not identify participants.

EPIM owns Participant Identification.

EPCM does not determine Participation Roles.

EPRM owns Participation Role governance.

EPCM does not establish the original Actor–Event Association.

EPAM owns Actor–Event Association.

EPCM does not establish specialized machine or autonomous
participation.

EPMAM owns that governance.

EPCM governs what happens after participation has already been
established and subsequently changes.

The foundational distinction is: Participation Change ≠ New Event
by DefaultOperational Role

Participation in real-world and digital events is not always
static.

A participant may: enter the event; leave the event; pause
participation; resume participation; change role; be replaced;
act through another system; transfer execution; become inactive;
re-enter later; move from human to machine execution; or
participate only during one stage of the event.

Without continuity governance, systems may incorrectly: create
duplicate participants; erase historical participation; merge
distinct actors; treat every role change as a new event; lose the
sequence of participation; or rewrite prior participation states.

EPCM preserves participation as a governed lifecycle structure.

Internal Module Flow

TREPS operates through:

EPIM — Participant Identification

→ EPRM — Participation Role

→ EPAM — Actor Association

→ EPMAM — Machine & Autonomous Actor Governance

→ EPCM — Participation Continuity

→ Governed Participatory Event

EPCM is the final Core Module within TREPS.

It receives the governed participation structures produced by the
preceding modules and establishes whether participation remains
coherent across change.

Operational Transition

The canonical EPCM transition is:

Governed Participant References + Governed Participation Roles +
Governed Actor–Event Associations + Governed Machine / Autonomous
Participation

→ Participation Continuity Governance

→ Governed Participation Continuity Structure

→ Governed Participatory EventOperational Space

EPCM governs: participant entry; participant exit; participation
pause; participation resumption; role change; participant
replacement; actor substitution; participation transfer;
sequential participation; overlapping participation;
participation interruption; participation reactivation;
participation-state change; participation-history preservation;
machine/human participation transitions; continuity uncertainty;
continuity conflict; and continuity traceability.

EPCM governs these mechanisms only within the already governed
event boundary.

Operational Scope

EPCM may operate across: commercial events; digital transactions;
manufacturing; logistics; banking; marketplaces; platform
operations; distributed services; AI-agent workflows; autonomous
systems; robotic operations; machine-to-machine events;
multi-stage processes; cross-border operations; and other events
in which participation changes while the event continues.

Participation Continuity

Participation Continuity means that changes in the participant
structure remain linked to the same governed event where the
event itself has not materially transformed into a different
event.

The continuity question is therefore:

Does the participation change represent evolution within the same
event, or does it require upstream event re-evaluation?

EPCM governs the participation side of this question.

It does not independently redefine Event Formation or Event
Boundary.

Participant Entry

A participant may become materially involved after the event has
already begun.

EPCM shall support legitimate participant entry without forcing
the creation of a new event.

Therefore:

Participant Entry ≠ New Event by Default.

The new participant must still satisfy the relevant TREPS
governance requirements.

Participant Exit

A participant may cease material involvement before the event
ends.

EPCM shall preserve both: the fact that the actor participated;
and the point at which participation ended where materially
relevant.

Therefore:

Participant Exit ≠ Historical Non-Participation.

Past governed participation shall not be erased merely because an
actor later exits.

Participation Pause and Resumption

Participation may temporarily stop and later resume.

EPCM shall distinguish temporary interruption from permanent exit
where operational reality supports that distinction.

Participation Pause ≠ Participant Exit by Default.

Likewise:

Participation Resumption ≠ New Participant by Default.

Role Change

A participant may change operational role while remaining part of
the same event.

EPCM shall preserve the transition between governed roles.

For example:

Initiator

↓

Coordinator

Processor

↓

Transfer Actor

Human Operator

↓

Supervisor

Autonomous Agent

↓

Escalated Human Control

Such change shall remain traceable.

Role Change ≠ New Participant by Default.

Role Change ≠ New Event by Default.

EPRM remains authoritative for the actual role definitions.

EPCM governs continuity across the change.

Participant Replacement

One actor may replace another during an event.

Replacement does not mean the actors are the same actor.

Therefore:

Participant Replacement ≠ Actor Identity Continuity.

EPCM shall preserve: outgoing participant; incoming participant;
transition relationship; participation interval where relevant;
and historical traceability.

Actor Substitution

An operational process may substitute one actor for another.

Examples may include: employee replacement; service-provider
replacement; machine replacement; agent handoff; system failover;
or autonomous actor substitution.

EPCM shall not overwrite the original participant merely because
another actor assumes the same role.

Same Role ≠ Same Participant.

Participation Transfer

An actor may transfer an operational function to another actor.

Where this occurs within the same governed event, EPCM shall
preserve the transfer relationship without automatically treating
the entire event as newly formed.

Participation Transfer ≠ Event Transfer.

Authority or legal delegation related to that transfer remains
outside EPCM.

Sequential Participation

Actors may participate one after another.

EPCM shall support sequence where materially relevant.

For example:

Actor A

↓

Actor B

↓

Actor C

may all legitimately belong to the same governed event.

Therefore:

Sequential Participants ≠ Sequential Events by Default.

Event Relationships remain governed by TRERLS where separate
events exist.

Overlapping Participation

Two or more participants may be active during overlapping
periods.

EPCM shall preserve overlap without forcing artificial
exclusivity.

Overlapping Participation ≠ Shared Identity.

Overlapping Participation ≠ Equal Role.

Participation Interruption

Operational disruptions may temporarily alter participation.

A network outage may remove one system.

A machine may fail.

A human may intervene.

A backup provider may take over.

EPCM shall preserve the participation history through such
interruptions where the event remains the same governed event.

Human-to-Machine Transition

An event may begin with human execution and later continue
through automated or autonomous systems.

EPCM shall preserve the transition rather than rewriting the
entire event under one actor type.

Example:

Human Operator

↓

Automated System

↓

Autonomous Agent

may remain one participation-continuity structure.

Human-to-Machine Transition ≠ New Event by Default.

Machine-to-Human Transition

The opposite may also occur.

An autonomous system may escalate control to a human.

EPCM shall preserve both participation states.

Machine-to-Human Escalation ≠ Erasure of Prior Machine
Participation.

This is particularly important for auditability and later legal
analysis.

Machine Replacement

A machine may be replaced by another machine during the event.

Where the event itself continues, EPCM shall preserve both
machine participants and their participation periods or
transitions.

Replacement Machine ≠ Original Machine.

Machine Replacement ≠ New Event by Default.

Autonomous Actor Replacement

One AI agent or autonomous system may transfer activity to
another.

EPCM shall preserve actor continuity without assuming that two
autonomous instances represent the same governed actor.

EPIM and EPMAM remain authoritative for actor identity and
non-human participation classification.

Participation State

Participation may occupy different operational states.

EPCM may represent states such as:

Active

Inactive

Paused

Resumed

Transferred

Replaced

Exited

Completed

Qualified

Unresolved

These states describe participation continuity only.

Historical Preservation

A current participation state shall not overwrite materially
relevant historical states.

The canonical rule is: Current Participation State ≠ Complete
Participation History

EPCM shall preserve reconstructability of prior participation
states where materially relevant.

Correction Versus Historical Erasure

An earlier participation record may later be found incorrect.

A legitimate correction may amend the governed participation
history.

However:

Participation Correction ≠ Historical Erasure.

The original state and correction should remain traceable where
governance requires reconstruction.

Continuity and Actor Identity

Participation continuity does not prove identity continuity.

The same role may pass between different actors.

The same actor may appear through changing references.

Therefore:

Participation Continuity ≠ Actor Identity Continuity.

EPIM and OBIDENITY® remain authoritative for actor identification
and deeper identity governance.

Continuity and Event Boundary

EPCM operates inside the existing governed Event Boundary.

If a participation change appears to fundamentally alter what
constitutes the event, EPCM shall not independently redefine that
event.

Instead, the issue must be referred to the relevant upstream
TREGA™ layer.

Therefore:

Participation Change ≠ Permission to Redefine Event Boundary.

TREBS remains authoritative for Event Boundary.

Continuity and Event Formation

Some changes may be so material that they indicate the formation
of another event.

EPCM shall support escalation where this possibility exists.

However:

Material Participation Change ≠ New Event Automatically.

TREFS and TREBS determine whether a new event actually exists.

Continuity and Timing

Participation continuity may use governed Event Timing to
establish entry, exit, sequence, overlap, pause, or resumption.

EPCM does not redefine Event Timing.

Therefore:

Participation Interval ≠ Event Timing Governance.

TRETS remains authoritative for the temporal structure of the
event.

Continuity and Location

A participant may change location while participation continues.

Likewise, the event itself may move across operational locations.

EPCM shall not treat participant movement as automatic
participation discontinuity.

Participant Location Change ≠ Participation Break by Default.

TRELS remains authoritative for Event Location.

Continuity and Role

EPCM consumes roles governed under EPRM.

It does not redefine role meaning.

Its responsibility is to preserve how those roles change over
time.

Therefore:

Role Governance ≠ Role Continuity Governance. Continuity and
Machine / Autonomous Participation

EPCM consumes non-human participation structures from EPMAM.

It governs how they persist or change across the event.

Examples may include: autonomous execution becoming supervised;
one agent replacing another; machine failover; human escalation;
autonomous delegation; or return from human intervention to
autonomous execution.

EPCM preserves continuity while EPMAM remains authoritative for
machine/autonomous participation characteristics.

Continuity and Value

Participation changes do not automatically determine changes in
value ownership, value entitlement, benefit, cost, revenue, or
Tax Base.

Therefore:

Participation Continuity ≠ Value Continuity.

TRVAS governs Value Association.

VFM® governs the Value Lifecycle.

Continuity and Accountability

A participant entering, leaving, or changing role does not
automatically determine accountability.

Therefore:

Participation Continuity ≠ Accountability Continuity.

AGA™ governs accountability where applicable.

Continuity and Liability

Historical participation may become relevant to later liability
analysis.

EPCM preserves the facts necessary for such analysis but does not
determine liability.

Therefore:

Participation History ≠ Liability Determination.

HALIA™ governs harm and liability lifecycle where applicable.

Continuity and Tax Status

A participant may change role or involvement while a jurisdiction
later assigns different legal significance to different parts of
that participation.

EPCM does not determine such tax consequences.

Therefore:

Participation State Change ≠ Tax Status Change by Default.

Participant Exit ≠ End of Tax Obligation by Default.

Participant Entry ≠ Creation of Tax Liability by Default.

These are jurisdiction-specific determinations.

Continuity Uncertainty

It may be unclear whether participation genuinely continued,
ceased, resumed, transferred, or was replaced.

EPCM shall preserve uncertainty where available information
cannot legitimately resolve the state.

Continuity Uncertainty ≠ Permission to Invent Continuous
Participation.

Continuity Conflict

Different records may present conflicting participation
histories.

One source may indicate continuous activity.

Another may indicate termination and later re-entry.

EPCM shall preserve materially relevant conflict until
sufficiently resolved.

Continuity Conflict ≠ Permission to Select the Most Convenient
Timeline.

Continuity Traceability

A governed participation structure shall remain reconstructable
across change.

The record should permit determination of: who participated; when
participation began; what role was held; when role changed;
whether participation paused; whether participation resumed;
whether another actor replaced the participant; whether
machine/human control changed; when participation ended; what
uncertainty existed; and what corrections were later made.

This traceability supports downstream governance without
converting participation history into legal conclusions.

Governance States

EPCM may represent continuity states including:

Continuity Ready

Continuity Under Governance

Continuous Participation

Interrupted Participation

Paused Participation

Resumed Participation

Transferred Participation

Replaced Participation

Participation Exited

Participation Completed

Continuity Qualified

Continuity Conflicted

Continuity Unresolved

Participation Continuity Established
Governance Requirements

EPCM implementations shall ensure that: participation changes
remain linked to the governed event; participant entry can be
represented; participant exit does not erase historical
participation; pause and resumption can be distinguished; role
changes remain traceable; participant replacement does not merge
identities; actor substitution preserves outgoing and incoming
actors; participation transfer can be represented; sequential
participants can belong to one event where legitimate;
overlapping participation can be represented; human-to-machine
transitions can be preserved; machine-to-human transitions can be
preserved; machine and autonomous replacement can be represented;
historical participation states remain reconstructable;
corrections do not erase prior governance history;
participant-location changes do not automatically break
continuity; participation changes do not automatically redefine
Event Formation or Event Boundary; uncertainty remains visible;
conflicts remain visible; Value Association remains separate;
accountability and liability remain separate; and tax status
remains downstream.

Governance Logic

IF a Governed Event Participant already exists and its
participation changes, THEN EPCM shall determine whether the
change can remain within the same governed participation
lifecycle.

IF a participant enters or exits while the governed event remains
the same, THEN participation history shall be updated without
automatic event reformation.

IF a participant changes role, THEN the role transition shall
remain traceable without automatically creating a new
participant.

IF one actor replaces another, THEN both actors shall remain
separately attributable.

IF human and machine execution transition during the event, THEN
both participation states shall remain preserved where materially
relevant.

IF participation change may indicate a fundamentally different
event, THEN EPCM shall escalate the issue to the relevant
upstream TREGA™ governance layer rather than redefining the event
independently.

IF continuity remains uncertain or conflicted, THEN the
uncertainty or conflict shall remain visible.

IF participation continuity is sufficiently governed, THEN TREPS
may produce a Governed Participatory Event.

Minimum Implementation Framework

A minimum EPCM implementation should support:

Governed Event Reference

The event whose participation continuity is being governed.

Participant Reference

The governed participant whose continuity is being evaluated.

Participation Continuity Identifier

The stable reference for the continuity record.

Prior Participation State

The immediately preceding governed participation state.

Current Participation State

The current governed participation state.

Role Reference

The governed role applicable to the participation state.

State Effective Point

The governed temporal reference associated with the state change.

Entry State

Whether the actor enters participation.

Exit State

Whether the actor exits participation.

Pause / Resume State

Whether participation temporarily stops or resumes.

Replacement Reference

The outgoing or incoming actor where replacement occurs.

Transfer Reference

The relationship representing transfer of participation.

Human / Machine Transition State

Whether execution transitions between human and non-human actors.

Continuity Confidence

The qualified confidence attached to the continuity
representation.

Ambiguity State

Whether continuity remains materially ambiguous.

Conflict State

Whether materially conflicting histories exist.

Correction Reference

Any governed correction affecting participation history.

Traceability Reference

The information required to reconstruct participation continuity.

Governance State

The current EPCM state.

Handoff State

Whether TREPS participation governance is complete.

Governance Outputs

EPCM may produce: Governed Participation Continuity Record;
Participant Entry Record; Participant Exit Record; Participation
Pause Record; Participation Resumption Record; Participation Role
Transition Record; Participant Replacement Record; Participation
Transfer Record; Sequential Participation Structure; Overlapping
Participation Structure; Human–Machine Transition Record;
Machine–Human Transition Record; Participation History;
Participation Continuity Confidence State; Participation
Continuity Ambiguity State; Participation Continuity Conflict
State; Participation Correction Record; and the principal output:

Governed Participation Continuity
Structure

When combined with the preceding TREPS outputs, this enables the
Parent Standard to produce: Governed Participatory EventCritical
Distinctions

Participation Change ≠ New Event by
Default

Participant Entry ≠ New Event by Default

Participant Exit ≠ Historical
Non-Participation

Participation Pause ≠ Participant Exit by
Default

Participation Resumption ≠ New Participant
by Default

Role Change ≠ New Participant by Default

Role Change ≠ New Event by Default

Participant Replacement ≠ Actor Identity
Continuity

Same Role ≠ Same Participant

Participation Transfer ≠ Event Transfer

Sequential Participants ≠ Sequential
Events by Default

Overlapping Participation ≠ Shared
Identity

Human-to-Machine Transition ≠ New Event by
Default

Machine-to-Human Escalation ≠ Erasure of
Prior Machine Participation

Machine Replacement ≠ New Event by Default

Current Participation State ≠ Complete
Participation History

Participation Correction ≠ Historical
Erasure

Participation Continuity ≠ Actor Identity
Continuity

Participation Change ≠ Permission to
Redefine Event Boundary

Material Participation Change ≠ New Event
Automatically

Participation Interval ≠ Event Timing
Governance

Participant Location Change ≠
Participation Break by Default

Role Governance ≠ Role Continuity
Governance

Participation Continuity ≠ Value
Continuity

Participation History ≠ Liability
Determination

Participation State Change ≠ Tax Status
Change by Default

Participant Exit ≠ End of Tax Obligation
by Default

Participant Entry ≠ Creation of Tax
Liability by Default Enterprise
Application

EPCM completes the TREPS participation-governance chain:

ERP / Commerce / Banking / Platform / AI
Agent / Machine System

→ EPIM — Governed Participant Candidate Set

→ EPRM — Governed Participant Role Set

→ EPAM — Governed Actor–Event Association Set

→ EPMAM — Governed Machine & Autonomous Participation Set

→ EPCM — Governed Participation Continuity Structure

→ Governed Participatory Event

→ TRVAS — Tax-Relevant Value Association Standard

This allows downstream systems to consume a stable participation
history rather than only a snapshot of who appears to participate
at one moment. Use Case 1 — Multi-Stage Cross-Border Service
Event

A service begins with one operating entity and one specialist.

During execution, the specialist is replaced, another
organization performs a later stage, and a digital platform takes
over part of the coordination.

The customer remains the same, while participation roles change
over time.

EPCM preserves the original participant, replacement actor, role
transitions, entry and exit points, and overlapping periods
without automatically creating a new event for every
participation change.

The resulting Governed Participatory Event allows downstream tax
systems to evaluate the complete participation history rather
than a misleading final-state participant list. Use Case 2 —
Autonomous Industrial Operation with Human Escalation

An autonomous machine begins an industrial operation under normal
autonomous control.

An AI agent coordinates the process until an anomaly is detected.

A human operator temporarily takes control, performs corrective
action, and then returns execution to the autonomous system.

EPCM preserves the sequence:

Autonomous Machine Participation

↓

AI-Agent Coordination

↓

Human
Intervention

↓

Return to Autonomous Execution

without erasing the original non-human participation or treating
every control transition as a separate event.

The complete governed participation history can later support
jurisdiction-specific evaluation, accountability analysis, audit,
or liability governance without EPCM itself determining any of
those legal conclusions.

Canonical Boundary

EPCM owns the governance of continuity, change, entry, exit,
pause, resumption, role transition, replacement, substitution,
transfer, sequence, overlap, human-machine transition, history
preservation, correction, uncertainty, conflict, and traceability
of already-governed Event Participation.

EPCM does not own Participant Identification, Participation Role
definition, original Actor–Event Association, specialized Machine
& Autonomous Actor qualification, Event Formation, Event
Boundary, Event Timing, Event Location, identity, ownership,
authority, Value Association, Event Relationships,
accountability, responsibility, liability, taxpayer status, Tax
Jurisdiction, tax nexus, permanent establishment, place of
supply, taxability, Tax Liability, filing, reporting, collection,
payment, or enforcement.

Its governance ends when participation throughout the event is
sufficiently coherent, historically reconstructable, and ready to
become part of the final TREPS output.

Canonical Handoff

EPAM — Governed Actor–Event Association Set EPMAM — Governed
Machine & Autonomous Participation Set

→ EPCM — Governed Participation Continuity Structure

→ TREPS — Governed Participatory Event

→ TRVAS — Tax-Relevant Value Association Standard

Canonical Closing Statement

EPCM preserves who or what participated as participation changes
over time without allowing every entry, exit, role change,
replacement, or human-machine transition to redefine the event
itself.

Participation may change while the governed event remains
continuous.

Participation Change ≠ New Event by Default.