Skip to content

Build AI methods with your coding agent, then run them anywhere: as an MCP for chatbots, as a webapp for people, or via API for your software.

docs(wip): mark durable-usage raw-records note superseded by the wire contract

Louis Choquele421ccd34874
diff --git a/wip/durable-results-tokens-usage-exposure.md b/wip/durable-results-tokens-usage-exposure.md
index d719be5ed..c5bbad2b2 100644
--- a/wip/durable-results-tokens-usage-exposure.md
+++ b/wip/durable-results-tokens-usage-exposure.md
@@ -4,6 +4,8 @@
exploration, 2026-07-18). Live-verified against hosted api-dev. Full findings:
`~/repos/Fenix/project/designs/a6-cost-measurement.md`.
+> **Superseded on the wire shape (2026-07-19):** the "keep it raw records, not a computed $ total" note below was deliberately reversed by the tokens-usage wire contract (workspace `wip/usage/tokens-usage-wire-contract.md`, FINAL). The wire record ships a server-computed `cost` and MUST NOT expose `unit_costs` — rates are the runtime's pricing data, not client contract, and `cost: null` (vs `0.0`) resolves the "zero-cost record" caveat flagged below. Consumers that want a run total sum the per-record `cost` values; the deterministic multiply-and-sum now happens server-side, pinned by parity tests against `CostRegistry`. The artifact/route plumbing described in this doc remains accurate.
+
## The gap
The engine assembles per-call usage onto `PipeOutput.tokens_usages` (token counts by category +