OOF™ Origin Open Foundation™

Independent Methodological Authority

Architecture Ecosystem: Structured Reality Standards™
Architecture Family: TREGA™ — Tax-Relevant Event Governance Architecture™
Parent Standard: TREGS — Tax-Relevant Event Record Governance Standard
Module: ERSTM — Event Record Structure Module
Operational Layer: Event Record Structure Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Core Module
Governed Space: Event Record Structure
Primary Governed Object: Governed Event Record Structure
Origin ID: TREGA-TREGS-ERSTM-002
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 Record Structure Module (ERSTM) governs how an
identified Tax-Relevant Event Record is structured so that the
materially relevant meaning of the Determined Tax-Relevant Event
can be represented in a sufficiently complete, coherent, bounded,
and machine-readable form.

Its principal transition is:

Governed Event Record Identity

↓

Event Record Structure Governance

↓

Governed Event Record Structure

ERSTM determines what structural elements a governed Record must
contain or reference in order to preserve the Event meaning
established by preceding TREGA™ governance layers.

It does not recreate those upstream governance results.

Its foundational distinction is:

Record Structure ≠ Event Structure.

Operational Role

ERIDM establishes which governed Record represents the Event.

ERSTM determines how that Record must be structurally
represented.

Its core function is to ensure that the Record does not become:
too sparse to preserve Event meaning; too fragmented to be
reconstructable; overloaded with unnecessary data; detached from
its Determination state; structurally inconsistent; or dependent
on one proprietary technical schema.

The module answers:

What structure must the governed Event Record possess so that the
Determined Tax-Relevant Event remains meaningfully represented?

Internal Module Flow

TREGS operates through:

ERIDM — Event Record Identification

↓

ERSTM — Event Record
Structure

↓

ERLKM — Event Record Linkage

↓

ERTM — Event Record
Traceability

↓

ERINM — Event Record Interoperability

↓

Governed
Tax-Relevant Event Record

ERSTM receives:

Governed Event Record Identity

and produces:

Governed Event Record Structure

for ERLKM.

Operational Transition

The canonical transition is:

Governed Event Record Identity

↓

Structural Requirement
Identification

↓

Component Structuring

↓

Sufficiency Assessment

↓

Structural State

↓

Governed Event Record Structure Operational
Space

ERSTM governs: Record component identification; structural
requirement definition; mandatory and conditional components;
Record composition; field grouping; governed references;
representational sufficiency; structural completeness; structural
coherence; structural consistency; structural modularity;
representation boundaries; qualification representation;
uncertainty representation; Determination-state representation;
relationship-reference capacity; lifecycle-reference capacity;
structural extensibility; and structure handoff.

Operational Scope

ERSTM may govern Event Record structures used across: ERP
systems; commerce systems; banking infrastructure; accounting
platforms; marketplaces; tax platforms; payment systems;
distributed systems; blockchain environments; smart contracts; AI
agents; autonomous systems; industrial systems;
machine-to-machine infrastructure; cross-border platforms; and
future machine economies.

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

Structural Object

The structural object is the identified Governed Event Record
whose canonical representation must be defined.

ERSTM structures the Record.

It does not redefine the underlying Event.

Structural Object ≠ Underlying Event.

Structural Requirement Identification

ERSTM shall identify which information categories are materially
necessary for the Record to perform its TREGS function.

Requirements may include direct values or governed references.

The module should avoid indiscriminate data replication.

More Fields ≠ Better Record Structure by default.

Mandatory Components

Every governed Event Record should contain or reference, where
applicable: Canonical Record Identifier; underlying Event
Reference; Determination Reference; current Record State;
governance-state references necessary to preserve meaning;
relevant qualification state; relevant uncertainty state; and
structural governance status.

These form the minimum structural foundation.

Conditional Components

Some components are required only where materially relevant.

Examples include: Location representation; Participation
representation; Value Association; Event Relationship references;
Merge/Split references; reconsideration references; cross-system
references; or jurisdiction-neutral processing metadata.

Conditional Component ≠ Optional Irrelevance.

A component may be conditionally required where its absence would
materially distort the Event.

Reference Versus Replication

ERSTM shall distinguish between: information that should be
represented directly; and information that may be referenced from
another governed source.

The standard does not require all upstream TREGA™ data to be
copied into the Record.

Governed Reference ≠ Missing Information.

Structural Completeness

A Record is structurally complete when all materially required
components are either: represented directly; or reliably
referenced.

Structural completeness is determined by governance sufficiency,
not by maximum field population.

Structural Completeness ≠ Every Field Populated.

Structural Sufficiency

Structural Sufficiency exists where the Record structure is
sufficient to preserve the meaning and downstream usability of
the governed Event.

A Record may be structurally sufficient even where non-material
detail is absent.

Structural Coherence

Record components shall not materially contradict each other.

For example, a Record should not simultaneously represent:
incompatible Determination states; contradictory Event
references; incompatible Record states; or mutually exclusive
qualification states

without explicitly governing that conflict.

Data Presence ≠ Structural Coherence.

Structural Consistency

The Record should apply the same structural meaning consistently
across equivalent representations.

Consistency includes: field semantics; state semantics;
identifier usage; component relationships; and reference logic.

Record Composition

The Record may be composed of: core components; conditional
components; embedded substructures; external references; state
objects; and governed metadata.

ERSTM governs their canonical function, not their physical
storage implementation.

Core Record Component

A Core Record Component is structurally necessary for the Record
to remain identifiable and interpretable.

Core components should not be removable without materially
affecting the Record's governance function.

Supporting Record Component

Supporting components provide additional governed context without
defining the Record identity itself.

They may include: technical references; implementation metadata;
supporting source references; processing metadata; or
non-material extensions.

Structural Modularity

ERSTM may permit modular Record structures where different Event
classes require different component sets.

Modularity shall preserve a common canonical core.

Modular Structure ≠ Fragmented Governance.

Event Reference Structure

The Record shall structurally preserve the association with the
Determined Tax-Relevant Event.

The Event Reference should be distinguishable from: Record ID;
transaction ID; document ID; external tax ID.

Event Reference ≠ Record Identifier.

Determination Reference Structure

The Record shall contain or reference the applicable TREDS
Determination state.

This may include: final Decision state; qualification;
uncertainty; reconsideration result.

ERSTM represents the Determination state structurally.

It does not govern that Determination.

Qualification Structure

Where TREDS produces a qualification, ERSTM shall preserve a
structural location for that qualification.

The Record shall not collapse:

Conditional Determination

↓

Unqualified Record

through omission.

Structural Omission ≠ Qualification Removal.

Uncertainty Structure

Where material uncertainty remains, the Record should preserve an
explicit structural representation or reference.

The uncertainty shall not disappear merely because the Record is
finalized.

Record Finalization ≠ Uncertainty Elimination.

Participation Representation

Where Participation is materially relevant to downstream
interpretation, the Record should contain or reference the
governed Participation result.

ERSTM does not determine participant identity or taxpayer status.

Timing Representation

The Record may structurally preserve: Event Start; Event
Completion; Event Duration; Temporal Order; or relevant Event
Time references.

These remain operational Event times.

Record Time Field ≠ Legal Tax Point.

Location Representation

The Record may preserve governed physical, digital, or
distributed Location results.

This does not establish Tax Jurisdiction.

Location Component ≠ Jurisdiction Component.

Value Representation

The Record may preserve the governed Value Association
established by TRVAS.

ERSTM does not calculate: Tax Base; taxable amount; valuation
under tax law.

Value Representation ≠ Tax Base Representation.

Relationship Representation Capacity

The Record structure should support references to Event
Relationships governed by TRERLS.

ERSTM provides the structural capacity.

ERLKM later governs actual Record linkage.

Relationship Capacity ≠ Relationship Linkage.

Merge and Split Representation

Where Events have been merged or split, the Record structure
should support the resulting governance references.

ERSTM does not govern the Merge or Split decision.

Reconsideration Representation

Where EDREM has changed the effective Determination state, the
Record structure should support representation of: current state;
prior state reference; reconsideration reference; supersession
relationship where relevant.

Detailed traceability belongs to ERTM.

Record State Representation

The structure shall support clear representation of Record state.

Possible Record states may include: Draft; Structurally
Incomplete; Structurally Sufficient; Qualified; Active;
Superseded; Archived; Ready for Lifecycle Governance.

These states shall remain distinguishable from Event
Determination states.

Record State ≠ Determination State.

State Separation

Different governance dimensions shall not be collapsed into one
generic status field where that would create ambiguity.

For example: Record State; Determination State; Uncertainty
State; Lifecycle State

should remain conceptually distinguishable.

One Status Field ≠ Complete Governance State by default.

Structural Boundaries

The Record should have a clear structural boundary defining which
components belong to the canonical governed Record and which are
external references.

This prevents uncontrolled technical metadata from becoming part
of the canonical Event representation.

Structural Extensibility

The Record should support extensions without destabilizing its
canonical meaning.

Extensions may support: sector-specific needs;
implementation-specific fields; jurisdiction-specific downstream
references; future technologies.

Extensions shall not redefine the canonical TREGA™ Event.

Extension ≠ Canonical Redefinition.

Jurisdiction-Specific Extension Boundary

A jurisdiction may append: tax classification; tax codes; filing
references; tax base; rate; exemption; legal treatment.

These fields remain downstream extensions.

They should not become part of the canonical jurisdiction-neutral
TREGS Record structure by default.

Schema Independence

ERSTM does not require one universal technical schema.

The governed structure may be implemented through: relational
databases; JSON; XML; graph structures; event streams;
distributed ledgers; object stores; semantic models; or future
data systems.

Canonical Structure ≠ Mandatory Technical Schema.

Schema Mapping Boundary

Mapping the canonical structure into specific system schemas may
be necessary.

ERSTM defines the structural meaning.

ERINM governs broader interoperability.

Data-Type Flexibility

Different technical implementations may represent the same
governed concept using different data types.

ERSTM requires semantic preservation rather than identical
physical encoding.

Record Granularity

The Record structure shall correspond to the governed Event
granularity.

It shall not fragment or aggregate Events merely because a system
prefers a particular storage model.

Storage Granularity ≠ Event Granularity.

Nested Records

Some complex Events may require nested structural
representations.

Nested structures may be used where they preserve: Event
hierarchy; components; relationship references; or conditional
data.

Nested technical structures do not automatically create separate
governed Events.

Distributed Record Structure

A governed Event Record may be physically distributed across
multiple systems.

ERSTM permits distributed representation where: canonical
identity remains stable; required structural components remain
reconstructable; and governance meaning remains coherent.

Distributed Storage ≠ Distributed Record Identity.

Record Compression

Systems may compress or abstract data.

Compression shall not remove materially necessary governance
meaning.

Compact Representation ≠ Incomplete Representation.

Structural Versioning

Record structure may evolve over time.

Versioning shall preserve: semantic continuity; interpretability;
canonical identity association; and historical reconstruction.

Schema Version Change ≠ New Governed Event.

Backward Compatibility

Where structure versions change, older Record representations
should remain interpretable where material to historical
continuity.

ERSTM does not require indefinite technical compatibility, but it
does require governance interpretability.

Forward Extensibility

Future components may be added where new system types or
governance requirements emerge.

Extensions should not invalidate the canonical core.

Structural Validation Boundary

ERSTM may assess structural sufficiency and coherence.

It does not perform general validation governance.

VALIDOS™ remains authoritative for validation.

Structural Sufficiency ≠ Validation.

Structural Integrity Boundary

ERSTM requires internally coherent representation.

Broader integrity governance belongs to INTEGROS®.

Structural Coherence ≠ General Integrity Certification.

Traceability Boundary

ERSTM provides fields or references necessary for later
traceability.

ERTM governs the actual Record Traceability space.

Traceability Capacity ≠ Traceability Governance.

Linkage Boundary

ERSTM provides structural slots for links.

ERLKM governs the creation and governance of those links.

Link Field ≠ Governed Linkage.

Interoperability Boundary

ERSTM establishes canonical structural meaning.

ERINM governs preservation of that meaning across systems and
organizations.

Canonical Structure ≠ Interoperability Completion.

Governance States

ERSTM may represent:

Structure Governance Not Initiated

Structural Requirements Identified

Core Components Defined

Conditional Components Identified

Structure Under Construction

Structure Incomplete

Structure Ambiguous

Structure Conflicted

Structure Coherent

Structure Sufficient

Structure Qualified

Structure Ready for Linkage Governance

Governed Event Record Structure
Established Governance Requirements

ERSTM implementations shall ensure that: a valid Governed Event
Record Identity exists; Record Structure remains distinct from
Event Structure; structurally required components are identified;
mandatory and conditional components remain distinguishable;
material components are represented or reliably referenced;
Record completeness does not require indiscriminate data
replication; Event Reference remains structurally distinguishable
from Record Identifier; Determination state is structurally
preserved; qualifications are not removed through omission;
material uncertainty remains representable; Participation,
Timing, Location, Value, and Relationship information is
represented only where materially required; tax-law conclusions
remain downstream extensions; Record State remains distinct from
Determination State; state dimensions are not collapsed where
this creates ambiguity; canonical structure remains
technology-neutral; schema differences do not automatically
create governance differences; structure can support extension
without redefining the canonical Event; record granularity
follows governed Event granularity; distributed representation
remains reconstructable; structural versioning preserves semantic
continuity; structural sufficiency remains distinct from
validation; structural coherence remains distinct from general
integrity governance; linkage, traceability, and interoperability
remain delegated to their respective modules; and the resulting
Governed Event Record Structure is suitable for ERLKM.

Governance Logic

IF no valid Governed Event Record Identity exists, THEN ERSTM
shall not establish a canonical Record Structure.

IF a materially necessary component is neither represented nor
reliably referenced, THEN the Record Structure shall remain
incomplete.

IF a component is not materially required, THEN its absence shall
not automatically make the Record incomplete.

IF upstream governance information can be reliably referenced,
THEN ERSTM shall not require unnecessary duplication.

IF structural components materially contradict each other, THEN
the structure shall not be considered coherent until the conflict
is governed.

IF a Determination qualification exists, THEN the Record
Structure shall preserve that qualification explicitly or by
reliable reference.

IF material uncertainty exists, THEN the Record Structure shall
provide a governed representation or reference for it.

IF a jurisdiction-specific tax field is added, THEN it shall
remain distinguishable from the canonical jurisdiction-neutral
Record structure.

IF system schema changes while the governed Event meaning remains
stable, THEN Record Structure continuity may remain intact.

IF the structure preserves the materially necessary Event meaning
and supports downstream linkage, traceability, and
interoperability, THEN ERSTM shall establish the Governed Event
Record Structure.

Minimum Implementation Framework

A minimum ERSTM implementation should support:

Record Structure Governance ID A stable identifier for the ERSTM
governance process.

Canonical Record Identifier The ERIDM-established Record
identity.

Determined Event Reference The underlying governed Event.

Structural Version The active canonical Record structure version.

Core Component Set The structurally mandatory Record components.

Conditional Component Set Components required only under
specified governance conditions.

Event Reference Component The canonical reference to the
underlying Event.

Determination Reference Component The applicable TREDS
Determination state.

Record State Component The current TREGS Record state.

Qualification Component Any material Determination qualification.

Uncertainty Component Any material governed uncertainty or
reference.

Timing Representation Relevant Event Timing reference where
required.

Location Representation Relevant Event Location reference where
required.

Participation Representation Relevant governed Participation
reference where required.

Value Association Representation Relevant TRVAS output where
required.

Relationship Representation Capacity Structural capability to
support ERLKM linkage.

Reconsideration Reference Relevant EDREM state where applicable.

Prior Structure Version Reference The previous structural version
where applicable.

Extension Reference Any implementation or sector-specific
extensions.

Jurisdiction-Specific Extension State Whether downstream
jurisdictional fields are attached separately.

Structural Completeness State Incomplete, Partial, Complete, or
Qualified.

Structural Coherence State Coherent, Ambiguous, Conflicted, or
Unresolved.

Structural Sufficiency State Insufficient, Conditionally
Sufficient, or Sufficient.

Governance State The current ERSTM governance state.

Handoff State Whether the Record is ready for ERLKM.

Governance Outputs

ERSTM may produce: Structural Requirement Set; Core Component
Set; Conditional Component Set; Event Reference Structure;
Determination Representation; Qualification Representation;
Uncertainty Representation; Record State Representation; Value
Representation; Participation Representation; Timing
Representation; Location Representation; Relationship
Representation Capacity; Structural Completeness State;
Structural Coherence State; Structural Sufficiency State;
Structural Version Reference; Extension State; and the principal
output: Governed Event Record Structure.

Critical Distinctions

Record Structure ≠ Event Structure.

Structural Object ≠ Underlying Event.

More Fields ≠ Better Record Structure by default.

Conditional Component ≠ Optional Irrelevance.

Governed Reference ≠ Missing Information.

Structural Completeness ≠ Every Field Populated.

Data Presence ≠ Structural Coherence.

Modular Structure ≠ Fragmented Governance.

Event Reference ≠ Record Identifier.

Structural Omission ≠ Qualification Removal.

Record Finalization ≠ Uncertainty Elimination.

Record Time Field ≠ Legal Tax Point.

Location Component ≠ Jurisdiction Component.

Value Representation ≠ Tax Base Representation.

Relationship Capacity ≠ Relationship Linkage.

Record State ≠ Determination State.

One Status Field ≠ Complete Governance State by default.

Extension ≠ Canonical Redefinition.

Canonical Structure ≠ Mandatory Technical Schema.

Storage Granularity ≠ Event Granularity.

Distributed Storage ≠ Distributed Record Identity.

Compact Representation ≠ Incomplete Representation.

Schema Version Change ≠ New Governed Event.

Structural Sufficiency ≠ Validation.

Structural Coherence ≠ General Integrity Certification.

Traceability Capacity ≠ Traceability Governance.

Link Field ≠ Governed Linkage.

Canonical Structure ≠ Interoperability Completion.

Enterprise Application

ERSTM provides the structural layer that converts an identified
Record into a governed representation capable of being linked,
traced, exchanged, and later maintained.

The canonical enterprise path is:

ERIDM — Governed Event Record Identity

→ ERSTM — Governed Event Record Structure

→ ERLKM — Governed Event Record Linkage

→ ERTM — Governed Event Record Traceability

→ ERINM — Governed Event Record Interoperability

→ Governed Tax-Relevant Event Record

This allows organizations to use different technologies while
preserving one canonical Event meaning. Use Case 1 — Cross-Border
Marketplace Record with Conditional Location Data

A marketplace Event has completed TREDS and ERIDM has established
the canonical Record identity.

The Event contains fully governed: Formation; Participation;
Value Association; and Determination.

Its distributed digital Location remains qualified.

ERSTM creates the governed Record structure with: Record
Identifier; Event Reference; Determination Reference;
Participation reference; Value Association reference; Location
qualification; and current Record State.

The Record does not duplicate all TREGA™ data and does not remove
the Location qualification.

It remains structurally sufficient for downstream Record Linkage
and later jurisdiction-specific evaluation. Use Case 2 —
Autonomous Machine Event Across Heterogeneous Systems

An autonomous industrial Event is represented across an ERP
platform, machine-control system, payment infrastructure, and
AI-agent environment.

Each system uses a different schema.

ERIDM has already established one canonical Record identity.

ERSTM defines the canonical structural meaning required across
those representations, including: Event Reference; Determination
state; relevant Participation; Value Association; material
machine context; and Record State.

Each system may implement the structure differently.

The underlying governed meaning remains consistent.

Different Schemas

↓

One Governed Record Structure.

Canonical Boundary

ERSTM owns the governance of Record structural requirements,
mandatory and conditional components, Record composition,
material representation, structural completeness, sufficiency,
coherence, consistency, modularity, Event and Determination
representation, qualification and uncertainty representation,
state separation, structural extensibility, schema independence,
structural versioning, and establishment of the Governed Event
Record Structure.

ERSTM does not establish canonical Record identity; ERIDM owns
that function.

It does not govern actual Record links; ERLKM owns linkage.

It does not govern complete Record lineage; ERTM owns
traceability.

It does not govern cross-system semantic exchange; ERINM owns
interoperability.

It does not recreate upstream TREGA™ Event governance and does
not determine legal tax consequences.

Its governance begins when a valid Governed Event Record Identity
exists.

Its governance ends when a sufficiently coherent and complete
Governed Event Record Structure is established for Record Linkage
Governance.

Canonical Handoff

ERIDM — Governed Event Record Identity

↓

ERSTM — Governed Event
Record Structure

↓

ERLKM — Event Record Linkage Governance

Canonical Closing Statement

ERSTM ensures that a governed Event Record contains enough
structure to preserve what the Event means without forcing every
system to store the Event in the same way.

The structure must be complete enough to govern the Record, but
never so rigid that the technical schema becomes the Event
itself.

Record Structure ≠ Event Structure.

Canonical Structure ≠ Mandatory Technical Schema.