Tax-Relevant Event Determination Standard - (TREDS)
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
Operational Layer: Tax-Relevant Event Determination Governance Layer
Category: Governance & Enforcement
Subcategory: Tax-Relevant Event Governance
Type: Parent Standard
Governed Space: Tax-Relevant Event Determination
Primary Governed Object: Tax-Relevant Event Determination
Origin ID: TREGA-TREDS-010
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 Tax-Relevant Event Determination Standard (TREDS) governs howan event that has passed through the preceding TREGA™ governance
layers is formally evaluated and determined to constitute a
sufficiently governed Tax-Relevant Event for downstream record
governance and jurisdiction-specific taxation analysis.
TREDS establishes whether the governed Event structure is
sufficiently complete, coherent, attributable, bounded,
temporally and spatially situated, participatory,
value-associated, relationship-aware, and methodologically
reliable to become a formal Tax-Relevant Event within TREGA™.
Its principal transition is:
Governed Event Relationship Structure
↓
Tax-Relevant Event Determination
↓
Determined Tax-Relevant Event
TREDS does not determine whether tax is legally due.
It does not determine the applicable jurisdiction, taxpayer, tax
base, tax rate, exemption, deduction, tax point, filing
obligation, or legal tax consequence.
Its foundational distinction is:
Event Determination ≠ Taxability Determination.
Purpose
The purpose of TREDS is to create a formal governance thresholdbetween:
an event that has been progressively structured by TREGA™
and:
an event that is sufficiently governed to be treated as
Tax-Relevant for downstream taxation analysis.
Without this threshold, downstream systems may consume:
incomplete events; unresolved events; contradictory events;
technically generated records; improperly bounded activities;
uncertain participant structures; unresolved Value Associations;
or unstable Event Relationships
as though they were fully governed taxation inputs.
TREDS prevents that failure.
It establishes a formal determination layer before the event
becomes a governed tax-relevant record.
Core Question
Has the event been governed sufficiently across the TREGA™lifecycle to become a formal Tax-Relevant Event suitable for
downstream jurisdiction-specific taxation analysis without
determining the tax itself?
Architecture Position
TREDS is Parent Standard 10 of 12 within TREGA™.Its immediate position is:
Event Relationships
↓
Event Determination
↓
Governed Tax-Relevant Event Record
TREDS consumes the governed structures produced by the first nine
Parent Standards and determines whether the event is ready to
become a formal governed Tax-Relevant Event.
Complete TREGA™ Governance Flow
1. TRECS — Tax-Relevant Event Context Standard→ 2. TRERS — Tax-Relevant Event Recognition Standard
→ 3. TREFS — Tax-Relevant Event Formation Standard
→ 4. TREBS — Tax-Relevant Event Boundary Standard
→ 5. TRETS — Tax-Relevant Event Timing Standard
→ 6. TRELS — Tax-Relevant Event Location Standard
→ 7. TREPS — Tax-Relevant Event Participation Standard
→ 8. TRVAS — Tax-Relevant Value Association Standard
→ 9. TRERLS — Tax-Relevant Event Relationship Standard
→ 10. TREDS — Tax-Relevant Event Determination Standard ← CURRENT
→ 11. TREGS — Tax-Relevant Event Record Governance Standard
→ 12. TRECLS — Tax-Relevant Event Lifecycle & Continuity Standard
The complete system position remains:
Real-World / Digital Event
↓
TREGA™
↓
Governed Tax-Relevant Event
↓
Jurisdictional Tax Rules
↓
Tax Determination
↓
Reporting /
Compliance Governed Input
TREDS consumes the governed outputs produced by preceding TREGA™
layers.
These may include: Governed Event Context; Governed Event
Recognition; Governed Event Formation; Governed Event Boundary;
Governed Event Timing; Governed Event Location; Governed Event
Participation; Governed Value Association; Governed Event
Relationship Structure; associated uncertainty states; conflict
states; correction history; and relevant governance traceability.
TREDS does not recreate those determinations.
It evaluates whether, taken together, they are sufficient for
formal Event Determination.
Principal Governance Transition
The canonical transition is:Governed Event Relationship Structure + Upstream Governance State
↓
Determination Readiness
↓
Determination Conditions
↓
Determination Decision
↓
Determination Uncertainty /
Reconsideration
↓
Determined Tax-Relevant Event
The result may be: Tax-Relevant Event Determined; Determination
Deferred; Determination Conditional; Determination Uncertain;
Determination Conflicted; Determination Rejected; or
Determination Reconsideration Required.
Tax-Relevant Event Determination
Tax-Relevant Event Determination is the formal TREGA™ governancedecision that an event has been sufficiently governed to proceed
as a Tax-Relevant Event.
It answers:
Is this event sufficiently governed for taxation systems to
evaluate it?
It does not answer:
Is this event legally taxable?
That distinction is fundamental.
Tax-Relevant Event ≠ Legally Taxable Event.
Determination Readiness
An event shall not enter formal Determination merely because itexists in an operational system.
TREDS shall first establish whether the event is ready for
determination.
Readiness may require that all materially necessary upstream
governance areas are sufficiently established.
These include, where applicable: Context; Recognition; Formation;
Boundary; Timing; Location; Participation; Value Association;
Event Relationships.
Event Presence ≠ Determination Readiness.
Readiness Completeness
Determination readiness requires sufficient completeness for thespecific event.
This does not require infinite or total information.
It requires sufficient governed information to support a
defensible determination.
Determination Completeness ≠ Total Data Capture.
Missing immaterial information shall not automatically block
determination.
Missing materially necessary information shall.
Readiness Coherence
Upstream governance outputs shall be sufficiently coherent.For example: Event Boundary should not contradict Formation;
Timing should not contradict the governed Event structure;
Participant structure should fit the Event; Value Association
should refer to the governed Event; Event Relationships should
not conflict with Event Identity.
Material contradictions may prevent determination.
Data Availability ≠ Governance Coherence.
Readiness Stability
The event should be sufficiently stable to support formaldetermination.
A structure undergoing unresolved Formation, Boundary,
Participation, Value, or Relationship reconsideration may not yet
be ready.
However, perfect permanence is not required.
Governance Stability ≠ Immutability.
Determination Conditions
TREDS shall govern the conditions that must be satisfied before aTax-Relevant Event can be formally determined.
Conditions may include: Event Identity sufficiently established;
Event Formation sufficiently governed; Event Boundary
sufficiently governed; Event Timing sufficiently established;
Event Location sufficiently represented where material; Event
Participation sufficiently represented; material Value
Association sufficiently governed; material Event Relationships
sufficiently governed; material conflicts sufficiently resolved
or explicitly qualified; material uncertainty sufficiently
controlled; and sufficient traceability for downstream
reconstruction.
The conditions may vary according to event complexity.
The standard governs sufficiency, not identical data volume for
every event.
Material Sufficiency
TREDS operates on material sufficiency.The relevant question is not whether every possible data field
exists.
The question is whether the governed Event representation is
sufficient for downstream taxation evaluation without requiring
the tax system to reconstruct Event Reality itself.
More Data ≠ Greater Determination Quality by default.
Event Integrity at Determination
TREDS shall evaluate whether the event remains internallycoherent across its governed layers.
An event should not be formally determined where: Event Identity
is unresolved; Boundary materially conflicts with Formation;
Value Association materially contradicts Event structure;
Participant structure is fundamentally uncertain; or material
relationships remain incompatible with the event representation.
Determination is therefore a governance synthesis point.
It is not merely another classification label.
Determination Decision
The Determination Decision establishes the formal status of thegoverned Event.
Possible decisions include:
Tax-Relevant Event Determined
Determination Conditional
Determination Deferred
Determination Rejected
Determination Uncertain
Determination Conflicted
Determination Reconsideration Required
The decision shall be explicit.Silence shall not be interpreted as determination.
No Decision ≠ Positive Determination.
Positive Determination
A positive determination means that the event is sufficientlygoverned to become a formal Tax-Relevant Event.
It means:
Eligible for downstream jurisdiction-specific taxation analysis.
It does not mean:
Tax legally due.
Therefore:
Positive Event Determination ≠ Positive Tax Determination.
Conditional Determination
An event may be sufficiently governed for downstream processingwhile one or more explicitly bounded conditions remain.
Conditional determination may be appropriate where uncertainty is
controlled and does not invalidate the Event structure.
The condition shall remain visible.
Conditional Determination ≠ Unqualified Determination.
Deferred Determination
Determination shall be deferred where materially necessaryupstream governance remains incomplete.
Examples may include unresolved: Event Boundary; Event
Participation; Value Association; Event Relationship; or material
Event Identity questions.
Deferred Determination ≠ Rejected Event.
The event may become determinable after additional governance.
Rejected Determination
TREDS may reject formal Tax-Relevant Event Determination wherethe available governed structure does not support the existence
of a sufficiently constituted Tax-Relevant Event.
Rejection may result where: Recognition was incorrect; Formation
fails; Event Boundary cannot be established; the apparent event
is merely a technical artifact; or another fundamental governance
failure exists.
Determination Rejection ≠ Legal Non-Taxability.
It means the event does not currently satisfy TREGA™ requirements
for a governed Tax-Relevant Event.
Determination Uncertainty
Uncertainty does not automatically invalidate an event.TREDS shall distinguish between: immaterial uncertainty; bounded
uncertainty; material uncertainty; unresolved uncertainty.
The effect on determination shall depend on whether the
uncertainty prevents reliable downstream taxation analysis.
Uncertainty ≠ Automatic Determination Failure.
Material Uncertainty
Uncertainty becomes material where it could materially change thegoverned identity or structure of the Event.
Examples may include uncertainty over: whether one or several
events exist; which participant materially participated; which
governed Value Result belongs to the event; which Event Boundary
applies; or which relationship structure is valid.
Material uncertainty may require deferral or conditional
determination.
Determination Conflict
Conflicting upstream governance outputs may prevent reliabledetermination.
For example: one system represents one event; another represents
two events; one source identifies Participant A; another
identifies Participant B; one Value Association conflicts with
another.
TREDS shall preserve material conflict.
Conflict ≠ Permission to Select the Convenient Result.
Conflict Resolution Boundary
TREDS may evaluate whether a conflict prevents determination.It does not necessarily resolve the underlying subject matter
itself.
Where the conflict belongs to: Formation
↓
TREFS; Boundary
↓
TREBS; Timing
↓
TRETS; Location
↓
TRELS; Participation
↓
TREPS;
Value Association
↓
TRVAS; Event Relationships
↓
TRERLS,
the issue shall be referred to the authoritative upstream layer.
TREDS governs determination impact, not ownership of every
upstream issue.
Determination Confidence
TREDS may qualify confidence in the determination where useful.Possible states may include: High; Qualified; Limited;
Conditional; Ambiguous; Conflicted; Unresolved.
Confidence shall not replace the determination decision.
Confidence Score ≠ Determination Decision.
Determination Reasoning
A formal Determination shall be supported by reconstructablegovernance reasoning.
The reasoning should show: which event is being determined; which
upstream governed outputs were relied upon; what material
conditions were satisfied; what uncertainties remained; whether
conflicts existed; and why the resulting determination state was
reached.
Determination Result Without Governance Basis ≠ Governed
Determination.
Determination Traceability
The determination shall remain traceable to its upstreamgovernance lineage.
This allows downstream systems to understand not only that a
Tax-Relevant Event exists, but how that conclusion was reached.
Traceability supports: review; audit; correction;
reconsideration; cross-system interoperability; and
multi-jurisdiction evaluation.
TREDS does not replace TREGS Event Record Governance.
It establishes the determination information that TREGS will
formally structure into the governed Event Record.
Event Determination and Recognition
Recognition identifies that an occurrence may require TREGA™governance.
Determination decides whether the fully governed Event is ready
to become a Tax-Relevant Event.
Therefore:
Event Recognition ≠ Event Determination.
TRERS is the entry recognition layer.
TREDS is the formal downstream determination layer.
Event Determination and Formation
Formation establishes what constitutes the event.Determination evaluates whether that formed and subsequently
governed event is sufficiently complete.
Event Formation ≠ Event Determination.
TREDS cannot compensate for defective Formation by declaring the
event determined.
Event Determination and Boundary
Boundary establishes where the event begins and endsconceptually.
TREDS consumes that result.
Event Determination ≠ Event Boundary Determination.
Event Determination and Timing
TREDS does not determine Event Time.It evaluates whether the governed timing information is
sufficient where timing is material.
Event Determination ≠ Event Timing Determination.
and:
Event Determination ≠ Legal Tax Point Determination.
Event Determination and Location
TREDS may require sufficient Event Location information wherematerial.
However:
Event Determination ≠ Tax Jurisdiction Determination.
Event Location remains operationally governed by TRELS.
Jurisdictional tax nexus remains downstream.
Event Determination and Participation
TREDS consumes the governed participation structure.It does not determine taxpayer status.
Event Participant ≠ Taxpayer.
and:
Event Determination ≠ Taxpayer Determination.
Event Determination and Value
TREDS may require sufficient Value Association where materiallyrelevant.
It does not determine taxable value.
Governed Value Association ≠ Taxable Value.
and:
Event Determination ≠ Tax Base Determination.
Event Determination and Event
Relationships
TREDS consumes the Governed Event Relationship Structure fromTRERLS.
It evaluates whether relationship ambiguity or structural
conflict prevents determination.
It does not recreate the Event Relationship structure.
Event Determination ≠ Event Relationship Redetermination.
Determination of Independent Events
Several strongly related events may each receive independentTax-Relevant Event Determination.
Relationship strength does not eliminate Event Identity.
Related Events ≠ One Determined Event by default.
Determination of Event Groups
Events belonging to one Event Group may still require individualEvent Determination where they retain separate Event Identities.
Event Group ≠ Determination Unit by default.
The governed Event Identity remains primary.
Determination after Merge
Where ERLMM establishes a governed Merge and Formation/Boundarygovernance support the resulting event, TREDS shall determine the
resulting governed Event representation.
Prior Event representations remain traceable.
Merged Representation ≠ Historical Erasure.
Determination after Split
Where an event has been legitimately split, each resultingindependently governed Event may require separate Determination.
Split Result ≠ Automatic Positive Determination.
Each resulting event must satisfy applicable TREDS conditions.
Determination and Technical Records
A technical record, transaction record, log entry, blockchaintransaction, API call, database object, invoice line, or
accounting entry is not automatically a determined Tax-Relevant
Event.
Technical Record ≠ Determined Tax-Relevant Event.
TREDS evaluates the governed Event, not the technical artifact.
Determination and Payments
A payment may constitute an independently governed event, formpart of another Event structure, or relate to several events.
TREDS does not assume:
Payment = Tax-Relevant Event
without preceding TREGA™ governance.Determination and Invoices
An invoice may provide evidence or operational structure.It does not itself establish Event Determination.
Invoice ≠ Tax-Relevant Event by default.
Determination and Contracts
A contract may contextualize one or many events.It does not itself establish a determined event.
Contract ≠ Tax-Relevant Event by default.
Determination and Blockchain Transactions
A blockchain transaction may correspond to: one event; part ofone event; several event relationships; or a purely technical
operation.
Therefore:
Blockchain Transaction ≠ Determined Tax-Relevant Event by
default.
TREDS relies on the complete governed Event structure.
Determination and Smart Contracts
Smart-contract execution does not automatically create oneTax-Relevant Event per call or transaction.
Smart-Contract Execution ≠ Tax-Relevant Event Determination.
Determination and AI Agents
AI agents may initiate or execute large numbers of activities.TREDS determines governed Tax-Relevant Events rather than
counting Agent Actions.
Agent Action ≠ Tax-Relevant Event by default.
Determination and Machine Activity
Machines may generate millions of technical operations.Only those operational structures that pass TREGA™ governance may
become determined Tax-Relevant Events.
Machine Operation Count ≠ Tax-Relevant Event Count.
Determination and Automation
Automated classification or detection systems may propose adetermination.
They shall not substitute for the governance conditions of TREDS.
Automated Classification ≠ Governed Event Determination.
Determination and AI Confidence Scores
AI systems may assign confidence or probability to a candidateEvent.
Such scores may inform governance.
They do not constitute the Determination itself.
Model Confidence ≠ Governance Determination.
Cross-System Determination
One event may be represented across several systems.TREDS shall determine the governed Event representation rather
than treating each system record as a separate Event.
System Record Count ≠ Event Count.
Cross-Organization Determination
The same broader Event may involve several organizations.TREDS may consume governed cross-organizational information
without deciding ownership, accountability, or tax liability.
Multiple Organizations ≠ Multiple Events by default.
Cross-Border Determination
An event may span several physical or digital locations.TREDS may still determine the event as Tax-Relevant without
deciding which jurisdiction may tax it.
Cross-Border Tax-Relevant Event ≠ Tax Jurisdiction Determination.
Multi-Jurisdiction Readiness
A central purpose of TREDS is to produce an event representationthat can support more than one legitimate downstream
jurisdictional evaluation.
The canonical model is:
One Determined Tax-Relevant Event
↓
Multiple Jurisdictional Tax Evaluations
TREDS therefore seeks to preserve the governed Event Reality
independently of later legal interpretation.
Jurisdiction-Neutral Determination
Determination conditions shall not be rewritten merely to fit onejurisdiction's tax law where the event is intended for
jurisdiction-neutral TREGA™ governance.
Legal rules may later consume the event differently.
TREGA™ does not permit downstream law to retroactively redefine
Event Reality.
Jurisdictional Interpretation ≠ Event Determination Authority.
Tax-Relevant ≠ Taxable
This is the central boundary of TREDS.
An event becomes Tax-Relevant when it is sufficiently governed
for taxation analysis.
It becomes legally taxable only if the applicable jurisdictional
rules establish that legal consequence.
The architecture therefore preserves:
Tax-Relevant Event
↓
Jurisdictional Tax Evaluation
↓
Legal Tax Determination
not:
Tax-Relevant Event = Taxable Event
Taxability Boundary
TREDS shall never determine: whether a supply is taxable; whetherincome is taxable; whether a transfer is taxable; whether VAT is
due; whether withholding applies; whether capital gains arise;
whether an exemption applies; or whether any other legal tax
consequence exists.
These belong downstream.
Tax Jurisdiction Boundary
TREDS may determine that Location governance is sufficient fordownstream evaluation.
It does not select the taxing jurisdiction.
Jurisdiction-Ready ≠ Jurisdiction-Determined.
Taxpayer Boundary
TREDS may consume governed Event Participation.It does not determine which participant is legally the taxpayer.
Participant ≠ Taxpayer.
Tax Base Boundary
TREDS may require that material Event–Value relationships aregoverned.
It does not convert governed value into legal Tax Base.
Value Association ≠ Tax Base.
Tax Rate Boundary
No TREDS Determination contains a tax rate.Determined Tax-Relevant Event ≠ Tax Rate Determination.
Tax Period Boundary
Event Timing may be available.TREDS does not translate operational timing into a
jurisdiction-specific taxable period.
Operational Event Time ≠ Legal Tax Period.
Legal Characterization Boundary
Tax law may later characterize the event as: sale; service;transfer; income; disposal; import; export; remuneration;
royalty; taxable benefit; or another legal category.
TREDS does not make that legal characterization unless such
terminology merely reflects an upstream governed operational
description.
Governed Event Determination ≠ Legal Tax Characterization.
Determination Readiness Across Different
Event Types
TREDS shall remain adaptable to different Event structures.A simple event may require relatively little information.
A distributed autonomous transaction may require significantly
more governance.
A multi-party cross-border event may require stronger Location,
Participation, Value, and Relationship representation.
The determination threshold shall therefore be materially
sufficient, not mechanically identical.
Proportional Governance
Determination governance should be proportionate to: Eventcomplexity; Event materiality; number of participants;
distributed nature; value complexity; relationship complexity;
uncertainty; cross-system fragmentation; and downstream reliance.
More Complex Event
↓
Greater Governance Demand
does not mean:
More Complex Event
↓
Different Canonical Principle.
The same governance boundary remains.
Determination Reliance
Once an event is positively determined, downstream systems mayrely on that determination as confirmation that the Event has
passed the required TREGA™ determination threshold.
This reliance shall remain bounded.
Downstream systems may rely on:
the governed Event representation
but not assume that TREDS has already made the legal tax
decision.
Downstream Tax Engine Consumption
A downstream tax engine may consume a Determined Tax-RelevantEvent and apply jurisdiction-specific rules.
The canonical handoff is:
Determined Tax-Relevant Event
↓
Governed Tax-Relevant Event
Record
↓
Jurisdiction-Ready Tax-Relevant Event
↓
Tax Engine
The tax engine should not need to reconstruct basic Event Reality
from raw operational records.
That is one of the principal infrastructure purposes of TREGA™.
Determination Reconsideration
A prior Event Determination may require reconsideration wherematerially relevant governance changes.
Examples include: corrected Event Boundary; corrected
Participant; revised Value Association; newly discovered Event
Relationship; Merge or Split; newly available operational
information; or correction of material upstream error.
TREDS shall preserve both the prior and reconsidered
determination states.
Reconsideration ≠ Historical Erasure.
Determination Supersession
A new Determination may supersede an earlier one.Supersession shall not erase the historical record.
Superseded Determination ≠ Deleted Determination.
TRECLS will govern longer-term lifecycle continuity.
Determination Correction
Where a determination contains an error that does not requirecomplete reconsideration of Event structure, a governed
correction may be issued.
Correction shall remain traceable.
Correction ≠ Silent Replacement.
Determination Finality
TREDS may establish operational finality sufficient fordownstream use.
This does not imply absolute legal finality.
Future corrections, evidence, or upstream governance changes may
justify reconsideration.
Governance Finality ≠ Legal Finality.
Determination Interoperability
A Determined Tax-Relevant Event should be representable acrosssystems without losing its core governance meaning.
Interoperability requires preservation of: Event identity;
determination status; relevant upstream governance references;
uncertainty; conflicts; and determination lineage.
Formal record structure belongs to TREGS.
Determination Auditability
A determination should be reviewable.The relevant reviewer should be able to establish: what event was
determined; on what governed basis; what conditions were
satisfied; what uncertainty remained; who or what governance
process produced the result; and whether the determination was
later corrected or reconsidered.
ADIT® may govern broader audit and evidential requirements.
TREDS owns the determination governance itself.
Determination Validation Boundary
VALIDOS™ may validate a methodology, system, evidence structure,or determination process.
TREDS does not replace validation architecture.
Event Determination ≠ Validation.
Determination Integrity Boundary
INTEGROS® may govern broader integrity requirements.TREDS requires sufficient determination integrity but does not
absorb the full integrity architecture.
Determination Accountability Boundary
AGA™ may govern accountability for decisions, roles, andfailures.
TREDS determines Event status, not accountability.
Determination Authority ≠ Accountability Assignment.
Cross-Architecture Governance Boundary
TREDS shall preserve the following ownership structure:ORA™ Governs what occurred operationally.
TREFS Governs Event Formation.
TREBS Governs Event Boundary.
TRETS Governs Event Timing.
TRELS Governs Event Location.
TREPS Governs Event Participation.
TRVAS Governs Event–Value Association.
TRERLS Governs relationships among Events.
TREDS Governs whether the resulting Event is sufficiently
governed to become a formal Tax-Relevant Event.
TREGS Governs the resulting Event Record.
TRECLS Governs Event lifecycle and continuity.
OBIDENITY® Governs identity, origin, ownership, authority,
permission, and provenance.
VFM® — Value Flow Mechanism Governs what happened to value
throughout its lifecycle.
ADIT® Governs evidence and auditability.
VALIDOS™ Governs validation.
AGA™ Governs accountability.
Jurisdiction-Specific Tax System Determines legal tax
consequences.
Governance States
TREDS may represent:Determination Not Ready
Determination Readiness Under Review
Determination Ready
Determination Conditions Incomplete
Determination Conditions Satisfied
Determination Conditional
Determination Deferred
Determination Rejected
Determination Uncertain
Determination Ambiguous
Determination Conflicted
Determination Under Reconsideration
Determination Corrected
Determination Superseded
Tax-Relevant Event Determined
Determined Tax-Relevant Event Ready for
Record Governance Governance Requirements
TREDS shall require that: Event Determination occurs only aftermaterially necessary upstream TREGA™ governance; Event
Determination remains distinct from Event Recognition; Event
Determination remains distinct from Event Formation; Event
Determination remains distinct from Taxability Determination;
Determination Readiness is explicit; material determination
conditions are identifiable; completeness is assessed according
to material sufficiency rather than total data capture;
materially contradictory upstream governance is not silently
ignored; determination uncertainty remains visible; determination
conflict remains visible; positive, conditional, deferred,
rejected, and reconsidered determination states remain
distinguishable; positive Event Determination does not imply
positive Tax Determination; tax jurisdiction remains downstream;
taxpayer status remains downstream; Tax Base remains downstream;
Tax Rate remains downstream; tax period remains downstream; legal
tax characterization remains downstream; downstream systems can
identify the governance basis for the determination;
determination reasoning remains reconstructable; determination
corrections remain traceable; determination reconsideration
preserves prior history; supersession does not erase prior
determination states; cross-system representation does not create
duplicate Event Determinations; cross-border Event Determination
remains jurisdiction-neutral; AI-generated or automated
determinations remain subject to TREDS governance; and the
resulting Determined Tax-Relevant Event is suitable for TREGS
Record Governance.
Governance Logic
IF the governed Event has not completed materially necessaryupstream TREGA™ governance, THEN formal Tax-Relevant Event
Determination shall not occur.
IF materially necessary Event Context, Formation, Boundary,
Timing, Location, Participation, Value Association, or Event
Relationship governance remains unresolved, THEN Determination
shall be deferred, conditioned, or otherwise qualified according
to material impact.
IF the governed Event structure is sufficiently complete,
coherent, stable, and reconstructable for downstream taxation
analysis, THEN a positive Tax-Relevant Event Determination may be
issued.
IF uncertainty remains but does not materially undermine Event
Identity or downstream interpretability, THEN Conditional or
Qualified Determination may be permitted.
IF material uncertainty prevents reliable Event interpretation,
THEN Determination shall remain deferred, uncertain, or
unresolved.
IF upstream governance outputs materially conflict, THEN the
conflict shall remain visible and the authoritative upstream
layer shall be invoked where required.
IF the apparent Event is only a technical artifact and does not
satisfy Event Formation or Boundary governance, THEN
Determination shall be rejected.
IF Merge or Split has changed the governed Event structure, THEN
the resulting Event representation shall undergo appropriate
Determination rather than inheriting positive Determination
automatically.
IF an automated system proposes a determination, THEN that
proposal shall remain subject to the same TREDS conditions as a
human-generated determination.
IF a positive Determination is established, THEN the resulting
Determined Tax-Relevant Event shall proceed to TREGS for Governed
Event Record construction.
IF later materially relevant information changes the Event
structure, THEN the Determination may be reconsidered without
erasing its prior governance history.
Governance Outputs
TREDS may produce: Determination Readiness State; DeterminationCondition Set; Determination Sufficiency State; Determination
Coherence State; Determination Stability State; Determination
Decision; Positive Determination; Conditional Determination;
Deferred Determination; Rejected Determination; Determination
Uncertainty State; Determination Conflict State; Determination
Confidence State; Determination Reasoning Record; Determination
Traceability Reference; Determination Correction; Determination
Reconsideration Record; Determination Supersession Record;
Jurisdiction-Ready Evaluation Indicator; and the principal
output: Determined Tax-Relevant Event.
Critical Distinctions
Event Determination ≠ Taxability Determination.Tax-Relevant Event ≠ Legally Taxable Event.
Event Presence ≠ Determination Readiness.
Determination Completeness ≠ Total Data Capture.
Data Availability ≠ Governance Coherence.
Governance Stability ≠ Immutability.
More Data ≠ Greater Determination Quality by default.
No Decision ≠ Positive Determination.
Positive Event Determination ≠ Positive Tax Determination.
Conditional Determination ≠ Unqualified Determination.
Deferred Determination ≠ Rejected Event.
Determination Rejection ≠ Legal Non-Taxability.
Uncertainty ≠ Automatic Determination Failure.
Conflict ≠ Permission to Select the Convenient Result.
Confidence Score ≠ Determination Decision.
Determination Result Without Governance Basis ≠ Governed
Determination.
Event Recognition ≠ Event Determination.
Event Formation ≠ Event Determination.
Event Determination ≠ Event Boundary Determination.
Event Determination ≠ Event Timing Determination.
Event Determination ≠ Legal Tax Point Determination.
Event Determination ≠ Tax Jurisdiction Determination.
Event Determination ≠ Taxpayer Determination.
Governed Value Association ≠ Taxable Value.
Event Determination ≠ Tax Base Determination.
Event Determination ≠ Event Relationship Redetermination.
Related Events ≠ One Determined Event by default.
Event Group ≠ Determination Unit by default.
Merged Representation ≠ Historical Erasure.
Split Result ≠ Automatic Positive Determination.
Technical Record ≠ Determined Tax-Relevant Event.
Invoice ≠ Tax-Relevant Event by default.
Contract ≠ Tax-Relevant Event by default.
Blockchain Transaction ≠ Determined Tax-Relevant Event by
default.
Smart-Contract Execution ≠ Tax-Relevant Event Determination.
Agent Action ≠ Tax-Relevant Event by default.
Machine Operation Count ≠ Tax-Relevant Event Count.
Automated Classification ≠ Governed Event Determination.
Model Confidence ≠ Governance Determination.
System Record Count ≠ Event Count.
Cross-Border Tax-Relevant Event ≠ Tax Jurisdiction Determination.
Jurisdictional Interpretation ≠ Event Determination Authority.
Jurisdiction-Ready ≠ Jurisdiction-Determined.
Participant ≠ Taxpayer.
Value Association ≠ Tax Base.
Operational Event Time ≠ Legal Tax Period.
Governed Event Determination ≠ Legal Tax Characterization.
Governance Finality ≠ Legal Finality.
Event Determination ≠ Validation.
Determination Authority ≠ Accountability Assignment.
Enterprise Application
TREDS establishes the decision threshold between governed Eventconstruction and downstream tax infrastructure.
A canonical enterprise path is:
ERP / Commerce / Banking / Marketplace / Blockchain / AI Agent /
Machine System
→ TREGA™ Event Governance
→ Governed Event Relationship Structure
→ TREDS — Tax-Relevant Event Determination
→ Determined Tax-Relevant Event
→ TREGS — Governed Tax-Relevant Event Record
→ TRECLS — Jurisdiction-Ready Event Lifecycle
→ Country / Jurisdiction Tax Engine
→ Legal Tax Determination
This separation allows organizations to construct one governed
Event Reality layer that can be consumed by multiple tax systems
without forcing each tax engine to independently reconstruct what
happened.
Operational Value
TREDS provides a practical control point for organizationsmanaging complex economic activity.
It prevents: raw system records entering tax engines as if they
were governed events; inconsistent Event representations across
systems; unresolved Event Boundaries entering legal tax
determination; unknown participants being silently treated as
taxpayers; Value Associations being treated automatically as Tax
Base; technical blockchain operations being counted automatically
as taxable events; AI-agent actions becoming tax events merely
because they were machine-generated; and jurisdiction-specific
interpretations from rewriting the underlying Event Reality.
The result is a reusable, jurisdiction-neutral Event
Determination layer.
Canonical Boundary
TREDS owns the governance of Determination Readiness,Determination Conditions, Determination Sufficiency,
Determination Decision, Determination Uncertainty, Determination
Conflict, Determination Qualification, Determination Reasoning,
Determination Reconsideration, Determination Correction,
Determination Supersession, and the formal establishment of a
Determined Tax-Relevant Event.
TREDS does not own Event Context, Recognition, Formation,
Boundary, Timing, Location, Participation, Value lifecycle, Value
Association, Event Relationship construction, Event Record
structure, Event lifecycle continuity, identity, ownership,
provenance, accountability, liability, tax jurisdiction, taxpayer
status, legal tax point, taxable value, Tax Base, Tax Rate,
exemption, deduction, Tax Liability, reporting obligation,
collection, enforcement, or any other jurisdiction-specific legal
tax consequence.
Its governance begins when the Event Relationship structure and
materially necessary upstream TREGA™ outputs are available for
formal Determination.
Its governance ends when the event has received a sufficiently
governed Determination state for downstream Event Record
Governance under TREGS.
Canonical Handoff
TRERLS — Governed Event Relationship Structure↓
TREDS —
Determined Tax-Relevant Event
↓
TREGS — Governed Tax-Relevant
Event Record
Canonical Closing Statement
TREDS establishes the point at which a governed event becomessufficiently complete, coherent, and reconstructable to enter
taxation infrastructure without allowing event governance to
become tax law.
Its purpose is not to decide whether tax is due. Its purpose is
to ensure that when a jurisdiction asks what happened, the event
presented to that jurisdiction has already been methodologically
governed.
Tax-Relevant Event ≠ Legally Taxable Event.
Event Determination ≠ Taxability Determination.
Jurisdiction-Ready ≠ Jurisdiction-Determined.
TREGA™ governs the event. The jurisdiction governs the tax.