Cost Attribution Layer

The architectural component that traces the operational cost of every agentic step, task class, and job-to-be-done against the business’s v0 baseline — enabling the Steward to evaluate the economic impact of each architectural optimisation decision with precision, rather than measuring compounding effect by impression or total spend.

Total token spend is not a governance instrument. A Steward who knows that the business spent $12,000 on tokens last month knows nothing about whether that spend was optimally allocated, whether specific task classes are generating disproportionate cost, or whether the architectural changes made in month three reduced the per-unit cost or merely shifted it to a different line item. Cost visibility at the aggregate level is accounting. Cost visibility at the step level is architecture.

The Cost Attribution Layer connects every model call, every tool invocation, and every data retrieval to the task class it serves, the step in the Revenue Loop it occupies, and the job-to-be-done it contributes to. This structure serves two distinct functions. First, it makes Architecture Cost Drift visible: the cumulative deviation between the current system’s cost profile and the v0 baseline, measured continuously as the Steward makes architectural refinements. If a month-four optimisation reduced the Escalation Rate by 30% but increased per-execution cost by 15%, the Cost Attribution Layer shows both effects at the step level. Second, it enables intelligent routing: when the Cost Attribution Layer confirms that a specific task class consistently consumes disproportionate compute relative to its contribution to output quality, that is the data signal that triggers an Intelligence Arbitrage routing review for that class.

The connection to the Operational Ledger is structural: cost records are a layer of the Ledger, not a separate system. Every execution cycle that the Ledger records includes the cost attribution for that cycle, indexed against the step and task class that generated it. The Ledger compounds operational intelligence. The Cost Attribution Layer compounds economic intelligence. Both must be designed from the same underlying trace data or they diverge and lose their comparability over time.

**Sub-concept: Architecture Cost Drift** — The cumulative economic delta between the current architecture’s cost profile and the v0 baseline, measured continuously by the Cost Attribution Layer to validate whether Steward optimisation decisions are compounding correctly or producing cost drift that offsets operational gains.

First used: May 2026