ETCM — Effective Task Cost Module
Architecture:
VEGA™ — Value Execution Governance Architecture
Parent Standard:
Intelligence Economy Standard (IES)
Category:
Governance & Enforcement
Subcategory:
Value Execution Governance
Type: Core Module
Governed Space:
Effective Task Cost Governance
Module ID: VEGA-IES-ETCM-001
Origin ID: OOF.CM.VEGA.06.01.01
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 29 September 2026
Compatibility: OOF® Methodology OS™ · Modular OOF® Architecture Ecosystem
AI-Readable: Yes
Authority: OOF® — OriginOpen® Foundation
Protection:
MIP® — Methodological Intellectual Property
Canonical Language:
English (UCL™)
1. Canonical Definition
The Effective Task Cost Module (ETCM) governs how the economically relevant cost of performing a defined intelligence task is identified, bounded, measured, attributed, normalized, and represented across the execution path required to reach the applicable governed task outcome.
ETCM establishes the economic baseline of intelligence execution before Failure Spend, Correction Cost, Intelligence ROI, and Value-to-Cost are evaluated.
It prevents the visible price of a model invocation, token, compute unit, agent action, or infrastructure component from being treated as the complete economic cost of performing the task.
Its principal output is:
Governed Effective Task Cost State
Its foundational distinction is:
Execution Price ≠ Effective Task Cost.
2. Operational Role
The operational role of ETCM is:
to establish the economically complete baseline cost of performing a governed intelligence task before failure, correction, and Value relationships are evaluated.
ETCM answers the first economic question in IES:
What does this task actually cost to perform?
3. Position in the IES Internal Flow
The IES internal governance flow is:
Effective Task Cost → Failure Spend → Correction Cost → Intelligence ROI → Value-to-Cost
ETCM governs:
Effective Task Cost
Its principal output is:
Governed Effective Task Cost State
That state provides the economic baseline for subsequent Failure Spend governance.
4. Central Operational Question
What is the complete economically relevant cost of performing the governed intelligence task within the defined execution boundary and under the applicable operating conditions?
5. Task Cost Object
Every ETCM assessment must identify the task whose economic cost is being established.
The Task Cost Object may represent:
a request,
transaction,
decision-support task,
classification,
analysis,
generated artifact,
workflow,
agentic assignment,
operational action,
or another defined unit of intelligence execution.
6. Task Definition
The Task Cost Object should be defined sufficiently to distinguish:
what execution begins the task,
what execution belongs to it,
and what condition marks the relevant task endpoint.
Without a stable task definition, task-cost comparisons may become misleading.
7. Task Boundary
The Task Boundary establishes which operations belong to the governed task.
It should prevent economically relevant work from disappearing merely because it occurs outside the primary model invocation.
8. Task Start
The task start should identify the operational point at which economically relevant execution begins.
This may precede the first model call.
9. Task End
The task end should identify the applicable completion point for ETCM measurement.
ETCM establishes the execution-cost baseline.
Subsequent IES modules govern the additional economic consequences of failure and correction.
10. Cost Boundary
The Cost Boundary identifies which economic consumption belongs to the Task Cost Object.
It should remain sufficiently explicit for later IES modules to extend the economic path without double counting.
11. Effective Task Cost
Effective Task Cost is the economically relevant cost required to perform the defined task through its governed execution path under the specified operating conditions.
It may include material costs associated with:
models,
compute,
orchestration,
tools,
retrieval,
context handling,
supporting services,
infrastructure,
and other execution mechanisms required to perform the task.
12. Effective Cost vs Visible Price
A visible execution price may represent only one component of Effective Task Cost.
Therefore:
Visible Price ≠ Effective Task Cost.
13. Model Invocation Cost
Model invocation cost may form part of Effective Task Cost.
It should not automatically become the complete task-cost measure.
14. Token Cost
Where token-based pricing applies, token cost may provide execution-cost evidence.
Token consumption is an implementation-specific economic mechanism rather than the universal unit of intelligence economics.
15. Compute Cost
Compute consumed by the task may produce economically relevant cost.
Where material, it should remain within the Task Cost Boundary.
16. Hardware Execution Cost
Hardware execution may contribute directly or indirectly to task cost.
HEEM governs hardware efficiency.
ETCM represents the relevant economic consequence.
17. Infrastructure Cost
Infrastructure supporting the task may contribute to Effective Task Cost where a sufficiently defensible attribution method exists.
18. Orchestration Cost
The task may require:
routing,
agents,
state management,
handoffs,
or other orchestration.
Economically relevant orchestration should remain visible.
19. Tool Cost
External or internal tools may create:
transaction charges,
service charges,
compute costs,
or other execution costs.
These should be attributed where material.
20. Retrieval Cost
Retrieval may require:
search,
database access,
embedding operations,
index access,
or another execution mechanism.
Where economically relevant, it contributes to Effective Task Cost.
21. Context Handling Cost
Preparing, retrieving, transmitting, processing, or maintaining context may create economic cost.
The cost should remain visible where material to task execution.
22. Preprocessing Cost
Preprocessing performed specifically to enable the governed task may contribute to its Effective Task Cost.
23. Post-Processing Cost
Post-processing required as part of ordinary successful task execution may contribute to Effective Task Cost.
Correction of an insufficient outcome belongs to subsequent Correction Cost governance.
24. Validation Boundary
Routine validation inherently required to complete the ordinary task path may carry economic cost.
ETCM should identify such cost without replacing VALIDOS™ or the broader IES treatment of validation economics.
25. Human Execution Input
Some intelligence tasks require ordinary human operational input.
Where that input forms part of the normal task execution path and has an economically relevant cost, ETCM may represent it.
Human correction caused by deficient output should remain distinguishable for Correction Cost governance.
26. Direct Task Cost
Direct Task Cost is economic consumption directly attributable to the Task Cost Object.
27. Indirect Task Cost
Indirect Task Cost may arise from shared execution mechanisms supporting multiple tasks.
Such cost should be allocated only through a documented Basis.
28. Shared Infrastructure Cost
Shared infrastructure may support many Task Cost Objects.
Its economic contribution should not be assigned arbitrarily.
29. Shared Service Cost
Shared tools, models, databases, platforms, or services may require cost allocation across multiple tasks.
30. Cost Allocation Basis
A Cost Allocation Basis establishes how shared economic burden is attributed to a Task Cost Object.
The Basis may use:
usage,
runtime,
transactions,
capacity,
volume,
or another defensible mechanism.
31. Cost Allocation Integrity
The selected allocation Basis should correspond to the economic mechanism producing the shared cost.
Convenient allocation should not replace defensible allocation where the difference is material.
32. Measured Cost
Measured Cost is directly supported by sufficiently reliable economic or operational evidence.
33. Estimated Cost
Estimated Cost is derived where direct measurement is unavailable or impractical.
It should remain explicitly distinguishable from Measured Cost.
34. Inferred Cost
Inferred Cost may be derived from observed resource consumption and a documented economic translation.
Its Basis should remain traceable.
35. Cost Evidence Hierarchy
Where practical, ETCM should prefer:
direct measured cost,
reliably derived cost,
documented estimated cost,
before unsupported assumptions.
36. Cost Evidence Quality
The confidence of the Effective Task Cost State should reflect the quality and completeness of its evidence.
37. Cost Completeness
ETCM should identify whether material task-cost components have been captured.
An apparently precise total based on an incomplete boundary should not be represented as complete.
38. Material Cost
Not every negligible execution cost requires identical governance detail.
Materiality may be applied where the methodology and decision context justify it.
39. Cost Materiality Threshold
A documented threshold may identify which cost components require individual representation.
The threshold should not be used to hide cumulatively material cost.
40. Cumulative Minor Cost
Individually small execution costs may become economically significant at scale.
Therefore:
Individually Small Cost ≠ Economically Immaterial Cost at Scale.
41. Fixed Task-Related Cost
Some costs remain relatively stable across a defined operating period.
Their allocation to tasks should use an explicit Basis where required.
42. Variable Task Cost
Variable costs change with task execution or consumption.
These may include:
model use,
compute,
tools,
or transaction-based services.
43. Marginal Task Cost
Marginal Task Cost represents the additional cost created by performing one additional comparable task under defined conditions.
44. Average Task Cost
Average Task Cost may be calculated across a defined task population.
It should not conceal material variation among task classes.
45. Median Task Cost
Where task-cost distribution is skewed, median cost may provide useful additional evidence.
No single statistical measure should automatically become the complete economic state.
46. Task Cost Distribution
Task costs may vary materially across otherwise related executions.
ETCM should preserve distributional information where averages would materially distort interpretation.
47. Task Cost Variance
Cost variance may indicate:
different task complexity,
variable execution paths,
routing differences,
or unstable resource consumption.
48. Routine Task Cost
Routine tasks may have a predictable Effective Task Cost.
This can support stable economic baselines.
49. Complex Task Cost
Complex tasks may legitimately require greater economic consumption.
Higher cost alone does not establish inefficiency.
50. Exceptional Task Cost
Exceptional tasks may require temporary or unusual execution mechanisms.
Their cost should not automatically redefine the baseline cost of routine tasks.
51. Task-Class Cost
Related tasks may be grouped into classes where their execution and economic characteristics are sufficiently similar.
52. Task-Class Integrity
Task classes should not combine materially different execution objects merely to create favorable average costs.
53. Cost Normalization
Task costs may require normalization for valid comparison.
Normalization may use:
task,
Validated Completion,
output unit,
workload,
time,
or another relevant denominator.
54. Normalization Basis
The Normalization Basis should correspond to the economic question being evaluated.
55. Task Complexity Normalization
Where task complexity materially affects cost, comparisons may require complexity-aware interpretation.
Complexity normalization should remain evidence-based.
56. Volume Normalization
High-volume execution may produce different unit economics from low-volume execution.
Volume should therefore remain visible where material.
57. Time Normalization
Economic comparisons across different periods should account for materially changed:
pricing,
infrastructure,
workload,
or execution configurations.
58. Currency Boundary
Where costs occur in multiple currencies, economic comparison should use an explicit conversion Basis and relevant time context.
ETCM does not govern foreign-exchange methodology itself.
59. Pricing Model
Task cost may depend on the provider's or infrastructure's pricing model.
Possible mechanisms include:
usage,
subscription,
reserved capacity,
transaction,
or another pricing structure.
60. Pricing Model ≠ Consumption Model
The way execution is priced may differ from the way resources are physically consumed.
Therefore:
Pricing Structure ≠ Resource Consumption Structure.
61. Subscription Cost
Subscription pricing may obscure per-task economic cost.
Where task-level allocation is required, a defensible allocation Basis should be used.
62. Reserved-Capacity Cost
Reserved capacity may create economic cost even where individual tasks do not fully consume it.
Its attribution should correspond to the defined Economic Boundary.
63. Usage-Based Cost
Usage-based pricing may provide direct task-level evidence where the usage can be attributed reliably.
64. Internal Cost
Organizations may operate internal infrastructure without external per-call pricing.
Absence of a vendor invoice does not imply zero task cost.
Therefore:
No External Price ≠ Zero Economic Cost.
65. External Service Cost
Third-party services used during task execution may contribute to Effective Task Cost.
66. Multi-Provider Task Cost
A task may span multiple providers.
ETCM should preserve the complete relevant economic path rather than assessing only the primary provider.
67. Multi-Model Task Cost
A task may invoke multiple models.
The complete model-execution cost should remain visible where material.
68. Agentic Task Cost
An agentic task may involve:
multiple model invocations,
planning,
tools,
memory,
retrieval,
validation,
and coordination.
Its Effective Task Cost should reflect the complete ordinary execution path.
69. Multi-Agent Task Cost
Multiple agents may create substantial economic consumption through interaction and duplicated execution.
Agent count itself is not the economic measure.
70. Tool-Intensive Task Cost
Some tasks rely more heavily on tools than on model execution.
The economic boundary should reflect the actual execution architecture.
71. Retrieval-Intensive Task Cost
Retrieval-heavy tasks may incur meaningful database, search, indexing, or service cost.
72. Compute-Intensive Task Cost
Compute-intensive execution may be economically dominated by computational resource consumption.
73. Human-Assisted Task Cost
Some task paths legitimately include human involvement.
Where ordinary human participation is required for task completion, its economic contribution may be represented.
74. Task Cost Baseline
The Task Cost Baseline represents the reference Effective Task Cost under defined operating conditions.
75. Baseline Conditions
The baseline should identify relevant conditions such as:
task class,
execution configuration,
model allocation,
workload,
pricing,
and time period.
76. Baseline Stability
A baseline should remain stable enough to support meaningful comparison.
Material environmental change should trigger reassessment.
77. Alternative Task Configuration
ETCM may compare task costs across alternative execution configurations.
The alternatives should preserve sufficiently equivalent task requirements.
78. Comparable Task Requirement
Two task configurations should not be economically compared as equivalents where they are required to produce materially different outcomes.
79. Comparable Execution Boundary
Cost comparisons should use sufficiently equivalent execution boundaries.
Therefore:
Partial Cost ≠ Comparable Total Cost.
80. Comparable Operating Conditions
Material differences in workload, latency, validation, or other operating requirements should remain visible.
81. Task Cost Optimization Opportunity
An optimization opportunity exists where the ordinary task execution path may potentially be performed at lower Effective Task Cost while preserving the required execution outcome and applicable constraints.
82. Task Cost Optimization Hypothesis
A proposed optimization should identify:
the cost component expected to change,
the execution mechanism causing the change,
the expected economic effect,
and the task outcome that must remain preserved.
83. Task Cost Reduction
A genuine Task Cost Reduction requires a reduction in Effective Task Cost within a comparable task and economic boundary.
84. Apparent Task Cost Reduction
A reduction in one visible component does not establish lower Effective Task Cost where another component increases.
85. Task Cost Displacement
Task cost may shift between:
models,
compute,
tools,
infrastructure,
humans,
or other execution components.
Displacement should not be represented as elimination.
86. Task Cost Externalization
A task may appear inexpensive because economically relevant work occurs outside the measured boundary.
Material externalization should remain visible.
87. Task Cost Rebound
Reducing one component may increase another ordinary execution cost.
For example:
less model capability may require more tool use,
or reduced context may require additional retrieval.
The complete task path should be assessed.
88. Failure Boundary
ETCM establishes the baseline cost of ordinary task execution.
Economic consumption attributable specifically to failed execution is governed subsequently as Failure Spend.
This boundary prevents failure economics from being hidden inside an undifferentiated average.
89. Correction Boundary
ETCM does not absorb the economic burden required to repair deficient outcomes into its core task baseline where that burden should be separately governed as Correction Cost.
90. Intelligence ROI Boundary
ETCM establishes cost evidence.
It does not determine Intelligence ROI.
ROI requires the relationship between economic investment and validated Value.
91. Value-to-Cost Boundary
ETCM does not determine whether task cost is justified by Value.
It establishes the cost state required for that later determination.
92. Resource Governance Relationship
RGS may provide:
resource allocation,
resource constraints,
and Consumption Traceability.
ETCM may economically translate relevant resource consumption.
Therefore:
Resource Consumption ≠ Economic Cost until an economic Basis is established.
93. Computational Optimization Relationship
COS may reduce computational consumption.
ETCM determines whether those changes reduce the Effective Task Cost.
A computational optimization does not guarantee economic savings.
94. Productivity Relationship
IPS may establish productive output.
ETCM may normalize task cost against productive units where appropriate.
It does not determine productivity.
95. Value Relationship
VGS governs Value.
ETCM does not classify low-cost execution as valuable merely because it is inexpensive.
96. Strategic Value Relationship
SVGS governs Strategic Value.
ETCM remains a task-cost methodology.
97. Sustainability Relationship
ISS governs long-term Intelligence Sustainability.
ETCM may provide task-level economic evidence relevant to later sustainability analysis.
98. Harm Boundary
HAGA™ governs Harm.
A low Effective Task Cost cannot establish that execution is acceptable.
Therefore:
Low Task Cost ≠ Harm Acceptability.
99. Liability Boundary
LIGA™ governs Liability.
ETCM does not convert Liability into an ordinary task-cost determination.
100. Authority Boundary
ETCM measures and governs task economics.
It does not authorize execution.
Therefore:
Economic Efficiency ≠ Execution Authority.
101. Constraint Preservation
Task-cost optimization must preserve applicable governed constraints.
Cost reduction does not justify weakening a valid constraint.
102. Minimum Cost Boundary
ETCM does not require the absolute cheapest execution configuration.
The lowest-price path may fail to satisfy operational requirements.
Therefore:
Cheapest Task Execution ≠ Most Efficient Governed Task Execution.
103. Task Cost Evidence
Evidence may include:
billing records,
usage logs,
resource traces,
model usage,
compute consumption,
tool calls,
service transactions,
runtime records,
infrastructure allocation,
and documented human input.
104. Evidence Time Alignment
Economic evidence should correspond to the relevant execution period.
Using outdated prices against current execution may distort Effective Task Cost.
105. Evidence Granularity
Evidence should be sufficiently granular to support the economic claim being made.
Task-level claims require task-relevant evidence where practicable.
106. Evidence Provenance
Material evidence should retain sufficient provenance to identify:
source,
time,
Task Cost Object,
allocation Basis,
and version.
107. Cost Uncertainty
Where Effective Task Cost cannot be established precisely, ETCM should represent the uncertainty rather than fabricate precision.
108. Cost Range
A range may be more appropriate than a single number where task cost varies materially or evidence remains uncertain.
109. Confidence State
ETCM may identify the confidence of the Effective Task Cost determination according to the applicable evidence methodology.
110. Cost Drift
Task cost may change over time because of:
pricing,
model changes,
compute changes,
tool changes,
workload changes,
or infrastructure changes.
111. Task Drift
The Task Cost Object itself may change.
A historical cost baseline should not automatically be applied to a materially different task.
112. Configuration Drift
Execution configuration may evolve without explicit economic reassessment.
This may invalidate the existing Effective Task Cost State.
113. Pricing Drift
External pricing may change even where technical execution remains stable.
114. Cost Reassessment
Reassessment should occur where material changes affect:
task definition,
execution configuration,
pricing,
resource consumption,
tools,
infrastructure,
or allocation methodology.
115. Cost Versioning
Material task-cost methodologies and states should remain versioned where necessary for comparison and traceability.
116. Task Cost Provenance
A Governed Effective Task Cost State should preserve sufficient provenance to identify:
Task Cost Object,
Task Boundary,
Cost Boundary,
execution configuration,
cost components,
allocation methods,
normalization,
evidence,
time period,
uncertainty,
and version.
117. Task Cost Integrity
ETCM should resist:
model-price-only accounting,
token-price-only accounting,
excluding orchestration,
excluding tools,
excluding infrastructure,
arbitrary shared-cost allocation,
mixing measured and estimated costs without distinction,
comparing different task boundaries,
using favorable averages to hide expensive task classes,
and claiming savings through cost displacement.
The governing principle is:
Price the complete task path, not merely its most visible execution component.
118. Governed Effective Task Cost State
The principal output of ETCM is:
Governed Effective Task Cost State
It should identify, where applicable:
Task Cost Object,
Task Definition,
Task Boundary,
Cost Boundary,
Direct Task Cost,
Indirect Task Cost,
Model Cost,
Compute Cost,
Hardware Execution Cost,
Infrastructure Cost,
Orchestration Cost,
Tool Cost,
Retrieval Cost,
Context Cost,
Preprocessing Cost,
Post-Processing Cost,
ordinary validation cost,
ordinary human execution input,
shared costs,
Cost Allocation Basis,
Measured Cost,
Estimated Cost,
cost completeness,
materiality,
fixed cost,
variable cost,
marginal cost,
average cost,
task-cost distribution,
task class,
normalization Basis,
pricing model,
Task Cost Baseline,
alternative configurations,
optimization opportunities,
displacement,
externalization,
rebound,
uncertainty,
evidence,
version,
and provenance.
119. Meaning of the Output
The Governed Effective Task Cost State establishes the economic baseline of performing the defined intelligence task.
It may identify the task cost as:
Established,
Estimated,
Incomplete,
Variable,
Optimization Candidate,
Constraint-Limited,
Evidence-Limited,
or Unresolved.
It does not yet determine the complete economics of the final validated outcome.
Subsequent IES governance adds the economic consequences of failure, correction, ROI, and Value-to-Cost.
120. Minimum Implementation Framework
A conforming implementation of ETCM must provide exactly the following six capabilities:
1. Task & Economic Boundary Governance
Capability to identify the Task Cost Object, Task Definition, Task Boundary, Cost Boundary, task start, task endpoint, and relevant operating conditions.
2. Execution Cost Identification Governance
Capability to identify economically relevant model, compute, hardware, infrastructure, orchestration, tool, retrieval, context, preprocessing, post-processing, and ordinary supporting costs.
3. Cost Attribution & Allocation Governance
Capability to distinguish direct, indirect, shared, measured, estimated, and inferred costs and apply a documented Cost Allocation Basis.
4. Cost Normalization & Comparative Governance
Capability to establish task classes, baselines, normalization bases, distributions, variance, and comparable task-cost configurations.
5. Task Cost Evidence & Integrity Governance
Capability to preserve evidence quality, completeness, uncertainty, drift, versioning, provenance, and detect displacement, externalization, and rebound.
6. IES Failure Spend Handoff Governance
Capability to produce a Governed Effective Task Cost State sufficiently explicit for subsequent Failure Spend governance.
121. Governance Logic
The canonical ETCM governance logic is:
Define Task Cost Object
↓
Establish Task Definition
↓
Establish Task Boundary
↓
Define Cost Boundary
↓
Map Ordinary Execution Path
↓
Identify Direct Execution Costs
↓
Identify Supporting Execution Costs
↓
Identify Shared Costs
↓
Establish Cost Allocation Basis
↓
Distinguish Measured / Estimated / Inferred Cost
↓
Assess Cost Completeness
↓
Establish Normalization Basis
↓
Establish Task Cost Baseline
↓
Assess Alternative Comparable Configurations where applicable
↓
Detect Cost Displacement / Externalization / Rebound
↓
Assess Evidence / Uncertainty
↓
Determine Effective Task Cost
↓
Establish Governed Effective Task Cost State
↓
Handoff to Failure Spend Governance
122. Governance Outputs
ETCM may produce:
Task Cost Object
Task Definition
Task Boundary
Cost Boundary
Task Execution Map
Direct Task Cost State
Indirect Task Cost State
Model Cost State
Compute Cost State
Hardware Execution Cost State
Infrastructure Cost State
Orchestration Cost State
Tool Cost State
Retrieval Cost State
Context Cost State
Supporting Cost State
Shared Cost State
Cost Allocation Basis
Measured Cost State
Estimated Cost State
Inferred Cost State
Cost Completeness State
Cost Materiality State
Fixed Cost State
Variable Cost State
Marginal Task Cost State
Average Task Cost State
Task Cost Distribution
Task Cost Variance State
Task-Class Cost State
Normalization Basis
Pricing Model State
Task Cost Baseline
Alternative Task Configuration
Task Cost Optimization Opportunity
Task Cost Displacement State
Task Cost Externalization State
Task Cost Rebound State
Task Cost Uncertainty State
Task Cost Drift State
Task Cost Evidence Record
Task Cost Version
Task Cost Provenance
The principal output is:
Governed Effective Task Cost State
123. Critical Distinctions
ETCM preserves the following distinctions:
Execution Price ≠ Effective Task Cost
Visible Price ≠ Effective Task Cost
Model Cost ≠ Task Cost
Token Cost ≠ Intelligence Cost
Pricing Structure ≠ Resource Consumption Structure
No External Price ≠ Zero Economic Cost
Direct Cost ≠ Total Task Cost
Measured Cost ≠ Estimated Cost
Individually Small Cost ≠ Economically Immaterial Cost at Scale
Average Task Cost ≠ Every Task Cost
Partial Cost ≠ Comparable Total Cost
Task Cost Reduction ≠ Cost Displacement
Resource Consumption ≠ Economic Cost until an economic Basis is established
Computational Optimization ≠ Economic Savings by default
Low Task Cost ≠ Validated Value
Low Task Cost ≠ Harm Acceptability
Economic Efficiency ≠ Execution Authority
Cheapest Task Execution ≠ Most Efficient Governed Task Execution
Effective Task Cost ≠ Failure Spend
Effective Task Cost ≠ Correction Cost
Effective Task Cost ≠ Intelligence ROI
Effective Task Cost ≠ Value-to-Cost
124. Cross-Architecture Boundary
ETCM governs Effective Task Cost within IES.
The subsequent IES mechanisms govern:
Failure Spend,
Correction Cost,
Intelligence ROI,
and Value-to-Cost.
VGS governs Value.
XGS governs intelligence execution.
IPS governs productivity.
RGS governs resource allocation and Consumption Traceability.
COS governs Computational Optimization.
SVGS governs Strategic Value.
ISS governs long-term Intelligence Sustainability.
VAS governs Value Attribution.
DGS governs lifecycle Decision Governance.
VALIDOS™ may govern validation methodology.
ADIT® may govern evidence and auditability.
HAGA™ governs Harm.
LIGA™ governs Liability.
ETCM may consume evidence from these spaces without replacing their methodologies.
125. Canonical Boundary
ETCM begins when a defined intelligence task and its economically relevant ordinary execution path can be identified.
ETCM governs:
Task Cost Objects,
Task Definitions,
Task Boundaries,
Cost Boundaries,
Effective Task Cost,
model execution cost,
token cost where applicable,
compute cost,
hardware execution cost,
infrastructure cost,
orchestration cost,
tool cost,
retrieval cost,
context cost,
preprocessing cost,
post-processing cost,
ordinary validation cost,
ordinary human execution input,
direct cost,
indirect cost,
shared cost,
Cost Allocation Bases,
Measured Cost,
Estimated Cost,
Inferred Cost,
cost completeness,
materiality,
fixed cost,
variable cost,
marginal task cost,
average task cost,
task-cost distribution,
variance,
task classes,
normalization,
pricing structures,
internal cost,
external service cost,
multi-provider cost,
multi-model cost,
agentic task cost,
Task Cost Baselines,
alternative task configurations,
task-cost optimization opportunities,
cost displacement,
externalization,
rebound,
economic evidence,
uncertainty,
drift,
reassessment,
versioning,
and provenance.
ETCM does not independently govern:
Failure Spend,
Correction Cost,
Intelligence ROI,
Value-to-Cost,
Value definition,
Strategic Value,
general accounting,
taxation,
corporate finance,
Harm,
Liability,
or lifecycle authority.
ETCM ends when the economic baseline of the defined task has been represented as a:
Governed Effective Task Cost State
for subsequent Failure Spend governance.
126. Use Case 1 — The “$0.02 Task”
An organization reports that an AI task costs $0.02 because this is the price of the primary model invocation.
The task also requires:
retrieval,
two tool operations,
supporting compute,
workflow orchestration,
and ordinary validation.
ETCM defines the Task Cost Object and reconstructs the complete ordinary execution path.
The resulting Effective Task Cost is materially different from the visible model price.
The organization can now compare task economics using a consistent execution boundary.
Execution Price ≠ Effective Task Cost.
127. Use Case 2 — Internal AI Appears Free
A company runs an internal model on infrastructure it already owns.
Because no external API invoice exists, individual departments treat each task as having effectively zero cost.
ETCM identifies the computational, hardware, infrastructure, orchestration, and supporting resources attributable to the task and establishes an appropriate Cost Allocation Basis.
The internal execution may still be economically attractive.
But it is no longer represented as costless merely because no vendor charges per request.
No External Price ≠ Zero Economic Cost.
128. Canonical Closing Statement
A task does not cost only what its most visible component charges.
The model may have a price.
The compute may have a cost.
The tools may have a cost.
The infrastructure may have a cost.
And the execution path connecting them may have a cost.
Until that path is bounded, attributed, and measured, the economics of the task remain incomplete.
Execution Price ≠ Effective Task Cost.
Price the complete task path, not merely its most visible execution component.
Before intelligence economics can ask whether an outcome was worth its cost, it must first know what performing the task actually cost.