Event Duration Module (ETDM)
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: ETDM — Event Duration Module
Operational Layer: Event Duration Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Core Module
Governed Space: Event Duration
Origin ID: TREGA-TRETS-ETDM-004
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 Duration Module (ETDM) governs how the temporal extentof a Tax-Relevant Event is established from its governed temporal
structure, including its Governed Event Start, Governed Event
Completion, intermediate temporal conditions, interruptions,
suspensions, phases, distributed execution, and supported
temporal precision.
ETDM determines how long the governed event persisted as
operational reality without converting that duration into a
jurisdiction-specific tax period, accounting period, reporting
period, contractual period, billing period, or legal duration.
Its specific task is:
to establish a coherent, traceable, and operationally justified
representation of the temporal extent occupied by the governed
event between its legitimate operational start and completion.
ETDM governs how long the event existed or persisted as the
governed event .
It does not determine the period in which a jurisdiction
recognizes, reports, assesses, or taxes that event.
------------------------------ 1. Operational Role
ETSM establishes the Governed Event Start.
ETCM establishes the Governed Event Completion.
ETDM governs the temporal extent between and across those
governed temporal conditions.
The primary transition is:
Governed Event Start + Governed Event
Completion
↓
Governed Event Duration
Duration may appear mathematically simple, but governed duration
cannot always be reduced to:
Completion Timestamp − Start Timestamp
Events may contain: pauses, suspensions, inactive intervals,phased execution, asynchronous components, distributed
operations, partial completion, uncertain temporal boundaries,
approximate timestamps, open-ended activity, machine execution
cycles, autonomous continuation.
ETDM therefore governs the meaning and representation of duration
rather than merely calculating elapsed clock time.
Elapsed Clock Time ≠ Governed Event Duration 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
ETDM governs:
Governed Event Start + Governed Event Completion
↓
Temporal
Extent Construction
↓
Active / Inactive Interval Assessment
↓
Interruption / Suspension Assessment
↓
Phase and Distributed
Duration Assessment
↓
Duration Precision & Uncertainty Governance
↓
Governed Event Duration
↓
ETOM
ETDM consumes the governed temporal results established by
preceding TRETS modules.
It does not reopen Event Start or Event Completion merely to
produce a preferred duration.
Where a material inconsistency is discovered, ETDM must preserve
the issue and route it to the relevant prior temporal governance
process. ------------------------------ 3. Operational Space
ETDM governs the space in which the temporal extent of the event
must be represented.
This includes: total event span, active duration, inactive
duration, interrupted duration, suspended duration, continuous
duration, discontinuous duration, phased duration, distributed
duration, overlapping execution intervals, machine execution
duration, autonomous-system duration, approximate duration,
bounded duration, open duration, duration uncertainty, duration
conflict, duration precision, duration traceability.
The governed duration must remain anchored to the event's
operational reality. ------------------------------ 4.
Operational Scope
ETDM governs:
1. construction of Event Duration from governed temporal inputs;
2. establishment of total temporal extent; 3. differentiation
between total span and active duration; 4. identification of
inactive intervals; 5. governance of interruptions; 6. governance
of suspensions; 7. representation of continuous and discontinuous
events; 8. representation of phased events; 9. representation of
distributed events; 10. treatment of overlapping temporal
components; 11. machine and autonomous-system duration; 12.
treatment of incomplete or open events; 13. duration precision;
14. duration uncertainty; 15. duration conflicts; 16. duration
correction; 17. duration traceability; 18. readiness for Event
Temporal Order governance.
ETDM does not determine jurisdiction-specific tax periods,
reporting periods, accounting periods, contractual durations,
billing periods, or statutory time periods.
------------------------------ 5. Temporal Extent Construction
The baseline temporal extent of an event is established from its
Governed Event Start and Governed Event Completion.
Conceptually:
Governed Event Start
↓
Temporal Extent
↓
Governed Event Completion
Where both endpoints are sufficiently established, ETDM may
derive an overall event span.
However, this span does not automatically represent the event's
active operational duration.
For example:
08:00 Start
↓
12:00 Suspension
↓
14:00 Resumption
↓
18:00
Completion
The overall temporal span is ten hours.
The event may have only eight hours of active execution.
Whether suspension belongs inside the governed duration
representation depends on what the duration is intended to
represent operationally.
ETDM must preserve this distinction.
Total Temporal Span ≠ Active Event Duration by Default.
------------------------------ 6. Continuous Event Duration
A continuous event proceeds without materially relevant
interruption between its Governed Event Start and Governed Event
Completion.
For such events:
Start
↓
Continuous Activity
↓
Completion
the temporal span may legitimately represent the event duration.
Examples may include: continuous machine operation, uninterrupted
data transfer, physical transport, continuous service execution,
single-stage transformation.
Even here, system latency, logging delays, confirmation delays,
or downstream processing must not artificially extend the
duration.
Continuous Event Duration ≠ System Processing Window by Default.
------------------------------ 7. Discontinuous Event Duration
Some governed events legitimately persist across interruptions or
inactive intervals.
Their structure may be:
Start
↓
Activity
↓
Pause
↓
Activity
↓
Suspension
↓
Activity
↓
Completion
ETDM must distinguish: overall temporal span, active execution
duration, inactive duration, suspension duration, interruption
duration.
The event may remain the same Governed Bounded Event despite
discontinuity.
ETDM does not split it into multiple events merely because
execution was interrupted.
Temporal Discontinuity ≠ New Event by Default.
Event separation remains governed by TREBS.
------------------------------ 8. Active Duration
Active Duration represents the time during which constitutive
operational activity belonging to the event is actively
occurring.
It may differ substantially from the total temporal span.
Examples include: machine processing time, active service
performance, autonomous execution time, physical transformation
time, active transfer time.
Active Duration must be derived from operationally meaningful
activity rather than system uptime or record availability.
System Activity ≠ Event Activity by Default.
------------------------------ 9. Inactive Duration
Inactive Duration represents temporal intervals within the
broader event span during which constitutive event activity is
not actively occurring but the same event may remain
operationally open.
Examples include: waiting periods, temporary pauses, resource
unavailability, queued continuation, scheduled interruption,
external dependency waiting.
Inactive time should not automatically be removed from every
duration representation.
ETDM must preserve whether the governed output represents:
Total Event Duration
or:Active Event Duration
or both.Inactive Time ≠ Event Absence by Default.
------------------------------ 10. Event Interruption
An interruption temporarily stops event activity without
necessarily ending the governed event.
ETDM must determine: interruption start, interruption end,
interruption duration, whether the event remains continuous as
one governed event, whether the interruption affects active
duration, whether the interruption introduces uncertainty.
An interruption must not automatically create a new Event Start
or Event Completion.
Interruption ≠ Completion.
Resumption ≠ New Event Start by Default.
------------------------------ 11. Event Suspension
Suspension is a governed state in which continuation is
intentionally or operationally deferred while the event remains
capable of resumption.
Suspension may arise from: human intervention, system control,
external dependency, resource constraints, safety procedures,
autonomous decision logic, operational authorization.
ETDM may represent suspended time separately from active time.
It does not determine whether a legal framework treats suspension
differently.
Operational Suspension ≠ Legal Suspension.
------------------------------ 12. Phased Duration
An event may contain multiple constitutive phases:
Phase A
↓
Phase B
↓
Phase C
↓
Completion
ETDM may represent: phase duration, transition intervals,
aggregate active duration, total event span.
Where phases overlap, simple addition may produce an incorrect
result.
For example:
Phase A = 3 hours
Phase B = 2 hours
with one hour of overlap.The event does not necessarily have five hours of elapsed
duration.
ETDM must preserve the temporal relationship among phases.
Sum of Phase Durations ≠ Event Duration by Default.
------------------------------ 13. Overlapping Duration
Multiple components of the same event may execute simultaneously.
This is common in: distributed computing, manufacturing,
logistics, autonomous systems, digital services, multi-party
operations.
ETDM must avoid double-counting overlapping intervals where the
objective is to establish elapsed event duration.
At the same time, component-level active duration may
legitimately exceed overall elapsed duration when multiple
components operate concurrently.
Therefore:
Aggregate Component Time ≠ Elapsed Event Duration.
------------------------------ 14. Distributed Event Duration
A distributed event may span: multiple machines, multiple
systems, multiple locations, multiple participants, multiple
technical environments.
Different components may begin and complete at different times.
ETDM must construct duration from the governed event as a whole
rather than selecting one system's local execution window.
Possible representations include: global event span, component
durations, active distributed duration, overlapping execution,
asynchronous intervals, completion lag.
Distributed Event Duration ≠ Duration of One Component.
------------------------------ 15. Machine Event Duration
Machine-generated events may produce extremely precise temporal
records.
A machine may report:
08:00:00.000001
↓
08:00:02.983746
Technical precision does not automatically establish that the
governed event legitimately has microsecond-level temporal
precision.
Machine clocks may contain: synchronization differences, clock
drift, buffering, delayed logging, asynchronous recording,
system-specific temporal semantics.
ETDM must therefore distinguish computational precision from
governed temporal precision.
Machine Precision ≠ Governed Duration Precision.
------------------------------ 16. Autonomous Event Duration
Autonomous systems may independently initiate, pause, modify,
resume, and complete operations.
An autonomous event may therefore include:
Initiation
↓
Execution
↓
Self-Pause
↓
Replanning
↓
Resumption
↓
Completion
↓
Monitoring
ETDM determines the governed temporal extent of the event without
assuming that all autonomous-system activity belongs inside the
event duration.
Post-completion monitoring may remain outside the governed event.
Likewise, internal computational cycles may not constitute
separate duration components unless operationally relevant.
Autonomous System Runtime ≠ Governed Event Duration by Default.
------------------------------ 17. Open Event Duration
An event may have a Governed Event Start while no legitimate
Event Completion has yet been established.
In such cases, ETDM must not fabricate final duration.
The event may be represented as:
Open Duration
Duration Pending
Duration To-Date
Completion Unresolved
A duration-to-date representation must clearly indicate that itis not final.
Elapsed Time To Date ≠ Final Event Duration.
------------------------------ 18. Partial and Interrupted
Completion
Where ETCM establishes partial, interrupted, or failed
completion, ETDM must preserve the corresponding temporal
condition.
A failed event may still have a legitimate duration.
An interrupted event may have: active duration, interruption
duration, total span, termination point.
Failure does not invalidate the temporal history of the event.
Failed Event ≠ Zero Duration. ------------------------------ 19.
Duration Precision
ETDM must represent duration only at the precision legitimately
supported by governed temporal inputs.
Possible representations include: exact duration, rounded
duration, approximate duration, minimum duration, maximum
duration, bounded duration range, unresolved duration.
If Event Start is known only within a one-hour interval and Event
Completion only within another interval, an artificially exact
duration must not be generated.
Precise Calculation from Imprecise Inputs ≠ Precise Governed
Duration. ------------------------------ 20. Duration Uncertainty
Duration uncertainty may arise from: uncertain Event Start,
uncertain Event Completion, missing intermediate signals,
disputed interruption periods, clock synchronization problems,
distributed systems, approximate observations, incomplete
records.
ETDM must propagate relevant temporal uncertainty rather than
hide it through mathematical calculation.
A numerically exact result derived from uncertain inputs remains
uncertain.
Mathematical Exactness ≠ Governance Certainty.
------------------------------ 21. Duration Conflict
Duration conflict exists when materially relevant records produce
incompatible duration representations.
For example: machine logs show 47 minutes; ERP records show 55
minutes; operator records show approximately one hour;
autonomous-system logs omit a suspension interval.
ETDM must identify the source of the conflict and preserve it
where it cannot be legitimately resolved.
Preferred Data Source ≠ Automatically Correct Duration.
------------------------------ 22. Duration Correction
New information may justify correction of a previously
established duration.
Corrections must preserve: prior duration representation, reason
for correction, affected temporal inputs, revised duration,
correction authority, traceability.
Correction must not silently overwrite governed history.
Duration Correction ≠ Historical Erasure.
If the correction originates from an incorrect Event Start or
Event Completion, the relevant issue should be routed to ETSM or
ETCM rather than being concealed through ETDM calculation.
------------------------------ 23. Event Duration States
ETDM may represent duration through governance states including:
Duration Ready Required temporal inputs are available.
Duration Under Governance Temporal extent is being constructed.
Duration Established A sufficiently governed duration exists.
Duration Approximate Duration is established with limited
precision.
Duration Bounded Duration can be represented only as a supported
range.
Duration Open The event has not reached Governed Event
Completion.
Duration Partial Only part of the temporal extent can be
governed.
Duration Conflicted Materially incompatible duration
representations exist.
Duration Uncertain Relevant uncertainty remains.
Duration Insufficient Available information cannot support a
legitimate duration.
Duration Corrected A prior duration has been revised through
governed correction.
Governed Event Duration ≠ Jurisdictional Tax Period.
------------------------------ 24. Tax Period Separation
One of ETDM's most important boundaries is the separation between
operational Event Duration and jurisdiction-specific Tax Period.
An event may: begin in one tax period and complete in another;
last seconds but be recognized legally later; continue across
multiple reporting periods; be operationally completed before
legal recognition; have different tax-period treatment across
jurisdictions.
ETDM does not resolve these questions.
It provides governed temporal reality for downstream systems.
Event Duration ≠ Tax Period Determination.
------------------------------ 25. Reporting and Accounting
Period Separation
Operational duration must also remain distinct from: accounting
period, reporting period, billing cycle, fiscal period,
contractual period, settlement window.
These periods may consume or interpret TREGA temporal outputs but
must not redefine the operational duration governed by ETDM.
Accounting Period ≠ Event Duration.
Reporting Period ≠ Event Duration.
Billing Period ≠ Event Duration. ------------------------------
26. Governance Requirements
A conforming ETDM implementation should:
1. consume Governed Event Start from ETSM; 2. consume Governed
Event Completion or corresponding completion state from ETCM; 3.
construct the event's temporal extent; 4. distinguish total span
from active duration where materially relevant; 5. identify
inactive intervals; 6. identify interruptions and suspensions; 7.
support continuous and discontinuous events; 8. support phased
events; 9. support overlapping temporal components; 10. support
distributed events; 11. support machine-generated and autonomous
events; 12. support open and incomplete events; 13. preserve
supported temporal precision; 14. propagate uncertainty; 15.
identify duration conflicts; 16. preserve correction history; 17.
maintain traceability to governed temporal inputs; 18. prevent
jurisdiction-specific Tax Period logic from entering ETDM; 19.
produce a Governed Event Duration suitable for ETOM.
------------------------------ 27. Governance Logic
The minimum ETDM governance logic is:
IF Governed Event Start and Governed Event
Completion are established,
THEN the event's temporal extent may be constructed.IF the event contains materially relevant
inactive periods,
THEN total span and active duration should be distinguished wherenecessary.
IF the event is interrupted but remains
the same Governed Bounded Event,
THEN interruption must not automatically create a new event.IF event phases overlap,
THEN phase durations must not be mechanically summed as elapsedEvent Duration.
IF distributed components execute
asynchronously,
THEN duration must be governed from the event structure ratherthan a single component clock.
IF Event Completion remains unresolved,
THEN final Event Duration must remain open or pending.IF temporal inputs are approximate,
THEN the resulting duration must preserve correspondinguncertainty.
IF machine timestamps provide greater precision than operational
evidence supports,
THEN governed duration precision must be reduced accordingly.
IF materially conflicting duration
representations remain,
THEN conflict must remain explicit.IF new evidence changes Event Start or
Event Completion,
THEN the affected upstream temporal governance must bereconsidered.
IF a jurisdiction assigns a Tax Period,
THEN that determination remains outside ETDM.------------------------------ 28. Minimum Implementation
Framework
A minimum ETDM implementation should support:
1. Governed Event Reference Reference to the Governed Bounded
Event.
2. Governed Event Start Reference Reference to ETSM output.
3. Governed Event Completion Reference Reference to ETCM output
or completion state.
4. Total Temporal Span Overall governed span between temporal
endpoints.
5. Active Duration Supported period of constitutive event
activity.
6. Inactive Duration Supported period of inactivity within the
event span.
7. Interruption Record Governed interruption intervals.
8. Suspension Record Governed suspension intervals.
9. Phase Duration Record Temporal representation of relevant
event phases.
10. Overlap Record Representation of concurrent event components.
11. Distributed Duration Record Temporal representation across
distributed components.
12. Duration Precision Supported level of temporal precision.
13. Duration Uncertainty State Known uncertainty affecting
duration.
14. Duration Conflict State Known incompatible duration
representations.
15. Duration Correction History Governed revisions to duration.
16. Duration Governance State Established, approximate, bounded,
open, partial, conflicted, uncertain, insufficient, or corrected.
17. Governed Event Duration Principal ETDM output.
18. Handoff State Readiness for ETOM.
------------------------------ 29. Governance Outputs
ETDM may produce: Governed Event Duration Total Event Span Active
Event Duration Inactive Duration Record Event Interruption Record
Event Suspension Record Phase Duration Structure Overlapping
Duration Structure Distributed Duration Structure Machine Event
Duration Record Autonomous Event Duration Record Open Duration
Indicator Partial Duration Indicator Duration Precision Record
Duration Uncertainty Indicator Duration Conflict Indicator
Duration Correction Record Duration Traceability Record Event
Temporal Order Governance Readiness State
The principal output is:
Governed Event Duration
This output proceeds to:ETOM — Event Temporal Order Module ------------------------------
30. Critical Distinctions
Elapsed Clock Time ≠ Governed Event
Duration by Default
Total Temporal Span ≠ Active Event
Duration by Default
Continuous Event Duration ≠ System
Processing Window by Default
Temporal Discontinuity ≠ New Event by
Default
System Activity ≠ Event Activity by
Default
Inactive Time ≠ Event Absence by Default
Interruption ≠ Completion
Resumption ≠ New Event Start by Default
Operational Suspension ≠ Legal Suspension
Sum of Phase Durations ≠ Event Duration by
Default
Aggregate Component Time ≠ Elapsed Event
Duration
Distributed Event Duration ≠ Duration of
One Component
Machine Precision ≠ Governed Duration
Precision
Autonomous System Runtime ≠ Governed Event
Duration by Default
Elapsed Time To Date ≠ Final Event
Duration
Failed Event ≠ Zero Duration
Precise Calculation from Imprecise Inputs
≠ Precise Governed Duration
Mathematical Exactness ≠ Governance
Certainty
Duration Correction ≠ Historical Erasure
Event Duration ≠ Event Temporal Order
Event Duration ≠ Tax Period Determination
Event Duration ≠ Accounting Period
Event Duration ≠ Reporting Period
Event Duration ≠ Billing Period
Governed Event Duration ≠ Legal Tax Duration------------------------------ 31. Enterprise Application
ETDM can support duration governance across: ERP systems,
financial infrastructure, payment platforms, digital
marketplaces, e-commerce systems, manufacturing environments,
logistics networks, service platforms, SaaS infrastructure,
industrial automation, robotics, autonomous agents, AI-operated
systems, machine-to-machine environments, IoT systems,
distributed computing, digital assets, cross-border transactions,
accounting infrastructure, tax technology systems.
ETDM provides these systems with a common operational
representation of how long an event persisted before downstream
legal, accounting, reporting, or taxation frameworks interpret
that temporal reality. ------------------------------ 32.
Real-System Use Case 1 — Cross-Border Logistics Event with
Suspension and Multiple Operational Clocks
A governed logistics event begins when a shipment enters the
operational transport process at:
Monday 08:00
Transport proceeds until:Monday 16:00
The shipment is then held because an external infrastructuredependency prevents continuation.
Transport resumes:
Tuesday 06:00
Physical delivery completes:Tuesday 12:00
The carrier's administrative system closes the shipment at:Tuesday 15:30
Financial settlement occurs on Wednesday.Several duration representations are therefore possible.
A simple calculation from Monday 08:00 to Tuesday 15:30 would
incorrectly include post-event administrative processing.
A calculation from Monday 08:00 to Tuesday 12:00 establishes the
overall operational span but includes the suspension period.
Active transport duration may represent a different operational
measure.
ETDM preserves these distinctions through governed
representations of:
Total Event Span
Active Duration
Suspension Duration
and:Governed Event Duration
The downstream tax infrastructure may later determine which taxperiod, reporting period, jurisdictional rule, or legal tax point
applies.
ETDM does not make that decision.
Operational duration describes how the event persisted in
reality; it does not decide how a jurisdiction places that event
into tax law. ------------------------------ 33. Real-System Use
Case 2 — Autonomous Distributed AI Operation Across Multiple
Machines
An autonomous industrial AI initiates a governed optimization
event at:
14:00:00
Machine A begins execution immediately.
Machine B begins at:
14:00:08
Machine C begins at:
14:00:15
Machine A completes its component at:
14:03:40
Machine B temporarily pauses for 35 seconds and completes at:
14:04:12
Machine C completes at:
14:04:05
The autonomous orchestration layer completes the governed
operational objective at:
14:04:20
Diagnostic monitoring continues until:
14:07:00
System logs remain active for another ten minutes.
Adding the runtime of Machines A, B, and C would significantly
overstate the elapsed duration because their operations overlap.
Using the final diagnostic timestamp would also extend the event
beyond its constitutive operational activity.
ETDM constructs the governed duration from the temporal structure
of the bounded autonomous event.
It can preserve: overall event span, component execution
durations, overlapping intervals, pause duration, distributed
execution, autonomous completion.
The resulting Governed Event Duration can then enter downstream
Event Temporal Order governance without treating system runtime
or aggregated machine execution time as the event's temporal
extent.
In autonomous and distributed systems, more machine time does not
necessarily mean more event time. ------------------------------
34. Canonical Boundary
ETDM governs the construction, representation, qualification,
precision, uncertainty, conflict, correction, and traceability of
the temporal duration of the Governed Bounded Event using the
temporal conditions established through TRETS.
It owns: Total Event Span, Active Duration, Inactive Duration,
interruption duration, suspension duration, phased duration,
overlapping duration, distributed duration, machine and
autonomous duration representation, open duration, approximate
duration, bounded duration, duration uncertainty, duration
conflict, duration correction, duration traceability.
ETDM does not own Event Time Identification, independently
redefine Event Start, independently redefine Event Completion,
determine final Event Temporal Order, redefine Event Boundary,
determine Event Location, determine Event Participation, govern
Value Association, establish Event Relationships, perform final
Event Determination, determine Legal Tax Point, determine Tax
Period, determine Tax Jurisdiction, determine Taxpayer status,
calculate tax liability, or establish jurisdiction-specific tax
consequences.
ETDM receives:
ETSM — Governed Event Start
and:ETCM — Governed Event Completion
ETDM produces:Governed Event Duration
The output is handed to:ETOM — Event Temporal Order Module
The canonical handoff is:ETSM — Governed Event Start + ETCM — Governed Event Completion
↓
ETDM — Governed Event Duration
↓
ETOM — Event Temporal Order
Module ------------------------------ 35. Canonical Closing
Statement
ETDM establishes how long the governed event persisted in
operational reality while preserving the difference between
elapsed time, active time, interrupted time, distributed
execution, and downstream legal or administrative periods.
ETDM governs the duration of the event — not the tax period into
which a jurisdiction may later place it.
TREGA™ governs the event. The jurisdiction governs the tax.