Explain one slow request from trace data
one move: instrument before debugging
Open the code pane immediately, then use the Spec tab, optional design question, tests, and artifact when you want them.
Finish each move before carrying the artifact forward.
Production behavior becomes diagnosable when each request emits structured spans, errors, tokens, latency, and cost signals.
Deliverable: State the invariant in one sentence.Aggregate span records into request count, error count, p95 latency, token usage, and total cost without hiding failed spans.
Deliverable: Type the smallest deterministic implementation.Empty traces, one slow request, and failed spans have explicit outputs; p95 is deterministic.
Deliverable: Record a normal case and a boundary case.Add a queue span, a model span, and a tool span; locate which component moved p95.
Deliverable: Name the failure signal and the guard you would add.An inspectable request trace and an SLO snapshot.
Deliverable: Save the contract, evidence, and handoff note.Empty traces, one slow request, and failed spans have explicit outputs; p95 is deterministic.
Add a queue span, a model span, and a tool span; locate which component moved p95.
An inspectable request trace and an SLO snapshot.
Deriva-authored extension beyond the supplied PDF. The five moves are Deriva’s implementation contract for this project.