Observability Semantics, Cost Attribution, and Forensics
Make runs comparable and incidents reconstructable across agents, tools, services, queues, environments, CI, deployment, and outcomes.
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Reconstruct and defend this chapter’s architecture.
Reconstruct the architecture, name each boundary, and defend the tradeoffs.
Open the source exercise
Trace one WorkOrder through queue, worker, model, three tools, CI, artifact registry, deployment, and product metric. Add a human pause, provider retry, secret-bearing tool response, and delayed incident. Design attributes, sampling, retention, and evidence conversion.
4. Tradeoffs and alternatives
Full-fidelity tracing improves reconstruction and increases cost and sensitive-data exposure. Tail sampling and risk-based retention preserve high-value traces. Standard conventions improve comparability and may lag new provider features; retain vendor details under namespaced attributes without breaking the common core.
5. Current Mission Control Implementation
The existing observability chapter covers correlation, events, metrics, logs, token usage, cost, runtime health, and evidence boundaries. The curriculum does not yet define a complete semantic schema, cardinality and sampling policy, lifecycle-wide trace linkage, cached and reasoning token attribution, or forensic-bundle contract.
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence