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: EPAM — Event Actor Association Module
Operational Layer: Event Actor Association Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Core Module
Governed Space: Event Actor Association
Origin ID: TREGA-TREPS-EPAM-003
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 Actor Association Module (EPAM) governs how identified
Participant Candidates and their governed operational roles are
materially associated with a specific Tax-Relevant Event.

EPAM determines whether the available actor, role, event,
temporal, spatial, and operational information is sufficient to
establish that an actor materially participates in the governed
event.

Its principal transition is: Governed Participant Candidate +
Governed Participation Role

↓

Governed Actor–Event Association

EPAM does not identify the actor.

EPIM owns Participant Identification.

EPAM does not establish the actor's operational role.

EPRM owns Participation Role governance.

EPAM establishes the governed relationship between the actor and
the specific event.

The foundational distinction is: Actor Association ≠ Event
Participation by Default

An actor becomes a Governed Event Participant only when its
association with the event is sufficiently supported and
materially relevant.

Operational Role

Modern event records may contain many identifiable actors and
many technically plausible relationships.

An actor may appear because it: owns infrastructure; appears in a
contract; operates a platform; holds an account; processes
information; provides connectivity; owns a machine; receives a
notification; appears in a payment record; is geographically
nearby; or belongs to the same corporate structure as another
actor.

None of these conditions alone necessarily establishes material
participation.

EPAM exists to determine whether the relationship between an
identified actor, its governed operational role, and the specific
event is sufficient to establish Event Participation.

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

EPAM receives:

Governed Participant Candidate Set

and:

Governed Participant Role Set

and establishes: Governed Actor–Event Association SetOperational
Transition

The canonical EPAM transition is:

Governed Participant Candidate + Governed
Participation Role + Governed Event

→ Actor–Event Association Governance

→ Governed Actor–Event Association

Where multiple actors are involved:

Governed Event

↓

Multiple Governed Actor–Event Associations

The existence of multiple associations does not create multiple
events by default.

Operational Space

EPAM governs: actor-event linkage; association materiality;
association basis; direct participation; indirect participation;
supporting association; multi-actor association; role-event
alignment; temporal association; spatial association; operational
association; association strength; association uncertainty;
association conflict; association change; and association
traceability.

EPAM governs whether an actor's relationship to the event
constitutes material Event Participation.

Operational Scope

EPAM may operate across: commercial transactions; services;
manufacturing; logistics; banking; digital platforms;
marketplaces; infrastructure operations; AI-mediated events;
autonomous transactions; machine-to-machine operations; robotic
systems; distributed systems; hybrid physical-digital events; and
other governable operational events.

The association logic remains jurisdiction-neutral and
technology-neutral.

Association Basis

A Governed Actor–Event Association requires an operationally
justified basis.

Association may be supported by information showing that an actor
materially: initiated; executed; provided; received; transferred;
processed; authorized; coordinated; facilitated; controlled;
operated; delivered; consumed; or otherwise performed a governed
operational role within the event.

The existence of actor information alone is insufficient.

Actor Record Presence ≠ Actor–Event Association.

Material Association

EPAM shall distinguish materially relevant participation from
incidental or background association.

An actor may be connected to an event without materially
participating in it.

Therefore:

Event Connection ≠ Material Event Participation.

A material association exists only where the actor's governed
operational relationship is sufficiently relevant to the event
being governed.

Materiality shall be determined according to operational reality
rather than downstream tax convenience.

Direct and Indirect Association

Participation may occur through direct or indirect operational
relationships.

A direct association may exist where an actor directly performs a
material function within the event.

An indirect association may exist where an actor materially
contributes through an intermediate operational structure.

EPAM shall preserve this distinction where it materially improves
the event representation.

However:

Indirect Association ≠ Non-Participation by Default.

Likewise:

Direct Technical Connection ≠ Material Participation by Default.

The operational function and event relationship remain decisive.

Supporting Association

Some actors or systems may support an event without becoming
material Event Participants.

Examples may include generic infrastructure, background
communications, passive hosting, administrative systems, or other
supporting resources.

EPAM shall permit supporting association to remain
distinguishable from material participation.

Supporting Association ≠ Governed Event Participation by Default.

This prevents every technical dependency from becoming a
participant. Role–Event Alignment

A Governed Participation Role must relate materially to the
specific event before it can support Event Participation.

An actor may perform the same general role across many activities
without participating in every event occurring within that
environment.

Therefore:

Governed Role ≠ Event Participation by Default.

EPAM establishes whether the governed role is actually exercised
in relation to the specific event.

Temporal Association

Actor participation shall be compatible with the governed
temporal structure of the event.

An actor appearing in records before or after an event does not
automatically establish participation during that event.

EPAM may use TRETS-governed temporal information to evaluate
association.

However:

Temporal Proximity ≠ Event Participation by Default.

EPAM does not redefine Event Timing.

TRETS remains authoritative for the event's temporal structure.

Spatial Association

An actor may be physically or digitally located at, near, or
within an Event Location without materially participating.

Likewise, an actor may participate remotely.

Therefore:

Spatial Presence ≠ Event Participation by Default.

Remote Actor ≠ Non-Participant by Default.

EPAM may consume TRELS-governed location information when
evaluating Actor–Event Association but shall not redefine Event
Location.

Transactional Association

An actor may appear within a transaction record without being
materially involved in the underlying governed event.

Likewise, an actor may materially participate even where a
conventional transaction record does not explicitly name it.

Therefore:

Transaction Record Presence ≠ Event Participation by Default.

Transaction Record Absence ≠ Non-Participation by Default.

EPAM governs operational association rather than database
visibility alone.

Contractual Association

Contracts may provide important evidence of actor relationships.

They do not automatically establish what operationally occurred.

Therefore:

Contractual Party ≠ Event Participant by Default.

Conversely:

Non-Contractual Actor ≠ Non-Participant by Default.

EPAM preserves the distinction between contractual representation
and operational participation.

Ownership Association

Ownership may connect an actor to assets, machines,
infrastructure, organizations, or systems involved in an event.

Ownership alone does not establish participation.

Therefore:

Owner ≠ Event Participant by Default.

Ownership governance remains outside EPAM.

Where necessary, governed ownership information may be consumed
from OBIDENITY®.

Organizational Association

Corporate groups may contain parent companies, subsidiaries,
branches, operating entities, service companies, and other
related organizations.

EPAM shall not transfer participation automatically across
organizational relationships.

Corporate Relationship ≠ Shared Event Participation.

Parent Company Participation ≠ Subsidiary Participation by
Default.

Subsidiary Participation ≠ Parent Company Participation by
Default.

Each Actor–Event Association requires its own sufficient
operational basis.

Platform Association

A digital platform may host, facilitate, coordinate, execute,
intermediate, or merely technically support an event.

EPAM shall determine whether the platform's governed operational
role creates a material Actor–Event Association in the specific
event.

Platform Presence ≠ Event Participation by Default.

Platform participation shall be based on operational function
rather than platform category alone.

Machine and Autonomous Association

Machines, AI agents, robots, and autonomous systems may possess
material Actor–Event Associations independently from humans or
organizations connected to them.

EPAM may establish such associations where operational evidence
supports them.

However, specialized governance of machine and autonomous
participation belongs to:

EPMAM — Event Machine & Autonomous Actor
Module

EPAM therefore establishes the association while EPMAM governs
the specific characteristics of non-human participation.

Machine Association ≠ Owner Association.

AI Agent Association ≠ Developer Association.

Multiple Actor Associations

One governed event may legitimately contain multiple Actor–Event
Associations.

The canonical model is:

One Governed Event

→ Actor A Association

→ Actor B Association

→ Actor C Association

→ Actor N Association

These associations may differ in role, materiality, timing,
location, directness, and operational significance.

Multiple Actor Associations ≠ Equal Participation.

Association Strength

Actor–Event Associations may possess different levels of
operational support.

EPAM shall permit association strength or confidence to be
qualified where required.

An association may be:

Established

Qualified

Partial

Ambiguous

Conflicted

Unresolved

Qualification shall reflect available operational support rather
than desired downstream legal outcomes.

Association Uncertainty

Where available evidence does not sufficiently establish or
reject participation, uncertainty shall remain visible.

Association Uncertainty ≠ Permission to Assume Participation.

Likewise:

Association Uncertainty ≠ Permission to Exclude Participation
Arbitrarily.

The event representation shall preserve uncertainty where
legitimate resolution is not available.

Association Conflict

Different sources may provide incompatible representations of an
actor's relationship to the event.

EPAM shall preserve material conflicts until sufficient
governance supports resolution.

Association Conflict ≠ Permission for Convenient Participant
Selection.

Original materially relevant representations shall remain
traceable.

Association Change

An actor's relationship to an event may evolve.

A supporting actor may become materially active.

A direct participant may cease involvement.

An intermediary may assume execution.

A machine may replace a human process.

EPAM shall preserve materially relevant association changes.

However:

Association Change ≠ New Event by Default.

Participation Continuity is governed subsequently by EPCM.

Association and Identity

EPAM does not determine who an actor fundamentally is.

EPIM provides the Participant Candidate reference, while
OBIDENITY® may provide deeper governed identity structures.

EPAM governs the relationship:

Actor ↔ Specific Governed Event

Therefore:

Actor–Event Association ≠ Identity Governance.

Association and Participation Role

EPRM determines the operational role.

EPAM determines whether that role materially connects the actor
to the specific event.

The distinction is:

EPRM: What operational function may the actor perform?

EPAM: Does that governed function materially associate this actor
with this event?

Therefore:

Participation Role ≠ Actor–Event Association.

Association and Accountability

Material participation does not automatically establish
responsibility or accountability.

Therefore:

Governed Actor–Event Association ≠ Accountability.

Governed Event Participant ≠ Responsible Party by Default.

AGA™ remains authoritative for accountability governance where
applicable.

Association and Liability

Actor–Event Association does not establish liability.

An actor may materially participate without being legally liable
for the event or its consequences.

Therefore:

Event Participation ≠ Liability.

HALIA™ governs the lifecycle of harm and liability where
applicable.

Association and Value

Material participation does not determine which value belongs to
an actor or which value result belongs to the event.

Therefore:

Actor–Event Association ≠ Value Association.

Event Participant ≠ Value Owner by Default.

TRVAS subsequently governs Value Association.

VFM® governs the Value Lifecycle itself.

Association and Tax Status

EPAM shall not transform Event Participation into a
jurisdiction-specific legal classification.

A Governed Event Participant is not automatically: a taxpayer;
taxable person; supplier; customer; employer; employee;
principal; legal agent; marketplace facilitator; withholding
party; permanent establishment; beneficial owner; liable party;
or reporting party.

Therefore: Governed Event Participant ≠
Taxpayer

A jurisdiction may subsequently interpret the participation
according to its own law.

EPAM preserves the operational participation reality on which
such interpretation can operate.

Multi-Jurisdiction Readiness

The same Actor–Event Association may support different legal
conclusions across jurisdictions.

The canonical model is:

One Governed Actor–Event Association

↓

Multiple Jurisdictional Evaluations

EPAM shall therefore avoid embedding one jurisdiction's legal
assumptions into the governed participation structure.

Governance States

EPAM may represent:

Association Ready

Association Under Governance

Association Established

Association Qualified

Association Supporting

Association Partial

Association Ambiguous

Association Conflicted

Association Unresolved

Governed Event Participant Established

These states govern Actor–Event Association only.

They do not determine legal or tax status.

Governance Requirements

EPAM implementations shall ensure that: associations refer to
governed Participant Candidates; relevant Participation Roles are
preserved; association with the specific event is operationally
justified; material participation is distinguished from
incidental connection; direct and indirect associations can be
differentiated where relevant; supporting relationships do not
automatically become material participation; role existence does
not automatically establish Event Participation; temporal
proximity does not automatically establish participation; spatial
presence does not automatically establish participation;
transaction-record presence does not automatically establish
participation; contractual status does not automatically
establish participation; ownership does not automatically
establish participation; corporate relationships do not
automatically transfer participation; machine and autonomous
actors can possess independent associations; multiple actor
associations can coexist; uncertainty remains visible; conflicts
remain visible; material association changes remain traceable;
identity governance remains separate; accountability and
liability remain separate; Value Association remains separate;
and legal tax status remains downstream.

Governance Logic

IF a Governed Participant Candidate and a Governed Participation
Role exist, THEN their relationship to the specific governed
event may be evaluated.

IF the actor's governed role is materially exercised in relation
to the event, THEN a Governed Actor–Event Association may be
established.

IF the relationship is merely incidental, technical,
administrative, or insufficiently material, THEN it shall not
automatically establish Event Participation.

IF participation evidence is uncertain, THEN the association
shall remain qualified or unresolved.

IF materially conflicting representations exist, THEN the
conflict shall remain visible until legitimately resolved.

IF the Actor–Event Association is sufficiently governed, THEN the
actor may be represented as a Governed Event Participant.

EPAM SHALL NOT convert Event Participation into taxpayer status,
accountability, liability, or another jurisdiction-specific legal
conclusion.

Minimum Implementation Framework

A minimum EPAM implementation should support:

Governed Event Reference

The specific governed event to which association is evaluated.

Participant Candidate Reference

The EPIM-governed actor.

Participation Role Reference

The EPRM-governed operational role.

Association Identifier

The stable reference for the Actor–Event Association.

Association Type

The operational nature of the association.

Association Basis

The basis supporting material association.

Association Materiality

Whether the relationship is materially relevant to Event
Participation.

Association Directness

Whether the relationship is direct, indirect, supporting, or
otherwise qualified.

Temporal Association

The relationship between participation and governed Event Timing.

Spatial Association

The relationship between participation and governed Event
Location where relevant.

Association Confidence

The qualified confidence attached to the association.

Association Ambiguity State

Whether participation remains materially ambiguous.

Association Conflict State

Whether material association conflicts exist.

Association Change State

Whether the Actor–Event relationship materially changes.

Evidence / Traceability Reference

The information required to reconstruct the association result.

Governance State

The current EPAM state.

Handoff State

Whether the association is sufficiently governed for subsequent
TREPS processing.

Governance Outputs

EPAM may produce: Governed Actor–Event Association; Governed
Event Participant; Association Type; Association Materiality
State; Direct Association Representation; Indirect Association
Representation; Supporting Association Representation; Temporal
Association Record; Spatial Association Record; Association
Confidence State; Association Ambiguity State; Association
Conflict State; Association Change Record; Association
Traceability Record; and the principal output:

Governed Actor–Event Association Set

This output represents actors whose relationships to the specific
event have been sufficiently governed.

Critical Distinctions

Actor Association ≠ Event Participation by
Default

Actor Record Presence ≠ Actor–Event
Association

Event Connection ≠ Material Event
Participation

Indirect Association ≠ Non-Participation
by Default

Direct Technical Connection ≠ Material
Participation by Default

Supporting Association ≠ Governed Event
Participation by Default

Governed Role ≠ Event Participation by
Default

Temporal Proximity ≠ Event Participation
by Default

Spatial Presence ≠ Event Participation by
Default

Remote Actor ≠ Non-Participant by Default

Transaction Record Presence ≠ Event
Participation by Default

Transaction Record Absence ≠
Non-Participation by Default

Contractual Party ≠ Event Participant by
Default

Non-Contractual Actor ≠ Non-Participant by
Default

Owner ≠ Event Participant by Default

Corporate Relationship ≠ Shared Event
Participation

Platform Presence ≠ Event Participation by
Default

Machine Association ≠ Owner Association

AI Agent Association ≠ Developer
Association

Multiple Actor Associations ≠ Equal
Participation

Actor–Event Association ≠ Identity
Governance

Participation Role ≠ Actor–Event
Association

Governed Actor–Event Association ≠
Accountability

Event Participation ≠ Liability

Actor–Event Association ≠ Value
Association

Event Participant ≠ Value Owner by Default

Governed Event Participant ≠ Taxpayer
Enterprise Application

EPAM establishes the material connection between governed actors
and the specific event:

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 — Machine & Autonomous Actor Governance

→ EPCM — Participation Continuity

→ Governed Participatory Event

This prevents downstream tax and compliance systems from treating
every actor appearing in operational data as an Event
Participant. Use Case 1 — Global Digital Commerce Event

A digital purchase contains records relating to a customer,
merchant, marketplace, payment processor, cloud provider,
analytics provider, logistics company, and several technical
services.

EPIM identifies the relevant Participant Candidates and EPRM
establishes their possible operational roles.

EPAM then determines which of those actors possess a materially
relevant relationship to the specific governed event.

A cloud provider appearing in infrastructure records or an
analytics service receiving technical data does not automatically
become a Governed Event Participant.

The resulting Actor–Event Association structure provides
downstream tax systems with a governed representation of actual
operational participation rather than an unfiltered list of
technically connected entities. Use Case 2 — Autonomous
Industrial Procurement Event

An AI agent detects a production requirement, evaluates
suppliers, initiates procurement, and communicates with an
autonomous logistics system.

A manufacturing robot later receives and uses the component.

The AI developer, robot manufacturer, equipment owner, cloud
provider, operating company, supplier, and monitoring systems may
all appear in available records.

EPAM determines which governed roles materially associate which
actors with the specific event.

Ownership, development, technical hosting, or monitoring alone
does not automatically establish Event Participation.

The resulting associations can proceed to specialized machine and
autonomous participation governance without prematurely
determining responsibility, liability, taxpayer status, or
another legal consequence.

Canonical Boundary

EPAM owns the governance of the material relationship between
governed Participant Candidates, their governed operational
roles, and a specific Tax-Relevant Event, including association
basis, materiality, directness, supporting association, temporal
and spatial relevance, uncertainty, conflict, change, and
traceability.

EPAM does not own Participant Identification, Participation Role
definition, complete identity governance, specialized Machine &
Autonomous Actor governance, Participation Continuity, Event
Timing, Event Location, Value Association, Event Relationships,
accountability, responsibility, liability, ownership, authority,
taxpayer status, Tax Jurisdiction, tax nexus, permanent
establishment, place of supply, taxability, Tax Liability, or
another jurisdiction-specific legal conclusion.

Its governance ends when the Actor–Event relationship is
sufficiently established for subsequent TREPS governance.

Canonical Handoff

EPIM — Governed Participant Candidate Set

→ EPRM — Governed Participant Role Set

→ EPAM — Governed Actor–Event Association Set

→ EPMAM — Event Machine & Autonomous Actor Governance

Canonical Closing Statement

EPAM establishes whether an identified actor and its governed
operational role materially belong to the specific event — not
what legal consequence follows from that participation.

Being connected to an event is not the same as participating in
it. Being a participant is not the same as being legally
responsible or taxable.

Governed Event Participant ≠ Taxpayer.