Incident Timeline Reconstruction with Claude Code: Result JSON Schema
A production playbook for incident timeline reconstruction in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: SRE and engineering leaders
The problem
SRE and engineering leaders need incident timeline reconstruction to run repeatedly against logs, deploy events, alerts, and chat exports. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Define the outer result contract once, let the incident timeline reconstruction skill own body.data, and reject terminal output that does not match the expected schema.
Tradeoffs and failure modes
Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For incident timeline reconstruction, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Result shape
{
"schema_version": "argo.result.v1",
"summary": "incident timeline reconstruction completed",
"body": { "type": "incident_timeline", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo