The Event Determination Decision Module (EDDM)
governs how the results of
OOF™ Origin Open Foundation™
Independent Methodological Authority
Architecture Ecosystem: Structured Reality Standards™
Architecture Family: TREGA™ — Tax-Relevant Event Governance Architecture™
Parent Standard: TREDS — Tax-Relevant Event Determination Standard
Module: EDDM — Event Determination Decision Module
Operational Layer: Event Determination Decision Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Core Module
Governed Space: Event Determination Decision
Origin ID: TREGA-TREDS-EDDM-003
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 2 September 2026
AI-Readable: Yes
Authority: OOF®
Protection: MIP® — Methodological Intellectual Property
Canonical Language: UCL — Universal Canonical Language
Canonical Definition
The Event Determination Decision Module (EDDM) governs how theresults of Determination Readiness and Determination Conditions
governance are converted into a formal Tax-Relevant Event
Determination Decision.
EDDM determines the governed Event status that follows from the
available readiness, condition, qualification, coherence,
uncertainty, and conflict information at the point of decision.
Its principal transition is:
Governed Determination Condition State
↓
Determination Decision
Governance
↓
Governed Event Determination Decision
EDDM does not determine legal taxability.
It does not determine tax jurisdiction, taxpayer status, taxable
value, Tax Base, Tax Rate, legal tax point, Tax Liability,
exemption, deduction, filing obligation, collection, enforcement,
or any other jurisdiction-specific tax consequence.
Its foundational distinction is:
Event Determination Decision ≠ Tax Decision.
Operational Role
EDDM is the formal decision layer of TREDS.EDRDM determines whether the Event is ready for formal
Determination.
EDCM determines whether the applicable Determination Conditions
are satisfied.
EDDM then answers:
What formal TREGA™ Determination state should this Event receive?
The Decision may be: Positive; Conditional; Deferred; Rejected;
Ambiguous; Conflicted; or otherwise qualified.
EDDM transforms prior governance into an explicit and traceable
Determination outcome.
Internal Module Flow
TREDS operates through:EDRDM — Event Determination Readiness
↓
EDCM — Event
Determination Conditions
↓
EDDM — Event Determination Decision
↓
EDUM — Event Determination Uncertainty
↓
EDREM — Event
Determination Reconsideration
↓
Determined Tax-Relevant Event
EDDM is the third Core Module.
Its output is passed to EDUM for Determination-level uncertainty
governance where required.
Operational Transition
The canonical transition is:Governed Determination Condition State + Readiness State +
Relevant Qualifications
↓
Decision Evaluation
↓
Governed Event
Determination Decision
Possible outputs include:
Tax-Relevant Event Determined
Conditionally Determined
Determination Deferred
Determination Rejected
Determination Ambiguous
Determination Conflicted
Determination Escalation Required
Determination Reconsideration Flagged
The Decision shall always be explicit.Operational Space
EDDM governs: decision initiation; decision basis; decisioneligibility; decision state selection; positive determination;
conditional determination; deferred determination; rejected
determination; ambiguous determination; conflicted determination;
decision qualification; decision rationale; decision consistency;
decision provenance; decision traceability; decision authority
reference; decision timing; decision finalization; decision
handoff; and decision-level governance control.
Operational Scope
EDDM may govern Event Determination Decisions arising from:commerce; marketplaces; banking; payments; accounting; ERP;
logistics; supply chains; digital platforms; digital assets;
blockchain systems; smart contracts; AI agents; autonomous
systems; industrial systems; energy systems; distributed
infrastructure; cross-border operations; machine-to-machine
activity; and future machine economies.
The decision logic remains technology-neutral and
jurisdiction-neutral.
Decision Object
The Decision Object is the governed Event represented through:the EDRDM Readiness State; the EDCM Condition State; relevant
upstream governance references; material qualifications;
uncertainty indicators; and conflict indicators.
EDDM decides the TREGA™ status of this governed Event.
It does not decide the legal tax status.
Decision Initiation
Decision governance begins when EDCM establishes a sufficientlygoverned Determination Condition State.
EDDM shall not begin a formal Decision process where required
condition governance remains absent.
Decision Initiation ≠ Positive Determination.
Decision Eligibility
An Event is decision-eligible where the relevant Readiness andCondition governance provides enough basis for EDDM to issue a
formal status.
Decision eligibility does not require that the result will be
positive.
A Decision may still be: Deferred; Rejected; Conflicted; or
Conditional.
Decision Eligible ≠ Determination Positive.
Decision Basis
Every Determination Decision shall be linked to its governancebasis.
The Decision basis may include: Readiness State; Condition State;
material qualifications; unresolved issues; conflict state;
uncertainty state; upstream referrals; governance traceability.
A Decision without a reconstructable basis shall not qualify as a
governed Decision.
Decision Output Without Decision Basis ≠ Governed Decision.
Positive Determination
A Positive Determination means that the Event is sufficientlygoverned to be formally recognized within TREGA™ as a
Tax-Relevant Event.
It means:
The Event is eligible for downstream jurisdiction-specific
taxation analysis.
It does not mean:
Tax is legally due.
Therefore:
Positive Event Determination ≠ Positive Tax Determination.
Conditional Determination
A Conditional Determination may be issued where the Event issufficiently governed for controlled downstream use but one or
more bounded qualifications remain.
These qualifications shall be explicit.
Conditional Determination ≠ Unqualified Determination.
The downstream system shall be able to identify the conditions
attached to the Decision.
Deferred Determination
A Deferred Determination means that the Event cannot yet receivea final Determination state because materially necessary
governance remains unresolved.
Deferral may result from: unresolved condition; material
uncertainty; material conflict; unstable Event structure;
unresolved upstream referral; or pending structural
reconsideration.
Deferred Determination ≠ Rejected Determination.
Rejected Determination
A Rejected Determination means that the governed Event structuredoes not support establishment of a Tax-Relevant Event under
TREGA™ at that time.
Rejection may occur where the apparent Event fails a foundational
governance requirement.
Examples may include: invalid Event Formation; non-establishable
Event Boundary; duplicate technical artifact; purely technical
operation incorrectly treated as an Event; or materially
incoherent Event structure.
Rejected Determination ≠ Legal Non-Taxability.
Ambiguous Determination
A Determination may remain Ambiguous where more than onematerially plausible Event interpretation remains and the
available governance does not support a single stable Decision.
Ambiguity shall remain visible.
Ambiguity ≠ Permission to Choose the Convenient Decision.
Conflicted Determination
A Determination may be Conflicted where materially authoritativegovernance inputs support incompatible outcomes.
The Decision shall preserve the conflict rather than collapse it
artificially.
Decision Conflict ≠ Decision Discretion without Governance Basis.
Decision Qualification
A Decision may contain a qualification.Qualification may relate to: bounded uncertainty; incomplete
geographic precision; limited participant certainty; partial
Value Association; conditional Relationship structure;
provisional source availability; or another materially relevant
limitation.
The qualification shall not disappear when the Event moves
downstream.
Decision Finality
EDDM may establish operational finality sufficient for downstreamprocessing.
This does not mean absolute or legal finality.
A later correction or reconsideration may change the Decision.
Operational Decision Finality ≠ Legal Finality.
Decision Consistency
EDDM shall apply consistent decision logic across materiallycomparable Events.
Consistency does not require identical outcomes where Event
circumstances differ.
Decision Consistency ≠ Mechanical Uniformity.
The governing principle is methodological consistency.
Decision Rationale
A formal Decision shall be accompanied by sufficient rationale toreconstruct why the Decision state was selected.
The rationale should identify: the Event under review; the
Readiness State; the relevant Condition State; material satisfied
conditions; material unsatisfied or qualified conditions;
material uncertainty; material conflict; and the reason for the
resulting Decision.
Decision Provenance
The Decision shall preserve provenance to the governanceinformation from which it arose.
This may include references to: upstream Parent Standards; EDRDM
readiness evaluation; EDCM condition evaluation; relevant system
or governance-source identifiers; previous Decision states.
Decision Provenance ≠ Identity Provenance.
OBIDENITY® remains authoritative for broader identity and origin
governance.
Decision Traceability
The Determination Decision shall remain reconstructable.A reviewer should be able to identify: what was decided; why; on
what governance basis; under which qualifications; with what
uncertainty; and whether the Decision later changed.
EDDM owns Decision traceability.
ADIT® may govern broader evidential or audit requirements.
Decision Authority
The Decision process may be: automated; human; hybrid; delegated;rules-based; AI-assisted.
EDDM requires the Decision authority or process reference to
remain identifiable.
It does not assign organizational accountability.
AGA™ remains authoritative for accountability governance.
Decision Timing
The time at which the Determination Decision was made should becaptured separately from the Event Timing itself.
Decision Time ≠ Event Time.
and:
Decision Time ≠ Legal Tax Point.
Decision Sequence
Where repeated Decision processes occur, Decision sequence may bepreserved.
For example:
Initial Decision
↓
Qualification
↓
Correction
↓
Reconsideration
This does not alter the underlying Event Sequence governed by
TRERLS.
Decision Sequence ≠ Event Sequence.
Positive Decision Threshold
A Positive Determination should require that: the Event issufficiently ready; materially required conditions are
sufficiently satisfied; remaining qualifications are compatible
with downstream use; no unresolved issue fundamentally undermines
Event Identity or structure; and the Decision basis is
reconstructable.
The threshold is methodological sufficiency.
It is not a jurisdiction-specific tax threshold.
Conditional Decision Threshold
A Conditional Determination may be appropriate where: Eventidentity is stable; material Event structure is sufficient;
remaining limitations are bounded; downstream interpretation
remains possible; the qualification is explicit.
Conditional Determination shall not be used to hide a
fundamentally unresolved Event.
Deferred Decision Threshold
Deferral is appropriate where material issues remain unresolvedbut the Event may become determinable later.
Deferral should preserve: reason; required follow-up; affected
governance layer; and current Decision state.
Rejected Decision Threshold
Rejection should require a sufficiently governed basis showingthat the apparent Event does not qualify as a governed
Tax-Relevant Event.
Rejection shall not be based merely on: low tax value; no
expected Tax Liability; jurisdictional exemption; or reporting
convenience.
Low Tax Relevance under Law ≠ TREGA™ Rejection Criterion.
Decision and Readiness
EDDM consumes the Readiness State.It does not reperform readiness governance.
Decision ≠ Readiness Assessment.
If Readiness becomes invalid, the matter should be referred back
to EDRDM.
Decision and Conditions
EDDM consumes the Condition State.It does not reperform condition governance.
Decision ≠ Condition Evaluation.
If the Condition basis materially changes, EDCM remains
authoritative.
Decision and Uncertainty
EDDM may identify uncertainty affecting the Decision.EDUM governs Determination-level uncertainty in greater detail.
Therefore:
Decision Uncertainty Recognition ≠ Full Uncertainty Governance.
Decision and Reconsideration
EDDM may flag that reconsideration is required.EDREM owns the reconsideration process.
Decision Change ≠ Determination Reconsideration by default.
Decision and Event Recognition
TRERS decides whether an occurrence should enter Eventgovernance.
EDDM decides the formal Determination state after the Event has
passed through the necessary governance layers.
Recognition Decision ≠ Determination Decision.
Decision and Event Formation
EDDM cannot use a positive Decision to override defectiveFormation.
Positive Decision ≠ Formation Authority.
TREFS remains authoritative.
Decision and Event Boundary
EDDM cannot redefine Event Boundary.Decision ≠ Boundary Redetermination.
TREBS remains authoritative.
Decision and Event Timing
EDDM cannot determine legal tax timing.Event Determination Decision ≠ Legal Tax Point Determination.
TRETS remains authoritative for Event Timing.
Decision and Event Location
EDDM may rely on governed Location information.It does not determine the taxing jurisdiction.
Positive Determination ≠ Tax Jurisdiction Determination.
Decision and Participation
EDDM may rely on governed Participant structure.It does not determine who is legally the taxpayer.
Positive Determination ≠ Taxpayer Determination.
Decision and Value
EDDM may rely on governed Value Association.It does not determine taxable amount.
Positive Determination ≠ Tax Base Determination.
Decision and Relationships
EDDM may rely on a Governed Event Relationship Structure.It does not merge, split, group, sequence, or otherwise recreate
relationships.
Decision ≠ Relationship Governance.
Decision after Merge
Where ERLMM has governed a Merge and the resulting Event hascompleted relevant upstream governance, EDDM may issue a Decision
for the resulting Event.
The resulting Event shall not inherit the prior Decision
automatically.
Merged Event ≠ Automatically Determined Event.
Decision after Split
Each resulting Event after a governed Split may require its ownDetermination Decision.
Split Event ≠ Automatically Determined Event.
Decision after Correction
Where an upstream correction materially changes the Eventstructure, the existing Decision may become invalid or require
reconsideration.
EDDM may identify the Decision impact.
EDREM governs broader reconsideration.
Technical Record Decisions
A system may label a transaction as: taxable; non-taxable;completed; posted; settled; final; reconciled.
These labels do not constitute TREGA™ Determination Decisions.
System Status ≠ Governed Event Determination Decision.
Accounting Decisions
Accounting classification may inform Event governance but doesnot replace EDDM.
Accounting Classification ≠ Event Determination Decision.
Invoice Decisions
An invoice-status engine cannot determine by itself whether theunderlying activity is a governed Tax-Relevant Event.
Invoice Status ≠ Event Determination Decision.
Payment Decisions
Payment completion does not establish Event Determination.Payment Completion ≠ Event Determination Decision.
Blockchain Finality
Blockchain finality establishes technical ledger state.It does not establish Tax-Relevant Event Determination.
Blockchain Finality ≠ Event Determination Decision.
Smart-Contract Completion
Smart-contract completion does not establish Determination.Smart-Contract Completion ≠ Event Determination Decision.
AI Classification
An AI system may propose a Decision state.That proposal remains subject to EDDM governance.
AI Classification ≠ Governed Determination Decision.
AI Confidence
Model confidence may support the Decision process.It cannot substitute for the Decision itself.
Model Confidence ≠ Decision.
Autonomous Decisioning
EDDM supports autonomous Determination processes where governancerequirements are satisfied.
Autonomy does not remove: Decision basis; Decision rationale;
qualification; traceability; or authority reference.
Automated Decision ≠ Ungoverned Decision.
Cross-System Decision
The same governed Event may appear in multiple systems.EDDM shall seek one governed Determination Decision for the
governed Event rather than one Decision per technical record.
Multiple Records ≠ Multiple Determination Decisions by default.
Cross-Organization Decision
The Event may involve several organizations.Different organizations may hold separate records or internal
classifications.
EDDM governs the TREGA™ Event Decision, not organizational tax
positions.
Multiple Organizational Views ≠ Multiple Event Realities.
Cross-Border Decision
A cross-border Event may receive a Positive Determination whileTax Jurisdiction remains unresolved downstream.
Cross-Border Positive Determination ≠ Jurisdiction Allocation.
Multi-Jurisdiction Decision Reuse
One governed Determination Decision may support multipledownstream jurisdictional evaluations.
The model is:
One Governed Event Determination Decision
↓
Multiple Jurisdictional Tax Evaluations
This is a core TREGA™ infrastructure
function. Jurisdiction-Neutrality
EDDM shall preserve a jurisdiction-neutral Decision.The Decision states:
This Event is sufficiently governed as Tax-Relevant.
It does not state:
This jurisdiction may tax it.
Jurisdiction-Neutral Determination ≠ Jurisdictional Tax Decision.
Decision and Taxability
This boundary is absolute.Event Determination Decision ≠ Taxability Determination.
Taxability belongs to downstream law.
Decision and Tax Jurisdiction
Event Determination Decision ≠ Tax Jurisdiction Determination.Decision and Taxpayer
Event Determination Decision ≠ Taxpayer Determination.Decision and Tax Base
Event Determination Decision ≠ Tax Base Determination.Decision and Tax Rate
Event Determination Decision ≠ Tax Rate Determination.Decision and Tax Period
Event Determination Decision ≠ Tax Period Determination.Decision and Tax Liability
Event Determination Decision ≠ Tax Liability Determination.Decision and Legal Characterization
A jurisdiction may later legally characterize the Eventdifferently from TREGA™ operational terminology.
Event Determination Decision ≠ Legal Tax Characterization.
Decision State Preservation
Every materially relevant Decision state shall remainhistorically traceable.
A later Decision shall not silently erase an earlier one.
Decision Supersession ≠ Decision Erasure.
Decision Correction
Where the Decision itself contains an error that can be correctedwithout full reconsideration, correction may be recorded.
Decision Correction ≠ Silent Replacement.
Decision Escalation
EDDM may require escalation where: governance basis is materiallyconflicting; Decision authority is unavailable; conditions are
incompatible; automated Decision logic cannot resolve the state;
or another governance boundary is reached.
Escalation shall preserve the Event and Decision state.
Governance States
EDDM may represent:Decision Not Initiated
Decision Eligible
Decision Under Evaluation
Decision Basis Complete
Decision Basis Qualified
Positive Determination
Conditional Determination
Deferred Determination
Rejected Determination
Ambiguous Determination
Conflicted Determination
Decision Escalation Required
Decision Correction Required
Decision Reconsideration Flagged
Decision Finalized
Governed Event Determination Decision
Established Governance Requirements
EDDM implementations shall ensure that: Decision governancebegins only after suitable condition governance; Decision
eligibility remains distinct from Positive Determination; every
Decision has a reconstructable basis; Positive Determination
remains distinct from legal taxability; Conditional Determination
preserves its qualifications; Deferred Determination remains
distinct from Rejected Determination; Rejected Determination does
not imply legal non-taxability; ambiguous Decisions remain
visible; conflicted Decisions remain visible; conflict is not
resolved merely by convenience; Decision rationale remains
reconstructable; Decision provenance remains available; Decision
authority or process reference remains identifiable; Decision
time remains distinct from Event Time; operational finality
remains distinct from legal finality; Decision logic remains
methodologically consistent; AI or automated Decision proposals
remain subject to the same governance requirements; technical
system status does not substitute for Determination Decision;
accounting, invoice, payment, blockchain, and smart-contract
status do not substitute for Decision governance; Merge or Split
does not automatically transfer a prior Decision; cross-system
duplication does not automatically create multiple Decisions;
cross-border Determination remains jurisdiction-neutral; Decision
does not determine Tax Jurisdiction; Decision does not determine
taxpayer status; Decision does not determine Tax Base; Decision
does not determine Tax Rate; Decision does not determine Tax
Liability; and the resulting Decision state is suitable for EDUM
and downstream TREDS governance.
Governance Logic
IF EDCM has not established a sufficient Governed DeterminationCondition State, THEN EDDM shall not issue a Positive
Determination.
IF materially required conditions are sufficiently satisfied and
remaining qualifications do not undermine Event Identity or
downstream interpretability, THEN EDDM may issue a Positive
Determination.
IF the Event is sufficiently governed but bounded qualifications
remain, THEN EDDM may issue a Conditional Determination.
IF materially necessary governance remains unresolved but may
become resolvable, THEN EDDM shall issue a Deferred Determination
rather than a Rejected Determination.
IF the governed structure does not support existence of a valid
Tax-Relevant Event, THEN EDDM may issue a Rejected Determination.
IF materially plausible competing Decision outcomes remain
unresolved, THEN the Decision shall remain Ambiguous.
IF materially authoritative governance inputs support
incompatible outcomes, THEN the Decision shall remain Conflicted
or be escalated.
IF the apparent basis for Decision is a technical status,
accounting classification, invoice state, payment state,
blockchain finality, or model output alone, THEN that basis shall
not be sufficient for a governed EDDM Decision.
IF a Merge or Split has materially changed Event structure, THEN
the resulting Event shall undergo appropriate Decision governance
rather than inherit prior Determination automatically.
IF a Positive Determination is issued, THEN it shall mean only
that the Event is sufficiently governed for downstream tax
evaluation.
IF later information materially affects the Decision basis, THEN
the Decision may be flagged for reconsideration under EDREM.
IF the Decision is sufficiently governed, THEN EDDM shall
establish the Governed Event Determination Decision and hand it
to EDUM where uncertainty governance is required.
Minimum Implementation Framework
A minimum EDDM implementation should support:Decision Identifier A stable identifier for the Determination
Decision.
Governed Event Reference The Event under Determination.
Readiness State Reference The relevant EDRDM output.
Condition State Reference The relevant EDCM output.
Decision Eligibility State Whether the Event is eligible for
formal Decision.
Decision Basis Reference The governance basis supporting the
Decision.
Decision State Positive, Conditional, Deferred, Rejected,
Ambiguous, Conflicted, or Escalation Required.
Decision Qualification Any bounded qualification attached to the
Decision.
Decision Rationale The governed reasoning supporting the selected
state.
Material Condition Summary The materially relevant conditions
supporting or preventing the Decision.
Unresolved Condition Reference Any unresolved condition affecting
the Decision.
Decision Uncertainty State Any uncertainty identified at the
Decision stage.
Decision Conflict State Any conflict identified at the Decision
stage.
Decision Authority / Process Reference The human, automated,
hybrid, delegated, or rule-governed Decision process.
Decision Time The time the Decision was formally established.
Decision Provenance Reference The governance lineage supporting
the Decision.
Decision Traceability Reference Information required to
reconstruct the Decision.
Prior Decision Reference Any previous Determination Decision for
the Event.
Decision Correction Reference Any correction of the Decision.
Decision Escalation Reference Any escalation resulting from the
Decision process.
Reconsideration Flag Whether the Decision requires EDREM review.
Jurisdiction-Neutrality State Confirmation that no
jurisdiction-specific tax conclusion has been embedded.
Taxability Boundary State Confirmation that the Decision does not
determine legal taxability.
Governance State The current EDDM governance state.
Handoff State Whether the Decision may proceed to EDUM or
downstream TREDS governance.
Governance Outputs
EDDM may produce: Decision Eligibility State; Decision BasisRecord; Positive Determination; Conditional Determination;
Deferred Determination; Rejected Determination; Ambiguous
Determination; Conflicted Determination; Decision Qualification;
Decision Rationale; Decision Provenance Record; Decision
Authority Reference; Decision Traceability Record; Decision
Correction; Decision Escalation; Reconsideration Flag;
Jurisdiction-Neutral Decision State; and the principal output:
Governed Event Determination Decision.
Critical Distinctions
Event Determination Decision ≠ Tax Decision.Decision Initiation ≠ Positive Determination.
Decision Eligible ≠ Determination Positive.
Decision Output Without Decision Basis ≠ Governed Decision.
Positive Event Determination ≠ Positive Tax Determination.
Conditional Determination ≠ Unqualified Determination.
Deferred Determination ≠ Rejected Determination.
Rejected Determination ≠ Legal Non-Taxability.
Ambiguity ≠ Permission to Choose the Convenient Decision.
Decision Conflict ≠ Decision Discretion without Governance Basis.
Operational Decision Finality ≠ Legal Finality.
Decision Consistency ≠ Mechanical Uniformity.
Decision Provenance ≠ Identity Provenance.
Decision Time ≠ Event Time.
Decision Sequence ≠ Event Sequence.
Low Tax Relevance under Law ≠ TREGA™ Rejection Criterion.
Decision ≠ Readiness Assessment.
Decision ≠ Condition Evaluation.
Decision Uncertainty Recognition ≠ Full Uncertainty Governance.
Decision Change ≠ Determination Reconsideration by default.
Recognition Decision ≠ Determination Decision.
Positive Decision ≠ Formation Authority.
Decision ≠ Boundary Redetermination.
Event Determination Decision ≠ Legal Tax Point Determination.
Positive Determination ≠ Tax Jurisdiction Determination.
Positive Determination ≠ Taxpayer Determination.
Positive Determination ≠ Tax Base Determination.
Decision ≠ Relationship Governance.
Merged Event ≠ Automatically Determined Event.
Split Event ≠ Automatically Determined Event.
System Status ≠ Governed Event Determination Decision.
Accounting Classification ≠ Event Determination Decision.
Invoice Status ≠ Event Determination Decision.
Payment Completion ≠ Event Determination Decision.
Blockchain Finality ≠ Event Determination Decision.
Smart-Contract Completion ≠ Event Determination Decision.
AI Classification ≠ Governed Determination Decision.
Model Confidence ≠ Decision.
Automated Decision ≠ Ungoverned Decision.
Multiple Records ≠ Multiple Determination Decisions by default.
Multiple Organizational Views ≠ Multiple Event Realities.
Cross-Border Positive Determination ≠ Jurisdiction Allocation.
Jurisdiction-Neutral Determination ≠ Jurisdictional Tax Decision.
Event Determination Decision ≠ Taxability Determination.
Event Determination Decision ≠ Tax Jurisdiction Determination.
Event Determination Decision ≠ Taxpayer Determination.
Event Determination Decision ≠ Tax Base Determination.
Event Determination Decision ≠ Tax Rate Determination.
Event Determination Decision ≠ Tax Period Determination.
Event Determination Decision ≠ Tax Liability Determination.
Event Determination Decision ≠ Legal Tax Characterization.
Decision Supersession ≠ Decision Erasure.
Decision Correction ≠ Silent Replacement.
Enterprise Application
EDDM provides the formal decision point at which a sufficientlygoverned Event receives its TREGA™ Determination status.
A typical operational path is:
EDRDM — Governed Determination Readiness
State
→ EDCM — Governed Determination Condition State→ EDDM — Governed Event Determination Decision
→ EDUM — Event Determination Uncertainty Governance
→ EDREM — Event Determination Reconsideration
→ Determined Tax-Relevant Event
This gives enterprises a clear, reviewable answer to whether a
governed Event can formally enter downstream tax infrastructure
without allowing the Event layer itself to become a tax engine.
Use Case 1 — Cross-Border Marketplace Event with Conditional
Determination
A marketplace Event has completed Readiness governance and its
materially necessary Determination Conditions are satisfied.
However, one bounded digital Location qualification remains.
The uncertainty does not undermine Event Identity, Formation,
Boundary, Participation, Value Association, or Event
Relationships.
EDDM issues a Conditional Determination and preserves the
Location qualification for downstream processing.
The Event becomes eligible for jurisdiction-specific analysis.
EDDM does not determine which jurisdiction has taxing authority.
Use Case 2 — Machine-Generated Record Rejected as a Tax-Relevant
Event
An autonomous industrial system generates a technical record
every time a machine changes operating state.
One record enters TREGA™ because a downstream accounting system
incorrectly treats each machine state change as a separate
economic event.
Upstream governance establishes that the state change is merely
part of an already-governed service Event and does not possess
independent Event Formation or Boundary.
EDDM therefore issues a Rejected Determination for the apparent
standalone Event.
The rejection does not mean the broader service is non-taxable.
It means only that the technical machine-state record does not
qualify as an independent Tax-Relevant Event.
Canonical Boundary
EDDM owns the governance of Decision initiation, Decisioneligibility, Decision basis, Positive Determination, Conditional
Determination, Deferred Determination, Rejected Determination,
Ambiguous Determination, Conflicted Determination, Decision
qualification, Decision rationale, Decision consistency, Decision
provenance, Decision authority reference, Decision timing,
Decision traceability, Decision correction, Decision escalation,
and establishment of the Governed Event Determination Decision.
EDDM does not perform Determination Readiness governance,
Determination Condition governance, full Determination
Uncertainty governance, or Determination Reconsideration.
It does not perform Event Context, Recognition, Formation,
Boundary, Timing, Location, Participation, Value Association, or
Event Relationship governance.
It does not determine legal taxability, Tax Jurisdiction,
taxpayer status, legal tax point, Tax Period, Tax Base, Tax Rate,
Tax Liability, exemption, deduction, filing obligation, payment,
collection, enforcement, or any other jurisdiction-specific legal
tax consequence.
Its governance begins when EDCM establishes a Governed
Determination Condition State suitable for Decision.
Its governance ends when a formal Governed Event Determination
Decision has been established for handoff to EDUM and the
remaining TREDS process.
Canonical Handoff
EDCM — Governed Determination Condition State↓
EDDM — Governed
Event Determination Decision
↓
EDUM — Event Determination
Uncertainty Governance
Canonical Closing Statement
EDDM converts governed readiness and explicit determinationconditions into a formal Event Determination Decision without
allowing that decision to become a legal tax conclusion.
The decision establishes whether TREGA™ recognizes a sufficiently
governed Tax-Relevant Event. It does not decide what any
jurisdiction must tax.
Event Determination Decision ≠ Tax Decision.
Positive Event Determination ≠ Positive Tax Determination.
TREGA™ governs the event. The jurisdiction governs the tax.