core practice · system design prompt
Design exercise: Agent Observability
Runs, steps, prompts, model calls, tool calls, tokens, costs, errors, state changes, and outcome metrics. Implement designOutline() returning non-empty values for: runIdentity, stepSpans, redaction. Each value must name a concrete mechanism or decision.
The mechanism
Agent observability connects the final outcome to every decision and side effect. A run needs stable IDs, step spans, inputs, outputs, costs, errors, and redaction.
Expected evidence
A design outline with runIdentity, stepSpans, redaction plus an explicit failure mode or trade-off.
Try this drill in the practice workspace →
Hints when you need them
- Name the failure mode before selecting the mechanism.