The Event Digital Location Module (ELDM) governs how
materially relevant
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: ELDM — Event Digital Location Module
Operational Layer: Event Digital Location Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Core Module
Governed Space: Event Digital Location
Origin ID: TREGA-TRELS-ELDM-003
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: UCL — Universal Canonical Language
Canonical Definition
The Event Digital Location Module (ELDM) governs how materiallyrelevant digital spatial signals associated with a Tax-Relevant
Event are identified, differentiated, evaluated, qualified, and
assembled into a governed representation of where the event
digitally occurs, is executed, is instantiated, is processed, or
materially manifests within digital operational environments.
ELDM operates on the Governed Event Location Signal Set
established by ELIM and alongside the Governed Event Physical
Location established by ELPM.
Its canonical task is:
to establish a coherent, traceable, and operationally justified
Governed Event Digital Location without allowing IP addresses,
server positions, cloud regions, user-device locations, platform
registrations, network routes, corporate addresses, or
jurisdiction-specific legal rules to become the digital location
of the event merely because they contain geographic information.
The principal transition is:
Governed Event Location Signal Set + Governed Event Physical
Location
↓
Governed Event Digital Location
ELDM governs digital Event Location.
It does not determine Tax Jurisdiction, digital tax nexus, legal
place of supply, or any jurisdiction-specific tax consequence.
Operational Role
Digital events frequently have no single obvious geographicposition.
A transaction may be initiated from a device in one country,
authenticated by infrastructure in another, processed across
several cloud regions, executed through a platform operated from
another jurisdiction, recorded in distributed databases, and
consumed by a user located elsewhere.
An AI agent may initiate and complete an economic operation
without a human being physically present at the location where
computational execution occurs.
A machine may act physically in one country while its decision
logic, orchestration, data processing, and supporting services
operate across globally distributed digital infrastructure.
Traditional information systems frequently represent such events
through whichever geographic field is easiest to obtain: IP
address; billing country; user profile country; server region;
platform registration; device location; merchant address; or
infrastructure location.
ELDM prevents these signals from being treated as authoritative
by default.
Its purpose is to govern the digital spatial reality of the
event.
Internal Flow
Within TRELS, ELDM occupies the third 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
ELDM receives:
Governed Event Location Signal Set +
Governed Event Physical Location
and produces:Governed Event Digital Location
for subsequent distributed-location governance.Operational Space
ELDM governs the digital spatial representation of theTax-Relevant Event.
Its operational space includes: digital execution environments;
platform environments; application environments; cloud
environments; cloud regions; cloud availability zones; edge
environments; network environments; API environments; digital
service environments; virtualized infrastructure; distributed
computing environments; digital transaction environments;
machine-to-machine environments; AI-agent environments;
autonomous-system environments; device-associated digital
locations; server-associated locations; infrastructure-associated
locations; network-associated locations; digital endpoint
locations; digital resource locations; logical locations;
digital-location transitions; digital-location precision;
digital-location uncertainty; digital-location conflict;
digital-location continuity; and digital-location traceability.
ELDM governs digital location only to the extent required to
represent the operational digital reality of the event.
Operational Scope
ELDM shall support digital-location governance for: e-commerce;digital marketplaces; cloud services; SaaS; digital content;
streaming; financial technology; digital payments; banking
systems; API transactions; telecommunications; online platforms;
distributed applications; AI services; AI agents; autonomous
systems; machine-to-machine transactions; robotics; IoT; edge
computing; digital assets; virtualized infrastructure; hybrid
physical-digital systems; and future machine economies.
ELDM shall support both digitally centralized and digitally
distributed events. 1. Digital Location Candidate Identification
ELDM shall identify digital-location candidates from the Governed
Event Location Signal Set.
Candidates may include: server location; cloud region;
availability zone; edge node; network endpoint; API endpoint;
device location; IP-derived location; application environment;
platform environment; execution environment; processing
environment; storage environment; digital resource location;
logical service location; or other materially relevant digital
spatial references.
A candidate shall not become Governed Event Digital Location
merely because it is technically observable.
Digital Location Candidate ≠ Governed Event Digital Location. 2.
Constitutive Digital Location
ELDM shall determine whether a digital environment materially
participates in the constitution of the governed event.
A Constitutive Digital Location is a digital environment in which
activity forming part of the event itself is executed,
instantiated, processed, or materially realized.
This distinction prevents infrastructure merely supporting the
event from being mistaken for the digital location of the event.
Supporting Digital Infrastructure ≠ Constitutive Digital Location
by Default. 3. Digital Execution Location
Where an event involves computational execution, ELDM shall
govern the digital environment in which material event execution
occurs.
Execution may occur through: application servers; cloud
workloads; edge systems; platform services; distributed
applications; AI inference systems; autonomous agents;
smart-contract environments; machine controllers; or other
computational environments.
Digital execution shall be governed according to its role in the
event rather than the geographic location of infrastructure
alone.
Infrastructure Geography ≠ Digital Event Location by Default. 4.
Server Location
A server may participate in the event, support the event, store
event data, authenticate participants, or merely route
information.
ELDM shall determine the operational significance of the server
before its location is attributed to the event.
Server Location ≠ Event Digital Location by Default.
A server physically located in a country does not, by itself,
establish that the digital event operationally occurred in that
country.
Nor does it establish taxation authority.
5. Cloud Region Location
Cloud platforms frequently distribute workloads across regions,availability zones, and dynamic infrastructure.
A cloud region may be materially relevant where event execution
is deliberately or operationally bound to that region.
However:
Cloud Region ≠ Event Digital Location by Default.
Cloud Region ≠ Tax Jurisdiction.
Infrastructure allocation decisions made by a cloud provider
shall not automatically redefine the operational spatial identity
of the event. 6. Availability Zone and Infrastructure Instance
Location
Cloud workloads may migrate between availability zones, physical
hosts, containers, virtual machines, or other infrastructure
components.
ELDM shall distinguish the operational digital environment from
transient infrastructure implementation.
Infrastructure Instance Location ≠ Event Location by Default.
The movement of a workload between infrastructure instances shall
not automatically constitute a change in the governed digital
location of the event. 7. Edge Computing Location
Edge systems may perform material event processing near devices,
machines, users, infrastructure, or physical operations.
Where edge execution forms a constitutive part of the event, ELDM
may govern the edge environment as a relevant Digital Event
Location.
However:
Edge Node Location ≠ Complete Event Digital Location by Default.
An edge node may represent one component of a broader distributed
digital event. 8. User Device Location
A user's device may provide relevant spatial information.
However, the device may be: mobile; remotely controlled;
connected through VPN; using roaming services; operating through
proxies; shared; automated; or physically separated from the
event's principal digital execution.
Therefore:
User Device Location ≠ Event Digital Location by Default.
The operational role of the device shall be established before
its location is attributed to the event. 9. IP Address Location
IP addresses may provide evidence about network connectivity.
They shall not be treated as definitive Event Location.
IP geolocation may be affected by: VPNs; proxies; corporate
networks; carrier routing; mobile networks; cloud gateways;
content-delivery networks; network address translation; satellite
connectivity; privacy services; and inaccurate geolocation
databases.
Therefore:
IP Address ≠ Event Location.
IP Geolocation ≠ Governed Digital Location by Default.
IP-derived information may remain a governed signal with explicit
confidence and provenance. 10. Network Route Location
Digital communications may traverse infrastructure across many
countries.
Network routing can change dynamically without changing the
governed event itself.
Therefore:
Network Transit Location ≠ Event Digital Location by Default.
Packet Route ≠ Event Location.
Transit infrastructure may be recorded where operationally
material but shall not automatically become part of the
constitutive Digital Event Location. 11. API Location
An event may be initiated, mediated, executed, or completed
through APIs.
An API may possess: logical endpoint; domain; gateway; service
region; execution region; provider infrastructure; and downstream
service dependencies.
ELDM shall determine which of these are materially relevant to
the event.
API Endpoint ≠ Geographic Event Location by Default.
API Provider Location ≠ Event Digital Location by Default. 12.
Platform Location
Digital marketplaces and platforms may operate across many
jurisdictions simultaneously.
A platform may have: legal headquarters; regional offices;
infrastructure regions; user markets; seller markets; payment
entities; data centers; operational subsidiaries; and globally
distributed services.
ELDM shall not reduce these structures to a single platform
location unless operational evidence supports such representation
for the governed event.
Platform Headquarters ≠ Event Digital Location.
Platform Registration Country ≠ Event Digital Location. 13.
Digital Service Location
Digital services may be provided through distributed
infrastructure without a clear physical point of delivery.
ELDM shall govern the operational digital environment through
which the event is materially performed.
This representation may be: centralized; multi-region;
distributed; logical; hybrid; or qualified as unresolved.
Digital Service Delivery ≠ Single Geographic Location by Default.
14. Data Storage Location
Event-related data may be stored separately from where the event
is executed.
Data may also be replicated across multiple regions.
Therefore:
Data Storage Location ≠ Event Digital Location by Default.
Database Location ≠ Event Execution Location by Default.
Storage location may remain a relevant digital spatial signal but
requires independent operational qualification. 15. Processing
Location
Data processing may constitute part of the event or merely
support it.
ELDM shall determine whether processing activity belongs to the
governed Event Boundary.
Where processing is constitutive, its digital environment may
form part of the Governed Event Digital Location.
Where processing is ancillary:
Processing Location ≠ Constitutive Event Location by Default. 16.
Digital Resource Location
Digital assets, records, files, models, tokens, software
components, or other digital resources may be associated with an
event.
Their technical storage or registration position shall not
automatically establish the location of the event.
Digital Resource Location ≠ Event Digital Location by Default.
The resource's operational role must first be established. 17.
Logical Digital Location
Some digital environments are better represented through logical
rather than physical geography.
Examples include: platform tenancy; virtual network; distributed
ledger environment; application namespace; service domain;
computational cluster; autonomous-agent environment; or governed
digital operational space.
ELDM shall support logical location where geographic
representation would distort operational reality.
Digital Location ≠ Geographic Coordinate
by Default. 18. AI Agent Location
AI agents may operate across distributed computationalenvironments and interact with platforms, APIs, machines, digital
assets, and other agents.
An AI agent may possess no stable physical location.
ELDM shall therefore distinguish: agent execution environment;
orchestration environment; model execution environment; tool
environment; external service environment; and physical
infrastructure.
AI Agent Location ≠ Server Location by Default.
AI Agent Location ≠ Owner Location.
AI Agent Location ≠ User Location.
Agent identity, authority, and responsibility remain outside
ELDM. 19. Autonomous-System Digital Location
Autonomous systems may continuously migrate workloads, invoke
external services, distribute processing, and coordinate with
other systems.
ELDM shall preserve the actual digital execution structure
without artificially assigning the event to the corporate or
physical location of a supervising human.
Autonomous Execution ≠ Human Supervisor Location.
Autonomous System Location ≠ Operator Residence. 20.
Machine-to-Machine Event Location
Machine-to-machine events may involve: physical machines;
embedded controllers; edge systems; cloud services; APIs; payment
systems; AI agents; and distributed infrastructure.
ELDM governs the digital dimension of such events independently
from the physical location governed by ELPM.
A machine-to-machine event may legitimately possess both:
Governed Event Physical Location +
Governed Event Digital Location
without requiring those locations to coincide. 21. DigitalLocation Transition
The digital location of an event may change during its lifecycle.
Workloads may migrate.
Agents may invoke services in different environments.
Processing may move between edge and cloud systems.
Transactions may pass through sequential digital execution
stages.
ELDM shall preserve materially relevant transitions where they
form part of the bounded event.
Digital Location Change ≠ New Event by Default. 22. Digital
Location and Event Timing
Digital location may vary over the duration of an event.
ELDM shall support temporal association where required.
For example:
Time T1
↓
Edge Environment A
Time T2
↓
Cloud Environment B
Time T3
↓
Platform Environment C
TRETS remains authoritative for Event Timing.
ELDM governs only the spatial association.
23. Digital Location Precision
Digital spatial representation shall use only the precisionsupported by evidence and operational relevance.
Possible representations may include: specific execution
instance; service; cluster; availability zone; cloud region;
platform environment; logical environment; distributed
environment; or qualified unknown digital location.
Technical Infrastructure Precision ≠ Governed Event Location
Precision.
Greater technical detail does not automatically produce better
governance. 24. Digital Location Uncertainty
Digital environments may obscure or dynamically change
infrastructure location.
ELDM shall preserve uncertainty where the digital spatial reality
cannot legitimately be reduced further.
Permissible states may include: exact; logical; regional;
multi-region; distributed; dynamic; approximate; qualified;
conflicted; partially established; or unresolved.
Unknown Infrastructure Geography ≠ Unknown Digital Event Location
by Default.
A logical or distributed location may still be governed even
where exact physical infrastructure geography is unavailable. 25.
Digital Location Conflict
ELDM shall govern conflicts among digital-location signals.
Examples include: IP geolocation indicating one country; cloud
execution indicating another; device location indicating another;
platform profile indicating another; network routing indicating
another; and user billing information indicating another.
Such differences do not necessarily represent evidence conflict.
They may represent different legitimate spatial dimensions.
Different Digital Location Signals ≠ Location Conflict by
Default.
Conflict exists only where signals make incompatible claims about
the same governed spatial dimension. 26. Digital Location
Continuity
ELDM shall preserve continuity of Digital Event Location across
changes in infrastructure where the event itself remains
continuous.
Container migration, load balancing, failover, scaling, routing
changes, or infrastructure replacement shall not automatically
create a new event or new digital location identity.
Infrastructure Change ≠ Event Change by Default.
Failover ≠ New Event by Default. 27. Physical and Digital
Location Separation
ELDM shall preserve the distinction established with ELPM.
A physical event may be digitally coordinated elsewhere.
A digital event may trigger physical execution elsewhere.
A machine may operate physically in one country while its digital
control environment spans several others.
Therefore:
Physical Event Location ≠ Digital Event Location.
Neither dimension automatically overrides the other.
Their relationship is governed later within TRELS. 28. Digital
Location and Participant Location
Participant location shall not automatically establish Digital
Event Location.
A participant may connect remotely to an event executed
elsewhere.
A customer may travel.
A seller may operate through a platform.
An AI agent may act on behalf of an organization.
A machine may transact without contemporaneous human
participation.
Therefore:
Participant Location ≠ Digital Event Location by Default.
TREPS governs participation.
OBIDENITY® governs origin-bound identity, ownership, and
authority where applicable. 29. Digital Location and Corporate
Location
Corporate headquarters, incorporation country, registered office,
business establishment, billing entity, and contractual entity
may be relevant downstream.
They do not automatically establish Digital Event Location.
Corporate Location ≠ Digital Event Location.
Company Registration ≠ Digital Execution Location.
Contracting Entity Location ≠ Event Digital Location by Default.
30. Digital Location and Tax Jurisdiction
ELDM shall maintain a strict boundary between operational digital
location and jurisdiction-specific taxation.
Governed Event Digital Location may become an input to downstream
tax analysis.
It does not itself determine: Tax Jurisdiction; digital tax
nexus; permanent establishment; significant economic presence;
tax residence; source jurisdiction; place of supply; place of
effective management; customer location under tax law; supplier
establishment; marketplace tax responsibility; legal situs; or
any other jurisdiction-specific taxation criterion.
Digital Event Location ≠ Tax Jurisdiction.
Server Location ≠ Tax Nexus.
Cloud Region ≠ Permanent Establishment.
IP Geolocation ≠ Legal Place of Supply.
Digital Execution Location ≠ Tax Residence.
These determinations belong to jurisdiction-specific tax systems.
31. Multi-Jurisdiction Readiness
ELDM shall preserve digital operational reality independently
from jurisdiction-specific interpretation.
Canonical logic:
One Governed Digital Event Reality
↓
Multiple Possible Jurisdictional
Evaluations
The same governed digital event may legitimately be evaluated
differently by multiple jurisdictions.
TREGA™ therefore establishes the event representation once.
Jurisdictions subsequently apply their own legal rules. 32.
Governance States
ELDM may assign states including:
Digital Location Ready Relevant digital spatial signals are
available.
Digital Location Under Governance Candidate environments are
being evaluated.
Digital Location Established A sufficient digital spatial
representation has been established.
Digital Location Logical The event is legitimately represented
through a logical digital environment.
Digital Location Multi-Region Material execution spans multiple
regions.
Digital Location Dynamic Material digital location changes during
the event.
Digital Location Distributed The digital event cannot
legitimately be reduced to one execution location.
Digital Location Qualified The location is established subject to
explicit qualification.
Digital Location Conflicted Material evidence concerning the same
digital dimension conflicts.
Digital Location Unresolved Available evidence is insufficient
for legitimate determination. 33. Governance Requirements
ELDM implementations shall: consume the Governed Event Location
Signal Set established by ELIM; preserve the Governed Event
Physical Location established by ELPM; identify materially
relevant digital-location candidates; distinguish constitutive
digital environments from supporting infrastructure;
differentiate execution, processing, storage, routing, platform,
device, and resource locations; support logical digital location;
support cloud, edge, API, platform, AI-agent, autonomous-system,
and machine-to-machine environments; support centralized,
dynamic, multi-region, and distributed digital events; preserve
digital-location transitions where materially relevant; preserve
supported precision; preserve uncertainty and conflict; prevent
infrastructure convenience from becoming location authority;
maintain physical/digital separation; prevent
jurisdiction-specific rules from redefining operational digital
reality; maintain traceability; and produce a Governed Event
Digital Location suitable for subsequent TRELS processing.
34. Governance Logic
ELDM follows the canonical logic:
Governed Event Location Signal Set
↓
identify digital-location
candidates
↓
determine their operational roles
↓
distinguish
constitutive execution from supporting infrastructure
↓
evaluate
logical, platform, cloud, edge, device, network, and distributed
dimensions
↓
govern precision, uncertainty, continuity, and
conflict
↓
establish Governed Event Digital Location.
Digital infrastructure shall describe operational reality.
It shall not silently determine legal geography. 35. Minimum
Implementation Framework
A minimum ELDM implementation should support:
Governed Event Reference Reference to the event under
digital-location governance.
Digital Location Identifier Unique reference for each governed
digital location.
Digital Location Type Execution environment, platform, cloud
region, edge environment, API environment, logical environment,
network environment, device-associated environment, or other
legitimate type.
Operational Role Constitutive, supporting, contextual,
transitional, or other governed role.
Digital Environment Reference Relevant service, platform,
cluster, region, logical environment, or infrastructure
reference.
Physical Infrastructure Association Physical infrastructure
relationship where known and materially relevant.
Temporal Association Relationship to governed Event Timing.
Execution State Whether material event execution occurs within
the environment.
Distribution State Centralized, multi-region, dynamic, or
distributed.
Precision State Supported digital-location precision.
Uncertainty State Known uncertainty.
Conflict State Known evidence conflict.
Evidence Reference Supporting operational evidence.
Traceability Reference Governance history enabling
reconstruction.
Governance State Current ELDM determination state.
Handoff State Readiness for distributed-location governance. 36.
Governance Outputs
ELDM may produce: Digital Location Candidate Register;
Constitutive Digital Location Record; Digital Execution Location
Record; Cloud Environment Record; Edge Environment Record; API
Location Record; Platform Location Record; Device Location
Association; Network Location Association; Logical Digital
Location Record; AI Agent Execution Location Record;
Machine-to-Machine Digital Location Record; Digital Location
Transition Record; Digital Location Precision Record; Digital
Location Uncertainty Record; Digital Location Conflict Record;
Digital Location Traceability Record; and the principal output:
Governed Event Digital Location
This output becomes an input to ELDSM. 37.
Critical Distinctions
Digital Location Signal ≠ Governed Event
Digital Location
Digital Location Candidate ≠ Governed
Event Digital Location
Supporting Digital Infrastructure ≠
Constitutive Digital Location
Infrastructure Geography ≠ Digital Event
Location
Server Location ≠ Event Digital Location
Cloud Region ≠ Event Digital Location
Infrastructure Instance Location ≠ Event
Location
Edge Node Location ≠ Complete Event
Digital Location
User Device Location ≠ Event Digital
Location
IP Address ≠ Event Location
IP Geolocation ≠ Governed Digital Location
Network Transit Location ≠ Event Digital
Location
Packet Route ≠ Event Location
API Endpoint ≠ Geographic Event Location
API Provider Location ≠ Event Digital
Location
Platform Headquarters ≠ Event Digital
Location
Platform Registration Country ≠ Event
Digital Location
Data Storage Location ≠ Event Digital
Location
Database Location ≠ Event Execution
Location
Digital Resource Location ≠ Event Digital
Location
AI Agent Location ≠ Server Location
AI Agent Location ≠ Owner Location
AI Agent Location ≠ User Location
Autonomous Execution ≠ Human Supervisor
Location
Participant Location ≠ Digital Event
Location
Corporate Location ≠ Digital Event
Location
Physical Event Location ≠ Digital Event
Location
Digital Location Change ≠ New Event
Infrastructure Change ≠ Event Change
Digital Event Location ≠ Tax Jurisdiction
Server Location ≠ Tax Nexus
Cloud Region ≠ Permanent Establishment
IP Geolocation ≠ Legal Place of Supply
Digital Execution Location ≠ Tax Residence
Operational Digital Reality ≠
Jurisdictional Tax Determination 38.
Enterprise Application
ELDM can operate as the digital spatial-governance layer betweenmodern computational systems and downstream taxation
infrastructure.
A generalized implementation pattern is:
Digital Platform / Cloud Service / API / AI Agent / Autonomous
System / Machine Network
↓
ELIM
↓
ELPM
↓
ELDM
↓
Governed Event
Digital Location
↓
ELDSM
↓
ELCM
↓
Governed Temporally and
Spatially Situated Event
↓
Jurisdiction-Specific Tax Engines
This allows tax infrastructure to consume a governed
representation of digital reality without forcing the event
itself to adopt the assumptions of one tax regime. 39. Use Case 1
— Global AI Agent Transaction
An autonomous AI procurement agent operating for an enterprise
identifies a supplier, negotiates through APIs, obtains
authorization, initiates a digital purchase, and coordinates
fulfillment.
The agent's orchestration service operates through a European
cloud region.
Model inference may occur in another region.
The supplier platform operates globally.
Payment authorization passes through infrastructure in additional
countries.
The purchasing organization is headquartered elsewhere.
The human who configured the agent is not involved when the
transaction occurs.
ELDM distinguishes the digital environments materially
constituting the event from infrastructure that merely supports,
routes, stores, or observes it.
It does not select the company's headquarters, server country,
user location, IP geolocation, or cloud region as the legal
location of the transaction.
The result is a governed digital spatial representation capable
of being consumed by multiple jurisdictional tax systems.
Autonomous digital execution requires governed location before
legal jurisdiction can legitimately interpret that location. 40.
Use Case 2 — Multi-Region Digital Service
A customer accesses a digital service through a mobile device
while traveling.
The account was created in another country.
The billing address belongs to another jurisdiction.
The service platform dynamically routes the session through edge
infrastructure.
Application processing occurs across two cloud regions.
Data is replicated globally.
Payment is handled by a separate provider.
A conventional system may derive location from the IP address,
billing country, server region, or customer profile depending on
which field is available.
ELDM instead governs each signal according to its operational
role.
It establishes the digital spatial structure of the event without
allowing any single technical or administrative signal to become
authoritative by default.
The digital event is governed as it actually operates before any
jurisdiction determines what that operational reality means under
tax law. 41. Canonical Boundary
ELDM owns the governance of the digital spatial manifestation of
the Tax-Relevant Event, including constitutive digital
environments, digital execution locations, cloud and edge
environments, API environments, platform environments,
device-associated locations, network-associated locations,
logical digital locations, AI-agent execution environments,
autonomous-system digital environments, machine-to-machine
digital locations, digital-location transitions, digital-location
precision, uncertainty, conflict, continuity, and traceability.
ELDM does not own final Distributed Event Location or final Event
Location Correlation.
It does not redefine Event Context, Event Recognition, Event
Formation, Event Boundary, Event Timing, Physical Event Location,
Event Participation, Participant Identity, Value Association,
Event Relationships, Event Determination, or Event Record
Governance.
It does not determine Tax Jurisdiction, digital tax nexus,
permanent establishment, significant economic presence, tax
residence, source jurisdiction, place of supply, customer
location under tax law, supplier establishment, marketplace tax
responsibility, Legal Tax Point, Tax Period, taxability, Tax
Liability, tax rate, reporting obligation, or any
jurisdiction-specific tax consequence.
The canonical handoff is:
ELIM — Governed Event Location Signal Set
↓
ELPM — Governed Event
Physical Location
↓
ELDM — Governed Event Digital Location
↓
ELDSM — Event Distributed Location Governance
Canonical Closing Statement
ELDM establishes where the governed event materially exists andoperates within digital environments without allowing servers, IP
addresses, cloud regions, devices, platforms, network routes, or
corporate locations to become authoritative merely because they
can be geographically identified.
Digital infrastructure can reveal where parts of an event
operate. It cannot, by itself, determine where the event legally
belongs.
ELDM governs where the event occurs digitally — not which
jurisdiction may tax the digital activity.
TREGA™ governs the event. The jurisdiction governs the tax.