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: EPRM — Event Participation Role Module
Operational Layer: Event Participation Role Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Core Module
Governed Space: Event Participation Role
Origin ID: TREGA-TREPS-EPRM-002
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 Role Module (EPRM) governs how
operational participation roles associated with Participant
Candidates are identified, differentiated, qualified, and
represented within a Tax-Relevant Event before final Actor–Event
Association is established.

EPRM determines the operational function through which an
identified Participant Candidate may participate in the governed
event.

Its principal task is: Governed Participant Candidate

↓

Governed
Participation Role

EPRM does not determine whether the actor is legally a seller,
buyer, taxpayer, taxable person, employer, employee, principal,
agent, permanent establishment, beneficial owner, withholding
party, liable party, or another jurisdiction-specific legal
actor.

The foundational distinction is: Operational Participation Role ≠
Legal Tax RoleOperational Role

EPIM establishes which actor is under participation governance.

EPRM establishes what operational function that actor performs in
relation to the event.

Modern events may involve multiple actors whose functions cannot
be accurately represented through simple labels such as buyer and
seller.

An actor may initiate an activity, provide a service, operate
infrastructure, authorize an action, transfer an object, execute
a process, receive an output, coordinate another actor, or
perform several operational functions within the same event.

EPRM provides a governed representation of those operational
roles before legal interpretation begins.

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

EPRM receives the Governed Participant Candidate Set from EPIM.

It produces governed participation-role information for
subsequent Actor–Event Association governance.

Operational Transition

The canonical EPRM transition is:

Governed Participant Candidate Set

→ Participation Role Governance

→ Governed Participant Role Set

The output describes the operational roles potentially performed
by identified Participant Candidates.

It does not yet establish final governed participation in the
event.

Operational Space

EPRM governs: participation-role identification; role
differentiation; role qualification; multi-role participation;
shared roles; sequential roles; simultaneous roles; supporting
versus material operational roles; role ambiguity; role conflict;
role changes; role traceability; human roles; organizational
roles; digital roles; machine roles; and autonomous operational
roles.

EPRM governs the operational function of the actor.

It does not govern the actor's complete identity or
jurisdiction-specific legal classification.

Operational Scope

EPRM may govern roles across: commercial transactions;
manufacturing; logistics; financial operations; digital services;
platforms; marketplaces; infrastructure operations;
machine-to-machine activity; autonomous procurement; AI-mediated
transactions; robotic operations; hybrid physical-digital events;
and other governable economic or operational events.

Role governance shall remain neutral to technology, industry, and
jurisdiction.

Operational Participation Role

An Operational Participation Role describes the materially
relevant function through which a Participant Candidate acts in
relation to the governed event.

Depending on operational reality, such functions may include:
initiation; provision; reception; execution; authorization;
coordination; facilitation; transfer; delivery; processing;
operation; control; intermediation; consumption; or another
materially distinguishable operational function.

These are operational representations.

They shall not automatically be interpreted as legally defined
roles.

Operational Function ≠ Legal Classification.

Role Evidence

A participation role shall be supported by information sufficient
to justify its operational representation.

Relevant information may originate from: transaction records;
operational logs; workflow records; contractual information;
system activity; platform records; machine telemetry;
communication records; authorization records; transfer records;
execution records; or other governed sources.

A label supplied by one system does not automatically establish
the governed role.

Source Role Label ≠ Governed Participation Role by Default.

Declared Role Versus Observed Role

An actor may be described under one role while operational
evidence indicates another function.

For example, a system may label an actor as a “provider,” while
the actor merely supplies infrastructure.

EPRM shall preserve the distinction between declared and
operationally supported roles.

Declared Role ≠ Observed Operational Role.

Where the distinction is materially relevant, both
representations shall remain traceable.

Material Role Versus Incidental
Involvement

Not every function associated with an event constitutes a
materially relevant participation role.

Technical, administrative, passive, incidental, or background
involvement may exist without becoming a material role in the
governed event.

Therefore:

Operational Involvement ≠ Material Participation Role by Default.

EPRM shall support differentiation between materially relevant
roles and merely incidental involvement.

Final Actor–Event Association remains governed by EPAM.

Multiple Roles

One Participant Candidate may perform more than one materially
relevant operational role.

Therefore:

One Participant Candidate

↓

Multiple Operational Roles

where operational reality supports such representation.

EPRM shall not force one actor into a single role merely because
a downstream data model expects one role field.

One Actor ≠ One Role by Default.

Shared Roles

Multiple Participant Candidates may perform the same or
overlapping operational function.

Therefore:

One Operational Role

↓

Multiple Participant Candidates

may be legitimate.

A shared role shall not automatically collapse several actors
into one participant.

Shared Role ≠ Shared Identity.

Role Granularity

Participation roles shall be represented at a level of detail
sufficient to preserve materially relevant operational
differences.

Excessive generalization may hide meaningful differences.

Excessive fragmentation may create artificial distinctions that
do not improve governance.

The role structure shall therefore reflect the actual operational
function relevant to the governed event.

More Detailed Role ≠ More Accurate Role by Default.

Role Hierarchy

Where operational reality requires it, roles may exist at
different levels.

A broad function may contain narrower operational functions.

For example:

Service Provision

↓

Processing

↓

Execution

or:

Logistics

↓

Transport

↓

Delivery

Role hierarchy may support representation but shall not
automatically create separate participants or separate events.

Role Hierarchy ≠ Event Hierarchy.

Role Sequence

Roles may occur sequentially.

One actor may initiate an event and another may subsequently
execute, transfer, process, or receive an operational result.

EPRM shall preserve materially relevant role sequencing where
necessary for participation governance.

However:

Role Sequence ≠ Event Sequence by Default.

Event Relationships remain governed by TRERLS.

Simultaneous Roles

Several actors may perform materially relevant roles at the same
time.

Likewise, one actor may perform multiple simultaneous functions.

EPRM shall permit these structures without forcing artificial
sequencing.

Simultaneous Roles ≠ Role Equivalence.

Role Change

An actor's operational role may change during the same governed
event.

A Participant Candidate may move from initiation to supervision,
from processing to transfer, or from passive availability to
active execution.

EPRM shall preserve materially relevant role changes.

Role Change ≠ New Participant by Default.

Role Change ≠ New Event by Default.

Participation continuity is subsequently governed by EPCM.

Human and Organizational Roles

Human and organizational actors may perform different operational
functions even when they are connected through employment,
ownership, delegation, or corporate relationships.

EPRM shall not automatically transfer one actor's operational
role to another related actor.

Organizational Relationship ≠ Shared Participation Role by
Default.

Employment Relationship ≠ Operational Role Equivalence.

Identity, authority, and accountability remain separate
governance spaces.

Digital Platform Roles

Digital platforms may perform materially different functions
across different events.

A platform may provide infrastructure in one event, actively
intermediate another, execute a process in another, or perform
multiple operational functions.

EPRM shall govern the role according to the specific event rather
than the generic category of the platform.

Platform Type ≠ Event Participation Role by Default.

Machine and Autonomous Roles

Machines, AI agents, robots, and autonomous systems may perform
operational functions independently of the roles performed by
their owners, developers, operators, or supervising
organizations.

EPRM shall allow such functions to be represented without
automatically attributing them to another actor.

Machine Function ≠ Owner Function.

AI Agent Function ≠ Developer Function.

Autonomous Execution Role ≠ Human Supervision Role.

Special governance of machine and autonomous participation is
subsequently provided by EPMAM.

Infrastructure Roles

Infrastructure may support an event without materially
participating in it.

A server, network, cloud environment, payment rail, warehouse,
communication system, or other infrastructure component may
enable an event while remaining merely supporting infrastructure.

Therefore:

Infrastructure Support ≠ Material Participation Role by Default.

EPRM shall prevent technical presence from automatically becoming
operational participation.

Role and Event Location

The location of an actor does not determine its operational
participation role.

Likewise, the location at which a role is performed does not
redefine Event Location.

Participant Location ≠ Participation Role.

Role Performance Location ≠ Event Location Governance.

TRELS remains authoritative for Event Location.

Role and Identity

A governed identity may support role attribution, but identity
does not itself determine operational role.

Actor Identity ≠ Participation Role.

OBIDENITY® remains authoritative for identity, origin, ownership,
authority, permission, and provenance where applicable.

EPRM governs only the operational role relevant to participation
in the event.

Role and Authority

An actor may perform an operational function without possessing
legal authority for that function.

Conversely, an actor may possess authority without directly
performing the operation.

Therefore:

Operational Role ≠ Authority.

Questions of authority and permission remain outside EPRM.

Role and Accountability

Performing an operational role does not automatically establish
accountability, responsibility, fault, or liability.

Therefore:

Participation Role ≠ Accountability.

Participation Role ≠ Responsibility.

Participation Role ≠ Liability.

These conclusions require separate governance.

Role and Value

An operational role does not automatically determine value
ownership, entitlement, benefit, consideration, revenue, cost, or
tax base.

Therefore:

Participation Role ≠ Value Association.

Operational Role ≠ Value Entitlement.

TRVAS governs Value Association after TREPS.

VFM® governs the Value Lifecycle.

Role and Tax Classification

Jurisdictions may subsequently interpret operational
participation roles under legal categories.

The same governed operational role may produce different legal
classifications under different tax systems.

Therefore:

One Governed Operational Role

↓

Multiple Possible Jurisdictional
Interpretations

EPRM preserves the operational role independently from those
interpretations.

It does not determine: taxpayer; supplier under tax law; taxable
person; marketplace facilitator; withholding agent; employer;
employee; principal; legal agent; permanent establishment;
importer; exporter; beneficial owner; or another
jurisdiction-specific legal status.

Role Uncertainty

Where available information supports more than one plausible
operational role, EPRM shall preserve uncertainty.

Role Uncertainty ≠ Permission for Arbitrary Role Selection.

A role shall not be chosen merely because it produces a preferred
downstream legal or tax result.

Role Conflict

Different sources may assign incompatible roles to the same
Participant Candidate.

EPRM shall preserve material conflict until sufficient governance
supports resolution.

Role Conflict ≠ Permission for Convenient Legal Classification.

Original source representations shall remain traceable where
materially relevant.

Role Confidence

Operational role representation may carry different levels of
confidence.

EPRM shall permit roles to remain qualified where evidence does
not support full certainty.

A downstream system requirement for a role field shall not
override this requirement.

Required Role Field ≠ Permission to Manufacture Role Certainty.

Role Traceability

A governed role shall remain reconstructable.

The governance structure should permit determination of: which
Participant Candidate the role concerns; which operational
function was represented; which information supported the role;
whether the role was declared, observed, derived, or otherwise
established; whether uncertainty or conflict existed; whether the
role changed; and what governance state applied.

Role traceability supports subsequent Actor–Event Association
without replacing it.

Governance States

EPRM may represent states including:

Role Ready

Role Under Governance

Role Qualified

Role Established

Multi-Role

Shared Role

Role Changed

Role Ambiguous

Role Conflicted

Role Unresolved

These states describe participation-role governance only.

They do not establish final Event Participation.

Governance Requirements

EPRM implementations shall ensure that: roles are associated with
governed Participant Candidates; operational functions are
distinguished from legal classifications; source role labels are
not automatically authoritative; declared and observed roles can
be differentiated; material roles can be distinguished from
incidental involvement; one actor may hold multiple roles;
multiple actors may share a role; role granularity remains
operationally justified; sequential and simultaneous roles can be
represented; material role changes remain traceable; human,
organizational, digital, machine, and autonomous roles can be
represented; infrastructure support does not automatically become
participation; role uncertainty remains visible; role conflicts
remain visible; role evidence remains traceable; roles do not
determine identity, authority, accountability, liability, or
value entitlement; roles do not determine taxpayer status; and
final Actor–Event Association remains downstream.

Governance Logic

IF a Governed Participant Candidate exists, THEN operational
functions potentially relevant to Event Participation may be
evaluated.

IF an operational function is sufficiently supported, THEN a
Governed Participation Role may be established.

IF one Participant Candidate performs multiple materially
distinct functions, THEN multiple roles may be preserved.

IF multiple Participant Candidates perform the same function,
THEN shared role representation may be preserved without merging
actors.

IF role evidence is uncertain or conflicting, THEN the role shall
remain appropriately qualified.

IF the operational role is sufficiently governed, THEN it may
proceed to Actor–Event Association governance.

EPRM SHALL NOT convert an operational participation role into a
jurisdiction-specific legal or tax role.

Minimum Implementation Framework

A minimum EPRM implementation should support:

Governed Event Reference

The governed event within which role governance occurs.

Participant Candidate Reference

The EPIM-governed actor to whom the role relates.

Participation Role Identifier

The stable reference for the governed role.

Operational Role Type

The operational function represented.

Role Source

The source supporting the role representation.

Role Basis

The operational basis upon which the role is attributed.

Role Materiality State

Whether the function is materially relevant to participation
governance.

Role Multiplicity State

Whether the Participant Candidate performs multiple roles.

Shared Role State

Whether the same role is performed by multiple Participant
Candidates.

Role Sequence State

Where materially relevant, the role's position relative to other
operational roles.

Role Change State

Whether the role materially changes during the event.

Role Confidence

The qualified confidence attached to the role.

Role Ambiguity State

Whether multiple plausible role interpretations remain.

Role Conflict State

Whether material source conflicts exist.

Traceability Reference

The information required to reconstruct the role governance
result.

Governance State

The current EPRM state.

Handoff State

Whether the role is sufficiently governed for EPAM.

Governance Outputs

EPRM may produce: Governed Participation Role; Participant Role
Reference; Operational Role Type; Multi-Role Structure; Shared
Role Structure; Role Sequence Representation; Role Change Record;
Role Materiality State; Role Confidence State; Role Ambiguity
State; Role Conflict State; Role Traceability Record; and the
principal output:

Governed Participant Role Set

This output provides the operational role structure required by
EPAM.

It does not establish final Actor–Event Association.

Critical Distinctions

Operational Participation Role ≠ Legal Tax
Role

Participant Identification ≠ Participation
Role

Participant Candidate ≠ Participation Role

Operational Function ≠ Legal
Classification

Source Role Label ≠ Governed Participation
Role by Default

Declared Role ≠ Observed Operational Role

Operational Involvement ≠ Material
Participation Role by Default

One Actor ≠ One Role by Default

Shared Role ≠ Shared Identity

More Detailed Role ≠ More Accurate Role by
Default

Role Hierarchy ≠ Event Hierarchy

Role Sequence ≠ Event Sequence by Default

Role Change ≠ New Participant by Default

Role Change ≠ New Event by Default

Platform Type ≠ Event Participation Role
by Default

Machine Function ≠ Owner Function

AI Agent Function ≠ Developer Function

Infrastructure Support ≠ Material
Participation Role by Default

Actor Identity ≠ Participation Role

Operational Role ≠ Authority

Participation Role ≠ Accountability

Participation Role ≠ Liability

Participation Role ≠ Value Association

Operational Role ≠ Value Entitlement

Role Uncertainty ≠ Permission for
Arbitrary Role Selection

Required Role Field ≠ Permission to
Manufacture Role Certainty Enterprise
Application

EPRM provides the role-governance layer between actor
identification and final Actor–Event Association:

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

→ EPIM — Governed Participant Candidate Set

→ EPRM — Governed Participant Role Set

→ EPAM — Actor–Event Association

→ Remaining TREPS Modules

→ Governed Participatory Event

This enables downstream systems to understand what actors
operationally did without embedding jurisdiction-specific legal
classifications into the event record. Use Case 1 — Digital
Marketplace Participation Roles

A marketplace transaction involves a customer, merchant,
platform, payment provider, and logistics provider.

EPIM has already established the relevant Participant Candidates.

EPRM determines their operational functions based on the governed
event: one actor initiates acquisition, another provides goods,
another facilitates interaction, another processes payment, and
another performs delivery.

The marketplace is not automatically classified as the legal
supplier merely because it facilitates the transaction, and the
payment provider is not automatically treated as a taxable
intermediary merely because it processes payment.

EPRM preserves the operational roles for subsequent Actor–Event
Association and jurisdiction-specific evaluation. Use Case 2 —
Autonomous Production and Procurement

An AI agent detects a production requirement, evaluates
suppliers, selects an option, initiates procurement, and
instructs an autonomous machine system.

A robot later receives and uses the supplied component while
organizational systems supervise the broader process.

EPRM governs the distinct operational functions performed by the
AI agent, machine system, robot, supplier organization, and
supervising organization without automatically transferring
machine or autonomous functions to owners, developers, or humans.

The resulting role structure preserves what each actor
operationally did while leaving authority, responsibility,
liability, taxpayer status, and other legal conclusions to their
appropriate governance and jurisdictional layers.

Canonical Boundary

EPRM owns the identification, differentiation, qualification,
representation, multiplicity, sequencing, change, uncertainty,
conflict, and traceability of operational participation roles
associated with governed Participant Candidates.

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

Its governance ends when operational participation roles are
sufficiently governed for Actor–Event Association.

Canonical Handoff

EPIM — Governed Participant Candidate Set

→ EPRM — Governed Participant Role Set

→ EPAM — Event Actor Association Governance

Canonical Closing Statement

EPRM establishes what operational function an identified actor
performs without converting that function into a
jurisdiction-specific legal or tax role.

What an actor does in the event and what the law later calls that
actor are separate governance questions.

Operational Participation Role ≠ Legal Tax Role.