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: ERLKM — Event Record Linkage Module
Operational Layer: Event Record Linkage Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Core Module
Governed Space: Event Record Linkage
Primary Governed Object: Governed Event Record Linkage State
Origin ID: TREGA-TREGS-ERLKM-003
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 Linkage Module (ERLKM) governs how a
structurally governed Tax-Relevant Event Record is linked to the
Event, related Event Records, upstream governance states,
supporting records, predecessor or successor representations, and
other materially relevant references required to preserve
reconstructability and downstream usability.

Its principal transition is:

Governed Event Record Structure

↓

Event Record Linkage Governance

↓

Governed Event Record Linkage State

ERLKM governs the relationship between records and references.

It does not recreate the substantive Event Relationships governed
by TRERLS.

Its foundational distinction is:

Record Linkage ≠ Event Relationship Governance.

Operational Role

A structurally complete Event Record may still be operationally
weak if it cannot be reliably connected to the objects and
governance states that give it meaning.

ERLKM answers:

Which records, Events, governance states, and materially relevant
references must this Event Record remain linked to in order to
preserve its governed meaning?

Its role is to prevent: isolated records; broken Event
references; lost predecessor or successor relationships; detached
Determination states; disconnected supporting records; ungoverned
duplicate links; ambiguous cross-system associations; and silent
link loss during transformation.

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

ERLKM receives:

Governed Event Record Structure

and produces:

Governed Event Record Linkage State

for ERTM.

Operational Transition

The canonical transition is:

Governed Event Record Structure

↓

Link Requirement Identification

↓

Link Establishment

↓

Link Qualification

↓

Link Validation State

↓

Governed Event Record Linkage State Operational Space

ERLKM governs: Event-to-Record linkage; Record-to-Record linkage;
upstream governance references; Determination references;
qualification references; uncertainty references; reconsideration
references; predecessor links; successor links; related-record
links; supporting-record links; duplicate-record associations;
Merge/Split references; cross-system references; link type; link
direction; link scope; link materiality; link validity state;
link continuity; link conflict; link correction; link
supersession; and linkage handoff.

Operational Scope

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

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

Linkage Object

The linkage object is a governed association between the Event
Record and another materially relevant governed object or
reference.

A link may connect the Record to: the underlying Event; another
Event Record; an upstream governance result; a supporting
technical record; a predecessor representation; a successor
representation; or another relevant reference.

Link Object ≠ Event Relationship by default.

Link Requirement Identification

ERLKM shall identify which links are materially required for the
Event Record to remain reconstructable and usable.

Not every available connection belongs in the canonical Record
linkage layer.

Available Connection ≠ Required Governed Link.

Event-to-Record Link

The Record shall remain linked to the Determined Tax-Relevant
Event it represents.

This link is foundational.

It allows downstream systems to move from:

Record

↓

Governed Event

without reconstructing Event identity independently.

Event-to-Record Link ≠ Record Identity itself.

ERIDM owns Record identity.

Record-to-Record Link

Event Records may require association with other governed Event
Records.

Examples include: predecessor/successor Record relationships;
duplicate representations; derived representations; superseding
Records; records corresponding to related Events.

ERLKM governs these associations at the Record layer.

Upstream Governance Linkage

The Record may preserve links to relevant upstream TREGA™
outputs, including: TRECS Context; TRERS Recognition; TREFS
Formation; TREBS Boundary; TRETS Timing; TRELS Location; TREPS
Participation; TRVAS Value Association; TRERLS Event
Relationships; TREDS Determination.

ERLKM does not reproduce these governance functions.

Determination Linkage

The Event Record shall remain linked to the applicable TREDS
Determination result.

Where reconsideration has occurred, linkage should support
identification of: prior Determination; reconsideration process;
current effective Determination.

Determination Link ≠ Determination Decision.

Qualification Linkage

Material qualifications may be linked directly or through
governed references.

The Record shall not lose qualification merely because the
underlying qualification is stored elsewhere.

Referenced Qualification ≠ Missing Qualification.

Uncertainty Linkage

Where material uncertainty remains relevant to downstream
reliance, ERLKM shall support a durable link to the governed
uncertainty state.

Uncertainty Link ≠ Uncertainty Governance.

EDUM remains authoritative.

Reconsideration Linkage

Where EDREM changes the effective Determination, the Event Record
should preserve relevant linkage between:

Prior Determination

↓

Reconsideration

↓

Current Determination

Detailed chronological reconstruction belongs to ERTM.

Predecessor Link

A Record may require linkage to an earlier representation from
which it developed.

Predecessor linkage supports continuity without implying that
both records represent different Events.

Predecessor Record ≠ Prior Event by default.

Successor Link

A Record may link to a later representation that replaces or
supersedes it.

This linkage preserves continuity while keeping identities
distinct where required.

Successor Record ≠ Same Record by default.

Supporting Record Linkage

A canonical Event Record may link to supporting technical records
such as: invoices; payment records; ledger entries; logs; sensor
records; contracts; API messages; transaction receipts.

These support or represent aspects of the Event.

They do not automatically become governed Event Records.

Supporting Record ≠ Canonical Event Record.

Invoice Linkage

An invoice may be linked to a governed Event Record where
materially relevant.

This does not make the invoice authoritative over the Event.

Invoice Link ≠ Event Definition.

Payment Linkage

A payment record may be linked to the Event Record.

The payment may represent: settlement; consideration; transfer;
or partial execution.

Payment Link ≠ Event Identity.

Blockchain Linkage

A blockchain transaction may be linked as a supporting or
operational representation.

A transaction hash may provide strong technical reference quality
without defining the Event itself.

Blockchain Link ≠ Event Equivalence.

Smart-Contract Linkage

A smart-contract execution log may be linked where relevant.

The link preserves technical execution association.

It does not determine full Event meaning.

Machine-Generated Linkage

Autonomous systems may create large numbers of technical
references.

ERLKM shall avoid creating canonical links merely because records
are technically adjacent.

Machine Correlation ≠ Governed Linkage by default.

Link Type

Every material governed link should possess a distinguishable
type.

Possible link types include: Represents; Supports; Derived From;
References; Supersedes; Precedes; Succeeds; Corresponds To;
Duplicate Of; Qualification Reference; Determination Reference;
Uncertainty Reference; Governance State Reference.

Link semantics should remain explicit.

Link Direction

Where direction matters, the governed Record should distinguish
source and target.

For example:

Record B Supersedes Record A

is not equivalent to:

Record A Supersedes Record B.

Link Presence ≠ Directional Meaning.

Link Scope

A link may apply to: the entire Record; one Record component; one
Determination state; one qualification; one supporting object; or
one lifecycle transition.

The scope should be explicit where material.

Link Materiality

Not every link requires canonical preservation.

A link is materially relevant where its absence could impair:
Event reconstruction; Record meaning; Determination
interpretation; downstream reliance; lifecycle continuity; or
auditability.

More Links ≠ Better Governance by default.

Link Validity

ERLKM shall represent whether a link is: Proposed; Established;
Qualified; Ambiguous; Conflicted; Invalid; Superseded; or Closed.

A stored reference is not necessarily a valid governed link.

Stored Reference ≠ Governed Link.

Link Qualification

A link may exist with qualification.

For example: probable source association; bounded duplicate
association; unresolved cross-system mapping.

Qualification shall remain visible.

Link Conflict

Link conflict exists where materially relevant sources support
incompatible associations.

Examples include: one Record linked to two mutually exclusive
Events; conflicting predecessor references; incompatible
duplicate-record conclusions; inconsistent Determination
references.

Link Conflict ≠ Permission to Preserve Both as Equally Valid
without Qualification.

Link Ambiguity

Ambiguous linkage exists where the correct association cannot be
established sufficiently.

Ambiguous links should remain explicitly governed rather than
silently treated as established.

Duplicate Linkage

Where multiple technical records represent the same governed
Event Record, ERLKM may establish duplicate or
corresponding-record associations.

This supports deduplication and traceability.

Duplicate Representation ≠ Duplicate Event.

Merge Linkage

Where TRERLS establishes an Event Merge, TREGS Records may
require links among: pre-Merge Event Records; merged Event;
resulting governed Record.

ERLKM represents these associations.

It does not govern the Merge itself.

Merge Linkage ≠ Merge Decision.

Split Linkage

Where an Event is split, Record linkage may preserve association
between: original Event Record; resulting Event Records; Split
governance reference.

Split Linkage ≠ Split Governance.

Record Supersession Linkage

Where one Record supersedes another, ERLKM shall preserve
explicit linkage.

Supersession linkage should support: prior Record identity;
successor Record identity; effective transition; reason
reference.

TRECLS owns broader lifecycle supersession.

Correction Linkage

Where a corrected Record exists, ERLKM may preserve the
association between prior and corrected representations.

Correction Link ≠ Event Correction Decision.

Cross-System Linkage

Different systems may maintain independent local representations
associated with the same governed Record.

ERLKM may link these representations through the canonical Record
identity.

Cross-System Link ≠ Full Interoperability.

ERINM governs interoperability.

Cross-Organization Linkage

Where several organizations exchange or consume the same Event
Record, linkage may preserve associations among: canonical
Record; local organizational representation; downstream
processing object.

This supports continuity without requiring identical local
schemas.

Cross-Border Linkage

Cross-border Event Records may link to several
jurisdiction-specific evaluations.

These downstream links shall remain distinguishable from the
canonical Event Record.

Jurisdictional Evaluation Link ≠ Tax Jurisdiction Determination.

Multi-Jurisdiction Linkage

The same Event Record may support:

Governed Event Record

↓

Jurisdiction A Evaluation

Governed Event Record

↓

Jurisdiction B Evaluation

Governed Event Record

↓

Jurisdiction C Evaluation

Each downstream evaluation may be linked without becoming part of
the canonical Event definition.

Linkage Cardinality

ERLKM shall support one-to-one, one-to-many, many-to-one, and
where necessary many-to-many Record associations.

Cardinality shall reflect governed reality rather than database
convenience.

Database Relationship Type ≠ Governed Linkage Meaning.

Linkage Persistence

Material links should persist as long as they are necessary for
reconstructability or lifecycle continuity.

Deletion of a technical reference shall not automatically erase a
materially relevant governed linkage.

Linkage Continuity

Links may remain continuous across: Record transformation; system
migration; identifier change; schema change; lifecycle state
change.

Continuity shall preserve semantic meaning.

Linkage Change

A link may change because: a prior association was incorrect; a
new supporting record appeared; a Record was superseded; a
Duplicate was resolved; Merge/Split changed Event structure.

Material changes should remain governable and traceable.

Linkage Correction

Where a link is known to be incorrect, it may be corrected.

Correction shall preserve prior link state where materially
relevant.

Link Correction ≠ Silent Historical Rewrite.

Linkage Supersession

A newer link may supersede an older link.

Superseded links should remain reconstructable where materially
necessary.

Linkage Closure

Some links may cease to be operationally active while remaining
historically relevant.

Closed linkage does not mean the association never existed.

Closed Link ≠ Erased Link.

Linkage and Traceability

ERLKM establishes governed associations.

ERTM uses those associations to reconstruct lineage and
governance history.

Therefore:

Linkage ≠ Traceability.

A network of links may exist without sufficient traceability
logic.

Linkage and Interoperability

ERLKM establishes what is linked.

ERINM governs whether those links and their meanings remain
usable across systems.

Linkage ≠ Interoperability.

Linkage and Event Relationships

TRERLS governs substantive relationships among Events.

ERLKM may represent those relationships at the Record level.

It does not create, merge, split, sequence, group, or
dependency-govern Events.

Record Relationship Representation ≠ Event Relationship
Determination.

Linkage and Identity

ERIDM establishes Record identity.

ERLKM may use that identity to establish links.

It does not re-identify the Record.

Link Establishment ≠ Record Identification.

Linkage and Structure

ERSTM establishes structural capacity for links.

ERLKM governs actual linkage.

Link Field ≠ Governed Link.

Linkage and Tax Law

Links to jurisdictional evaluations, assessments, returns, or
filings do not cause TREGA™ to own those legal outcomes.

Tax Assessment Link ≠ Tax Assessment Governance.

Governance States

ERLKM may represent:

Linkage Governance Not Initiated

Link Requirement Identified

Link Candidate Identified

Link Under Evaluation

Link Established

Link Qualified

Link Ambiguous

Link Conflicted

Link Invalid

Duplicate Link Established

Predecessor Link Established

Successor Link Established

Supersession Link Established

Correction Link Established

Cross-System Link Established

Link Superseded

Link Closed

Linkage Sufficient

Governed Event Record Linkage State
Established

Ready for Traceability Governance
Governance Requirements

ERLKM implementations shall ensure that: a valid Governed Event
Record Structure exists; materially required links are
identified; Event-to-Record linkage remains preserved; Record
Linkage remains distinct from Event Relationship governance;
upstream governance references can be maintained where material;
Determination, qualification, uncertainty, and reconsideration
references remain governable; predecessor and successor links
remain distinguishable; supporting technical records remain
distinct from canonical Event Records; link type is explicit
where material; link direction is preserved where relevant; link
scope is identifiable; link materiality is assessed; stored
references do not automatically become governed links; ambiguous
and conflicted links remain visible; Duplicate representations do
not become duplicate Events; Merge/Split links do not recreate
Merge/Split governance; correction and supersession links
preserve materially relevant prior states; cross-system linkage
remains distinct from interoperability; jurisdiction-specific
evaluation links remain downstream; materially relevant links
persist sufficiently for reconstructability; link changes remain
traceable; and the resulting Governed Event Record Linkage State
is suitable for ERTM.

Governance Logic

IF no valid Governed Event Record Structure exists, THEN ERLKM
shall not establish canonical Record Linkage.

IF a link is materially necessary to reconstruct or interpret the
Event Record, THEN the link shall be represented or reliably
referenced.

IF a connection is technically present but has no governed
semantic meaning, THEN it shall not automatically qualify as a
canonical Record Link.

IF multiple technical records correspond to the same canonical
Record, THEN duplicate or corresponding-record linkage may be
established without creating multiple Events.

IF a link is materially ambiguous, THEN it shall remain qualified
or unresolved rather than treated as established.

IF materially authoritative sources support incompatible links,
THEN Link Conflict shall be established and governed explicitly.

IF one Record supersedes another, THEN predecessor/successor or
supersession linkage shall preserve continuity.

IF a link changes because of correction, Merge, Split, or
reconsideration, THEN prior materially relevant linkage shall
remain reconstructable.

IF a jurisdiction-specific evaluation is linked, THEN the linkage
shall not redefine the canonical Event Record.

IF materially required links are sufficiently established and
qualified, THEN ERLKM shall produce the Governed Event Record
Linkage State for ERTM.

Minimum Implementation Framework

A minimum ERLKM implementation should support:

Linkage Governance ID A stable identifier for the ERLKM
governance process.

Canonical Record Identifier The ERIDM-established Record
identity.

Record Structure Reference The ERSTM-governed Record Structure.

Link Identifier A stable identifier for each governed link.

Link Type Represents, Supports, References, Derived From,
Precedes, Succeeds, Supersedes, Duplicate Of, Qualification
Reference, Determination Reference, Uncertainty Reference, or
other governed type.

Source Object Reference The source side of the link.

Target Object Reference The target side of the link.

Link Direction The governed directional meaning where relevant.

Link Scope Record-wide, Component-Level, Determination-Level,
Qualification-Level, Lifecycle-Level, or other governed scope.

Link Materiality State Immaterial, Material, Critical, or
Unresolved.

Link Validity State Proposed, Established, Qualified, Ambiguous,
Conflicted, Invalid, Superseded, or Closed.

Event Reference Link The canonical association to the governed
Event.

Determination Link Reference The applicable TREDS Determination
link.

Qualification Link Reference Any material qualification link.

Uncertainty Link Reference Any EDUM uncertainty link.

Reconsideration Link Reference Any EDREM reconsideration
association.

Predecessor Record Reference Any prior Record representation.

Successor Record Reference Any later Record representation.

Supporting Record Reference(s) Invoices, payments, ledger
records, logs, contracts, or other supporting objects.

Duplicate Representation Reference Any governed duplicate or
corresponding technical representation.

Merge / Split Reference Any relevant TRERLS structural
transition.

Cross-System Reference Any materially relevant local-system
representation.

Cross-Organization Reference Any organizational representation
associated with the Record.

Jurisdictional Evaluation Reference Any downstream tax evaluation
linked to the canonical Record.

Prior Link State The previous materially relevant link state.

Link Correction Reference Any governed link correction.

Link Supersession Reference Any superseding linkage.

Link Qualification Any limitation attached to the link.

Link Conflict State Whether materially incompatible link
conclusions exist.

Link Trace Reference Minimum reference required for later ERTM
reconstruction.

Governance State The current ERLKM governance state.

Handoff State Whether linkage is sufficiently governed for ERTM.

Governance Outputs

ERLKM may produce: Event-to-Record Link; Record-to-Record Link;
Determination Link; Qualification Link; Uncertainty Link;
Reconsideration Link; Predecessor Link; Successor Link;
Supporting Record Link; Duplicate Representation Link;
Merge/Split Reference; Cross-System Link; Cross-Organization
Link; Jurisdictional Evaluation Link; Link Validity State; Link
Materiality State; Link Conflict State; Link Correction State;
Link Supersession State; Link Continuity State; and the principal
output: Governed Event Record Linkage State.

Critical Distinctions

Record Linkage ≠ Event Relationship Governance.

Link Object ≠ Event Relationship by default.

Available Connection ≠ Required Governed Link.

Event-to-Record Link ≠ Record Identity itself.

Determination Link ≠ Determination Decision.

Referenced Qualification ≠ Missing Qualification.

Uncertainty Link ≠ Uncertainty Governance.

Predecessor Record ≠ Prior Event by default.

Successor Record ≠ Same Record by default.

Supporting Record ≠ Canonical Event Record.

Invoice Link ≠ Event Definition.

Payment Link ≠ Event Identity.

Blockchain Link ≠ Event Equivalence.

Machine Correlation ≠ Governed Linkage by default.

Link Presence ≠ Directional Meaning.

More Links ≠ Better Governance by default.

Stored Reference ≠ Governed Link.

Link Conflict ≠ Permission to Preserve Both as Equally Valid
without Qualification.

Duplicate Representation ≠ Duplicate Event.

Merge Linkage ≠ Merge Decision.

Split Linkage ≠ Split Governance.

Correction Link ≠ Event Correction Decision.

Cross-System Link ≠ Full Interoperability.

Jurisdictional Evaluation Link ≠ Tax Jurisdiction Determination.

Database Relationship Type ≠ Governed Linkage Meaning.

Link Correction ≠ Silent Historical Rewrite.

Closed Link ≠ Erased Link.

Linkage ≠ Traceability.

Linkage ≠ Interoperability.

Record Relationship Representation ≠ Event Relationship
Determination.

Link Establishment ≠ Record Identification.

Link Field ≠ Governed Link.

Tax Assessment Link ≠ Tax Assessment Governance.

Enterprise Application

ERLKM creates the governed association layer that allows a
canonical Event Record to remain connected to the Event, its
governance basis, related representations, and downstream
processing objects.

The canonical enterprise path is:

ERIDM — Governed Event Record Identity

→ ERSTM — Governed Event Record Structure

→ ERLKM — Governed Event Record Linkage State

→ ERTM — Governed Event Record Traceability

→ ERINM — Governed Event Record Interoperability

→ Governed Tax-Relevant Event Record

This prevents the Event Record from becoming an isolated data
object after it enters complex system infrastructure. Use Case 1
— Cross-Border Marketplace Event Linked Across Commerce, Payment,
and Tax Systems

A marketplace Event has one canonical Governed Event Record.

The marketplace maintains an order record, the payment provider
maintains a settlement record, the ERP maintains an accounting
object, and three jurisdictions later create separate
tax-evaluation objects.

ERLKM links the canonical Event Record to the relevant supporting
technical records and downstream jurisdictional evaluations while
preserving their distinct roles.

The payment record does not become the Event.

The tax evaluations do not redefine the canonical Record.

One governed Record remains the common reference across the
infrastructure. Use Case 2 — Event Record Supersession After
Merge

Two Events previously possessed separate governed Event Records.

TRERLS later determines that the Events must be merged into one
governed Event.

TREDS produces the appropriate reconsidered Determination, and a
resulting Event Record is created.

ERLKM preserves links from the new Record to the predecessor
Records and the relevant Merge governance reference.

The prior Records remain historically reconstructable while the
new Record becomes the effective canonical representation.

Record continuity is preserved without pretending that
supersession erased the prior Record state.

Canonical Boundary

ERLKM owns the governance of Event-to-Record links,
Record-to-Record links, upstream governance references,
Determination/qualification/uncertainty/reconsideration links,
predecessor and successor links, supporting-record associations,
duplicate-representation links, Merge/Split references, link
type, direction, scope, materiality, validity, ambiguity,
conflict, continuity, correction, supersession, and establishment
of the Governed Event Record Linkage State.

ERLKM does not establish Record identity; ERIDM owns that space.

It does not define Record Structure; ERSTM owns that space.

It does not govern full Record lineage reconstruction; ERTM owns
Traceability.

It does not govern semantic preservation across systems; ERINM
owns Interoperability.

It does not recreate Event Relationships; TRERLS owns Event
Relationship Governance.

It does not govern Event lifecycle amendment, correction,
supersession, or closure; TRECLS owns those lifecycle functions.

It does not determine legal taxability, Tax Jurisdiction,
taxpayer status, Tax Base, Tax Rate, legal tax point, Tax Period,
Tax Liability, or other jurisdiction-specific tax consequences.

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

Its governance ends when materially required Record links are
sufficiently governed and the Governed Event Record Linkage State
is ready for Traceability Governance.

Canonical Handoff

ERSTM — Governed Event Record Structure

↓

ERLKM — Governed Event
Record Linkage State

↓

ERTM — Event Record Traceability
Governance

Canonical Closing Statement

ERLKM ensures that a governed Event Record remains connected to
the Event, governance states, records, and representations that
give it operational meaning without confusing those links with
the Event relationships themselves.

A Record can be richly connected and still remain one canonical
representation of one governed Event.

Record Linkage ≠ Event Relationship Governance.

Linkage ≠ Traceability.