The Event Location Identification Module (ELIM)
governs how spatial

OOF™ Origin Open Foundation™

Independent Methodological Authority

Architecture Ecosystem: Structured Reality Standards™
Architecture Family: TREGA™ — Tax-Relevant Event Governance Architecture™
Parent Standard: Tax-Relevant Event Location Standard (TRELS)
Module: ELIM — Event Location Identification Module
Operational Layer: Event Location Identification Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Core Module
Governed Space: Event Location Identification
Origin ID: TREGA-TRELS-ELIM-001
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 31 August 2026
AI-Readable: Yes
Authority: OOF®
Protection: MIP® — Methodology Intellectual Property Protection
Canonical Language: English

Canonical Definition

The Event Location Identification Module (ELIM) governs how
spatial information potentially associated with a Governed
Temporally Situated Event is discovered, identified,
contextualized, differentiated, correlated, and qualified before
any specific physical, digital, distributed, or composite Event
Location is established.

ELIM creates the governed spatial-input layer required for
subsequent Event Location governance.

Its canonical task is:

to establish a coherent and traceable Governed Event Location
Signal Set representing the materially relevant spatial signals
associated with the governed event without prematurely
determining Physical Event Location, Digital Event Location,
Distributed Event Location, Tax Jurisdiction, tax nexus, place of
supply, source jurisdiction, or any other jurisdiction-specific
tax consequence.

ELIM therefore answers:

What location information legitimately belongs to the event?

It does not yet answer:

What is the final governed location of the event?

And it never answers:

Which jurisdiction has authority to tax the event?

Operational Role

A modern event may generate numerous location-bearing signals.

These may originate from physical facilities, devices, users,
machines, networks, servers, cloud regions, delivery points,
payment infrastructure, operational systems, autonomous agents,
transaction records, digital platforms, sensors, logistics
systems, or other sources.

The existence of such information does not automatically
establish Event Location.

ELIM determines which spatial signals are materially associated
with the bounded event and creates the governed location evidence
structure that subsequent TRELS modules can evaluate.

Its operational transition is:

Governed Temporally Situated Event

↓

Governed Event Location Signal Set

The module prevents downstream systems from selecting the
easiest, earliest, most commercially convenient, or legally
advantageous location signal and treating it as operational
truth.

Internal Flow

Within TRELS, ELIM occupies the first operational position:

ELIM — What spatial information legitimately belongs to the
event?

↓

ELPM — What physical location materially belongs to the
event?

↓

ELDM — What digital location materially belongs to the
event?

↓

ELDSM — How is a genuinely distributed event spatially
represented?

↓

ELCM — How are relevant event locations correlated
into a governed spatial representation?

↓

Governed Temporally and
Spatially Situated Event

ELIM therefore establishes the spatial signal foundation.

It does not perform the downstream determinations owned by ELPM,
ELDM, ELDSM, or ELCM.

Operational Space

ELIM governs the identification layer between an event that has
already been bounded and temporally situated and the subsequent
determination of its operational spatial characteristics.

Its operational space includes: physical location signals;
digital location signals; infrastructure location signals;
device-derived location signals; machine-generated location
signals; platform-recorded location signals; network-derived
location signals; transaction-associated location signals;
service-execution location signals; delivery and fulfillment
location signals; participant-associated spatial signals where
materially relevant to the event; distributed-system location
signals; autonomous-system location signals; spatial metadata;
location-source relationships; location-signal relevance;
location-signal precision; location-signal uncertainty;
location-signal ambiguity; conflicting location signals; spatial
traceability.

The module governs these signals as potential descriptors of
operational reality.

It does not assume that any one signal represents the Event
Location.

Operational Scope

ELIM shall support the identification and governance of spatial
signals associated with physical, digital, hybrid, distributed,
transactional, service-based, machine-generated, autonomous, and
value-affecting events.

The module shall be capable of distinguishing between: where an
actor is located; where an object is located; where
infrastructure is located; where a device is located; where a
system records an event; where computation occurs; where a
service executes; where goods move; where goods are delivered;
where instructions originate; where an autonomous action
executes; where payment processing occurs; where records are
stored; and where the governed event itself may operationally
occur.

These locations may coincide.

They must not be assumed to coincide. 1.
Spatial Signal Discovery

One Machine Location ≠ One Event Location.
19. Location Normalization

Spatial data may require normalization for interoperability.

Normalization may include standardized coordinates, address
structures, facility identifiers, region identifiers, or other
spatial representations.

The original location information shall remain traceable where
material.

Normalized Location ≠ Original Location Evidence.

Normalization shall improve interoperability without rewriting
the spatial evidence history of the event. 20. Location Signal
Correction

Where a spatial signal is later shown to be incorrect,
incomplete, or improperly associated, correction shall remain
traceable.

Correction shall not silently erase the previous state where
historical reconstruction is required.

Location Correction ≠ Historical Erasure.

Correction of a signal also does not automatically change the
Event Boundary or create a new event. 21. Governance Requirements

ELIM implementations shall: identify materially relevant spatial
signals; preserve signal-source traceability; distinguish signal
type from Event Location; distinguish physical, digital,
infrastructure, participant, device, machine, transaction, and
other location dimensions; preserve legitimate spatial
multiplicity; identify ambiguity and conflict; maintain
appropriate spatial precision; avoid false geographic certainty;
preserve original spatial evidence where normalization occurs;
support distributed and autonomous environments; prevent
downstream legal assumptions from redefining operational spatial
information; and produce a governed location signal set suitable
for subsequent TRELS processing.

No individual spatial signal shall become authoritative Event
Location solely because it is technically available, commercially
convenient, administratively preferred, or required by a
downstream tax system. 22. Governance Logic

ELIM follows the canonical logic:

Location information exists

↓

identify its source

↓

determine its
relationship to the governed event

↓

classify its spatial
function

↓

assess material relevance

↓

preserve precision

↓

identify ambiguity or conflict

↓

correlate legitimate signals

↓

establish Governed Event Location Signal Set.

The module deliberately stops before final Event Location
determination. 23. Minimum Implementation Framework

A minimum ELIM implementation should support:

Governed Event Reference Reference to the event received from
TRETS.

Spatial Signal Identifier Unique reference for each materially
relevant spatial signal.

Spatial Signal Type Physical, digital, infrastructure, device,
machine, participant-associated, network-derived, transactional,
logistics, service-execution, or other legitimate category.

Spatial Signal Source System, device, actor, infrastructure,
record, or evidence source producing the signal.

Spatial Representation The location information itself at the
legitimately supported precision.

Event Association Relationship between the signal and the
governed event.

Operational Function The spatial role represented by the signal.

Temporal Association Relevant relationship between the location
signal and governed Event Timing where necessary.

Precision State Level of spatial precision legitimately
supported.

Relevance State Material, contextual, supporting, weak,
redundant, excluded, or unresolved.

Ambiguity State Known ambiguity associated with the signal.

Conflict State Known conflict with other spatial signals.

Traceability Reference Evidence or governance reference
supporting reconstruction.

Governance State Current state of the signal within ELIM.

Handoff State Readiness for downstream Physical, Digital,
Distributed, and Correlation governance. 24. Governance Outputs

ELIM may produce: Spatial Signal Register; Spatial Source Map;
Spatial Relevance Assessment; Physical Signal Set; Digital Signal
Set; Infrastructure Signal Set; Machine / Autonomous Spatial
Signal Set; Spatial Precision Record; Spatial Ambiguity Record;
Spatial Conflict Record; Spatial Correlation Map; Spatial
Traceability Record; and the principal output:

Governed Event Location Signal Set

This output becomes the spatial governance input for ELPM. 25.
Critical Distinctions

Location Data ≠ Event Location

Location Signal ≠ Governed Event Location

Location Source ≠ Event-Location Authority

Participant Location ≠ Event Location

Organization Address ≠ Event Location

Device Location ≠ Event Location

Machine Location ≠ Event Location

Server Location ≠ Event Location

Cloud Region ≠ Event Location

IP Location ≠ Event Location

Payment Processing Location ≠ Event
Location

Settlement Location ≠ Event Location

Delivery Location ≠ Complete Event
Location

Digital Location Signal ≠ Physical Event
Location

Physical Location Signal ≠ Digital Event
Location

Multiple Location Signals ≠ Location
Conflict

Spatial Correlation ≠ Spatial Equivalence

Recorded Precision ≠ Proven Accuracy

Required Location Field ≠ Governed
Location Certainty

Normalized Location ≠ Original Location
Evidence

Location Correction ≠ Historical Erasure

Event Location ≠ Tax Jurisdiction

Operational Spatial Reality ≠
Jurisdictional Tax Determination 26.
Enterprise Application

ELIM can operate as the spatial-input governance layer between
operational systems and downstream taxation infrastructure.

A generalized implementation pattern is:

ERP / Commerce / Banking / Digital Platform / Logistics / Cloud /
AI Agent / Machine System

↓

Spatial Signal Discovery

↓

ELIM

↓

Governed Event Location Signal Set

↓

TRELS Location Modules

↓

Governed Event Location

↓

TREGA™ Event Layer

↓

Jurisdiction-Specific Tax Engines

This allows organizations to preserve one governed operational
representation of spatial reality while enabling multiple
downstream legal systems to interpret that reality independently.
27. Use Case 1 — Distributed Digital Marketplace

A customer initiates a digital purchase from a mobile device in
Country A.

The platform operator is established in Country B.

Authentication infrastructure operates in Country C.

The application executes through cloud regions in Countries D and
E.

Payment authorization is processed through Country F.

The customer's account contains an address in Country G.

The platform therefore contains several technically valid
location signals.

A conventional implementation may select the customer's IP
address, billing address, merchant address, or server region and
immediately treat it as transaction location.

ELIM instead identifies each materially relevant spatial signal,
records its source and operational function, preserves its
precision, and establishes its relationship to the governed
event.

It does not decide which location is the final Event Location.

It does not decide which country may tax the transaction.

The output is a Governed Event Location Signal Set that
subsequent TRELS modules can evaluate.

Complex spatial reality must be governed before it is compressed
into a legal jurisdictional conclusion. 28. Use Case 2 —
Autonomous Industrial Event

An AI-controlled production network receives a manufacturing
requirement.

Planning occurs through cloud infrastructure in one country.

A robotic production cell operates in another.

Components arrive from a separate facility.

Machine coordination uses edge infrastructure in another region.

Quality verification occurs through remote computational
infrastructure.

The finished component is transferred to an autonomous logistics
system serving another country.

Thousands of machine, sensor, infrastructure, network, and
logistics records contain location information.

ELIM identifies which spatial signals materially belong to the
governed event and distinguishes machine location, infrastructure
location, computational location, logistics location, and other
relevant spatial dimensions.

It does not allow the physical position of the AI infrastructure,
the robot, or a server to become Event Location automatically.

The location of the machine performing an action is evidence
about the event — not automatically the complete spatial identity
of the event. 29. Canonical Boundary

ELIM owns the identification, contextualization, differentiation,
relevance assessment, correlation, precision qualification,
ambiguity recognition, conflict recognition, normalization
traceability, and governance of spatial signals materially
associated with the Tax-Relevant Event.

ELIM does not determine final Physical Event Location, Digital
Event Location, Distributed Event Location, or final Event
Location Correlation.

It does not redefine Event Context, Event Recognition, Event
Formation, Event Boundary, Event Timing, Event Participation,
Participant Identity, Value Association, Event Relationships,
Event Determination, or Event Record Governance.

It does not determine Tax Jurisdiction, tax nexus, tax residence,
permanent establishment, place of supply, source jurisdiction,
customs jurisdiction, taxpayer status, legal taxability, Tax
Liability, Tax Period, Legal Tax Point, tax rate, tax
calculation, filing obligation, or any other
jurisdiction-specific tax consequence.

The canonical handoff is:

TRETS — Governed Temporally Situated Event

↓

ELIM — Governed
Event Location Signal Set

↓

ELPM — Event Physical Location
Governance

Canonical Closing Statement

ELIM establishes which spatial signals legitimately describe the
governed event before any individual address, device, machine,
server, infrastructure region, or participant location is
permitted to define where that event occurred.

ELIM identifies the locations that may describe the event — it
does not yet decide the final Event Location, and it never
decides the Tax Jurisdiction.

The Event Location Identification Module (ELIM)governs how spatial