AI Operations · B10–B27wk 2 / 54
B21 · measurement · Orchestration & durability

Trace Attribution + MAST Frequencies

Status
planned
Weeks
3436
Permission gate
none
Depends on
B10 · B11 · B12
Page depth
outline
This is an outline, not a result.
Nothing here has been built. It states what the block is for, what it has to produce and what would make it a failure, so that the claim can be checked against the result later. Written 2026-09-01, and it will change.

Why this block exists

Scheduled here because it comes needs real multi-step traces from real traffic. Note the correction that matters: attribution needs multiple steps, not multiple agents, a single agent with eight tool calls has the same attribution problem and is easier to instrument.

What it has to produce

When a multi-step workflow fails, know which step caused it. Publish measured failure frequencies against the peer-reviewed taxonomy.

01What it has to teach me

topicstructured span design
topicnode-level failure attribution
topicMAST conformance

02Evidence this page will carry

emptyPrimary artifact
emptyMeasured result
emptyRejection record
2026-09-01Outline created from the AI Operations Roadmap (B10-B27).
B20 Durability II. Compensation and WasteB22 Scoped Identity + Capability Contracts