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 Timing Standard (TRETS)
Module: ETSM — Event Start Module
Operational Layer: Event Start Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Core Module
Governed Space: Event Start
Origin ID: TREGA-TRETS-ETSM-002
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 Start Module (ETSM) governs how the operational
beginning of a Governed Bounded Event is determined from the
Governed Event Time Signal Set by identifying, evaluating,
qualifying, and establishing the temporal condition at which the
governed event legitimately begins as the event under
examination.

ETSM distinguishes the operational beginning of the governed
event from earlier preparatory activity, system initialization,
authorization, scheduling, communication, recording, technical
activation, contractual milestones, accounting recognition, and
jurisdiction-specific legal or taxation points that may occur
before, at, or after the event begins.

Its specific task is:

to establish a coherent, traceable, and operationally justified
Governed Event Start without allowing technical timestamps,
administrative conventions, contractual dates, accounting
treatment, or jurisdiction-specific tax rules to redefine the
operational beginning of the governed event.

ETSM governs when the bounded event begins as an operational
event.

It does not determine when that event is legally recognized for
taxation. ------------------------------ 1. Operational Role

ETIM identifies and structures the materially relevant temporal
signals associated with the Governed Bounded Event.

ETSM determines which temporal condition legitimately establishes
the beginning of that event.

The transition governed by ETSM is:

Governed Event Time Signal Set

↓

Governed Event Start

This requires more than selecting the earliest available
timestamp.

The earliest recorded activity may represent: preparation,
authorization, scheduling, system initialization, resource
reservation, communication, preliminary machine activity, data
creation, contractual formation, administrative processing.

None necessarily establishes that the governed event itself has
begun.

ETSM therefore determines the operational threshold separating
activity preceding the event from activity constituting the
event.

Earliest Timestamp ≠ Event Start by Default.
------------------------------ 2. Internal Flow

The TRETS Internal Module Flow is:

Governed Bounded Event

↓

ETIM — Event Time Identification

↓

ETSM
— Event Start

↓

ETCM — Event Completion

↓

ETDM — Event Duration

↓

ETOM — Event Temporal Order

↓

Governed Temporally Situated Event

ETSM governs:

Governed Event Time Signal Set

↓

Start Candidate Identification

↓

Start Condition Assessment

↓

Pre-Event Activity Differentiation

↓

Start Qualification

↓

Start Ambiguity / Conflict Handling

↓

Governed Event Start

↓

ETCM

ETSM receives temporal evidence from ETIM.

It does not recreate the temporal signal inventory.

It determines which governed temporal condition establishes Event
Start. ------------------------------ 3. Operational Space

ETSM governs the operational space in which the beginning of the
bounded event must be distinguished from surrounding temporal
activity.

This space includes: candidate start signals, candidate start
conditions, operational initiation, first constitutive event
activity, preparatory activity, authorization activity,
scheduling, resource allocation, system initialization, machine
activation, autonomous-system initiation, transaction initiation,
service activation, physical commencement, digital commencement,
distributed commencement, conditional commencement, phased
commencement, approximate start conditions, conflicting start
signals, start uncertainty, start traceability.

The presence of earlier activity does not automatically extend
the governed event backward to that activity.
------------------------------ 4. Operational Scope

ETSM governs:

1. identification of candidate Event Start signals; 2. assessment
of candidate start conditions; 3. distinction between pre-event
activity and constitutive event activity; 4. determination of the
operational commencement threshold; 5. evaluation of physical,
digital, transactional, distributed, machine-generated, and
autonomous starts; 6. treatment of multiple possible start
signals; 7. treatment of phased or distributed commencement; 8.
detection of start ambiguity; 9. detection of conflicting start
representations; 10. preservation of start uncertainty where
necessary; 11. establishment of Event Start precision; 12.
maintenance of traceability to ETIM temporal signals; 13.
production of the Governed Event Start for ETCM.

ETSM does not determine Event Completion, Event Duration, final
Event Temporal Order, Legal Tax Point, Tax Period, or
jurisdiction-specific tax consequences.
------------------------------ 5. Event Start Candidate
Identification

ETSM begins by identifying temporal signals that could plausibly
establish Event Start.

Candidate signals may include: first material operational action,
physical commencement, transaction execution, service activation,
transfer initiation, machine execution, autonomous execution,
first constitutive state transition, digital process
commencement, first material performance, first governed event
component entering execution.

Candidate identification does not establish Event Start.

Each candidate must be evaluated against the governed structure
of the bounded event.

Start Candidate ≠ Governed Event Start.
------------------------------ 6. Constitutive Event Activity

A legitimate Event Start should correspond to a temporal
condition at which the governed event begins to exist
operationally as the event defined by its governed structure.

ETSM therefore distinguishes constitutive activity from activity
merely associated with the event.

Constitutive activity materially participates in the event's
operational realization.

Associated activity may support, prepare, authorize, document, or
anticipate the event without itself constituting commencement.

The relevant question is not:

What happened first?

The relevant question is:

When did the governed event begin to occur as the event under
examination?

First Related Activity ≠ First Constitutive Event Activity.
------------------------------ 7. Pre-Event Activity
Differentiation

Many operational processes contain substantial activity before
the governed event begins.

Examples include: quotation, negotiation, scheduling,
reservation, planning, approval, authorization, resource
allocation, software initialization, machine warm-up, preliminary
data exchange, contract preparation, risk screening.

ETSM must prevent such activity from automatically extending
Event Start backward.

However, activity that appears preparatory in one event model may
be constitutive in another.

The determination must therefore remain tied to the Governed
Bounded Event received from TREBS.

Event Association ≠ Event Commencement.
------------------------------ 8. Authorization vs. Execution

Authorization frequently occurs before operational execution.

A payment may be authorized before settlement.

A machine may receive authorization before physical operation.

An autonomous agent may receive permission before executing an
action.

A service may be approved before activation.

ETSM preserves this distinction.

Authorization may constitute Event Start only where the governed
event itself is legitimately defined around the authorization
activity.

Otherwise:

Authorization Time ≠ Event Start by Default.

Likewise:

Permission ≠ Execution. ------------------------------ 9. System
Activation vs. Event Start

Technical systems often activate before the governed event
begins.

Examples include: application session creation, API
authentication, device wake-up, machine initialization, database
transaction creation, cloud resource provisioning, workflow
initialization.

Such timestamps may be operationally relevant without
constituting Event Start.

ETSM must prevent technical architecture from redefining event
reality.

System Activation ≠ Event Start by Default.
------------------------------ 10. Transactional Event Start

Transactional environments may contain several plausible
commencement signals.

For example:

Order Creation

↓

Order Submission

↓

Merchant Acceptance

↓

Payment
Authorization

↓

Execution

↓

Confirmation

The correct operational start depends on the structure of the
Governed Bounded Event.

ETSM does not impose a universal rule that every transaction
begins with order creation, acceptance, payment, or settlement.

Instead, it determines the start condition from the governed
event itself.

Transaction Record Creation ≠ Transaction Event Start by Default.
------------------------------ 11. Physical Event Start

Physical events may begin through observable operational
activity.

Examples include: movement, production commencement, loading,
construction activity, physical transfer, machine execution,
delivery commencement, resource transformation.

Where physical commencement is relevant, ETSM must associate the
start determination with sufficient supporting temporal signals.

Physical events may nevertheless contain preparatory physical
activity that does not belong to the governed event.

Physical Activity ≠ Event Start by Default.
------------------------------ 12. Digital Event Start

Digital events may begin without a physical action.

Potential start conditions include: execution of a digital
service, transfer initiation, access activation, processing
commencement, digital delivery, deployment, state transition,
autonomous instruction execution.

ETSM evaluates when the governed digital event actually begins
rather than automatically using the first timestamp generated by
the technical system.

First Digital Timestamp ≠ Digital Event Start by Default.
------------------------------ 13. Distributed Event Start

A governed event may begin across multiple systems or locations.

There may therefore be no single perfectly synchronized timestamp
representing commencement.

ETSM may need to establish: one sufficiently supported start
timestamp, a bounded start interval, a start condition
represented across multiple correlated signals, an approximate
operational start, a distributed commencement state.

The methodology must preserve the temporal precision actually
supported by the evidence.

Distributed Commencement ≠ Artificial Single-Time Precision.
------------------------------ 14. Machine and Autonomous Event
Start

Autonomous systems introduce additional complexity because
planning, decision, authorization, communication, and execution
may occur without direct human intervention.

A sequence may be:

Objective Received

↓

Autonomous Analysis

↓

Decision

↓

Resource
Reservation

↓

Command

↓

Machine Execution

The first autonomous computation does not necessarily constitute
Event Start.

Nor does the first machine-generated timestamp.

ETSM identifies the point at which the governed autonomous or
machine-mediated event begins operationally.

Autonomous Decision ≠ Event Start by Default.

Machine Command ≠ Machine Execution.
------------------------------ 15. Conditional Event Start

Some events begin only when specified operational conditions
become true.

A process may be initialized earlier but remain inactive until:
acceptance occurs, resources become available, required input
arrives, physical execution begins, threshold conditions are
reached, service activation occurs.

ETSM may therefore represent Event Start through a governed
condition rather than merely selecting a pre-existing timestamp
field.

Process Creation ≠ Operational Commencement.
------------------------------ 16. Phased Event Start

Some bounded events begin through several tightly connected
actions rather than one instantaneous transition.

Where operational reality does not support a single precise start
moment, ETSM may represent commencement as a governed temporal
interval or composite start condition.

This should occur only when supported by the event structure and
temporal evidence.

ETSM must not manufacture precision where operational reality is
genuinely gradual.

Temporal Precision Requirement ≠ Operational Reality.
------------------------------ 17. Start Ambiguity

Start ambiguity exists where available governed information
supports more than one plausible Event Start and available
evidence does not sufficiently justify selection.

ETSM should preserve such ambiguity explicitly.

Possible causes include: incomplete logs, contradictory records,
uncertain event formation, asynchronous systems, delayed
recording, approximate physical observations, insufficient
machine telemetry, competing operational interpretations.

An unresolved start should not be silently converted into an
exact timestamp.

Required Start Field ≠ Governed Start Certainty.
------------------------------ 18. Start Conflict

Start conflict exists when materially relevant temporal evidence
supports incompatible commencement representations.

ETSM must identify and preserve the conflict until sufficient
governance can establish a legitimate resolution.

Resolution should be based on operational event structure and
evidence rather than system hierarchy alone.

A preferred ERP timestamp does not automatically override
contradictory physical or digital evidence.

System Authority ≠ Event-Time Authority by Default.
------------------------------ 19. Event Start Precision

Event Start may legitimately be represented at different
precision levels.

Examples include: exact timestamp, second, minute, hour, date,
bounded interval, approximate period, sequence-relative start.

The selected precision must not exceed what the governed temporal
evidence supports.

Timestamp Precision ≠ Temporal Certainty.
------------------------------ 20. Event Start States

ETSM may represent Event Start governance through states such as:

Start Candidate A temporal signal or condition may represent
Event Start.

Start Qualified The candidate is sufficiently supported as
constitutive commencement.

Start Established A legitimate operational Event Start has been
established.

Start Approximate Commencement is sufficiently known but not
precisely timestamped.

Start Ambiguous Multiple plausible commencement representations
remain.

Start Conflicted Material evidence supports incompatible start
determinations.

Start Insufficient Available information is inadequate for
reliable determination.

Start Unresolved Further governance or evidence is required.

Start Established ≠ Legal Tax Point Established.
------------------------------ 21. Governance Requirements

A conforming ETSM implementation should:

1. consume the Governed Event Time Signal Set from ETIM; 2.
identify plausible Event Start candidates; 3. evaluate start
candidates against the Governed Bounded Event; 4. distinguish
preparatory activity from constitutive event activity; 5.
distinguish authorization from execution where relevant; 6.
distinguish technical activation from operational commencement;
7. support physical, digital, distributed, transactional,
machine-generated, and autonomous events; 8. preserve ambiguity
and conflict; 9. prevent artificial temporal precision; 10.
maintain traceability to supporting temporal signals; 11. avoid
jurisdiction-specific tax assumptions; 12. avoid treating
accounting, contractual, technical, or administrative dates as
authoritative by default; 13. establish a Governed Event Start
suitable for Event Completion governance.

------------------------------ 22. Governance Logic

The minimum ETSM governance logic is:

IF one or more temporal signals plausibly
represent commencement,

THEN they must be evaluated as Event Start candidates.

IF a signal represents only preparatory or
supporting activity,

THEN it must not establish Event Start unless that activity is
constitutive of the Governed Bounded Event.

IF authorization precedes execution,

THEN authorization must not automatically establish Event Start.

IF system initialization precedes
operational commencement,

THEN initialization must remain distinct from Event Start.

IF multiple start candidates are
compatible,

THEN they may support one governed commencement representation.

IF multiple start candidates materially
conflict,

THEN the conflict must remain explicit until sufficiently
resolved.

IF precise commencement cannot be
legitimately established,

THEN an approximate time or bounded interval must be preserved
where appropriate.

IF a jurisdiction-specific tax rule uses a
different legal date,

THEN that legal date must not retroactively redefine the
operational Event Start governed by ETSM.
------------------------------ 23. Minimum Implementation
Framework

A minimum ETSM implementation should support:

1. Governed Event Reference Reference to the Governed Bounded
Event.

2. Temporal Signal Set Reference Reference to ETIM output.

3. Start Candidate Identifier Unique reference for each candidate
commencement signal or condition.

4. Start Candidate Type Physical, digital, transactional,
machine, autonomous, conditional, distributed, or other.

5. Start Condition Operational condition represented by the
candidate.

6. Constitutive Activity Assessment Whether the candidate
represents actual commencement of the governed event.

7. Pre-Event Activity Indicator Whether preceding activity
remains outside Event Start.

8. Start Precision Supported temporal precision.

9. Start Evidence / Traceability Reference Links to supporting
temporal signals and operational records.

10. Ambiguity / Conflict State Explicit representation of
unresolved start issues.

11. Start Governance State Candidate, qualified, established,
approximate, ambiguous, conflicted, insufficient, or unresolved.

12. Governed Event Start The established operational commencement
representation.

13. Handoff State Readiness for ETCM.
------------------------------ 24. Governance Outputs

ETSM may produce: Governed Event Start Event Start Candidate Set
Start Condition Record Constitutive Activity Assessment Pre-Event
Activity Record Start Qualification Record Start Precision Record
Start Ambiguity Indicator Start Conflict Indicator Start
Insufficiency Indicator Distributed Start Representation Machine
/ Autonomous Start Representation Event Start Traceability Record
Event Completion Governance Readiness State

The principal output is:

Governed Event Start

This output proceeds to:

ETCM — Event Completion Module ------------------------------ 25.
Critical Distinctions

Temporal Signal ≠ Event Start

Start Candidate ≠ Governed Event Start

Earliest Timestamp ≠ Event Start by
Default

First Related Activity ≠ First
Constitutive Event Activity

Event Association ≠ Event Commencement

Preparation ≠ Event Start

Authorization Time ≠ Event Start by
Default

Permission ≠ Execution

System Activation ≠ Event Start by Default

Transaction Record Creation ≠ Transaction
Event Start by Default

Physical Activity ≠ Event Start by Default

First Digital Timestamp ≠ Digital Event
Start by Default

Autonomous Decision ≠ Event Start by
Default

Machine Command ≠ Machine Execution

Process Creation ≠ Operational
Commencement

Distributed Commencement ≠ Artificial
Single-Time Precision

Timestamp Precision ≠ Temporal Certainty

Required Start Field ≠ Governed Start
Certainty

System Authority ≠ Event-Time Authority by
Default

Event Start ≠ Event Completion

Event Start ≠ Event Duration

Event Start ≠ Final Temporal Order

Operational Event Start ≠ Legal Tax Point

Event Start ≠ Tax Period Determination

Event Start ≠ Tax Liability Determination
------------------------------ 26. Enterprise Application

ETSM can support operational event governance across: ERP
systems, banking infrastructure, payment systems, digital
marketplaces, e-commerce platforms, SaaS environments, logistics
networks, manufacturing systems, IoT infrastructure, autonomous
agents, robotics, machine-to-machine systems, distributed
computing environments, digital-asset infrastructure,
cross-border transaction platforms, automated accounting and tax
infrastructure.

ETSM enables these systems to preserve one governed operational
Event Start independently of how downstream accounting,
regulatory, contractual, or jurisdiction-specific taxation
systems subsequently interpret the event.
------------------------------ 27. Real-System Use Case 1 —
Cross-Border Digital Service

A business customer requests a cloud service at 23:56.

The platform records the order at 23:57.

Payment authorization occurs at 23:59.

The provider accepts the request at 00:01.

Cloud resources are provisioned at 00:03.

The service becomes operationally available at 00:04.

The invoice is generated at 00:06.

Payment settles the following day.

Several systems could independently claim that their timestamp
represents the beginning of the transaction.

ETSM does not automatically choose the earliest timestamp,
invoice date, payment authorization, or settlement date.

It evaluates the Governed Bounded Event and the temporal signals
produced by ETIM to determine which condition represents the
actual commencement of the event under governance.

Where the governed event concerns operational delivery of the
digital service, service activation may provide the constitutive
commencement condition even though multiple related activities
occurred earlier.

The resulting Governed Event Start remains distinct from any
jurisdiction-specific rule determining when a taxable supply
legally occurs.

Operational commencement must be established from the event
itself — not inherited from whichever downstream system needs a
date. ------------------------------ 28. Real-System Use Case 2 —
Autonomous Manufacturing Operation

An AI production controller receives an objective at 07:52.

It begins planning at 07:53.

Resources are reserved at 07:56.

Production authorization is issued at 08:00.

A robotic handling system moves raw material at 08:02.

The production machine begins material transformation at 08:04.

Quality sensors and supporting robots subsequently perform
thousands of machine operations.

A naive implementation could define Event Start using the
objective receipt, AI planning, authorization, first robotic
movement, or first machine-control timestamp.

ETSM evaluates which activity constitutes commencement of the
Governed Bounded Event.

If the bounded event represents the manufacturing transformation
itself, preliminary AI planning and resource allocation remain
pre-event activities, while commencement of material
transformation may establish the legitimate operational start.

ETSM records that determination without asserting when any
jurisdiction considers the resulting activity legally taxable.

Autonomous preparation can precede the event without becoming the
event. ------------------------------ 29. Canonical Boundary

ETSM governs the identification, assessment, qualification,
establishment, precision, ambiguity, conflict, and traceability
of the operational commencement of a Governed Bounded Event using
the Governed Event Time Signal Set produced by ETIM.

It does not determine Event Completion, Event Duration, final
Event Temporal Order, Event Location, Event Participation,
Event-to-Value Association, Event Relationships, Event
Determination, Legal Tax Point, Tax Period, Tax Jurisdiction,
legal taxability, tax liability, or jurisdiction-specific tax
consequences.

ETSM receives:

ETIM — Governed Event Time Signal Set

ETSM produces:

Governed Event Start

The output is handed to:

ETCM — Event Completion Module

The canonical handoff is:

ETIM — Governed Event Time Signal Set

↓

ETSM — Governed Event
Start

↓

ETCM — Event Completion Module
------------------------------ 30. Canonical Closing Statement

ETSM establishes when the governed event begins in operational
reality before accounting systems, legal frameworks, or taxation
regimes determine what that beginning means for their own
purposes.

ETSM determines when the event begins — not when a jurisdiction
decides that tax begins.