agent-run-forensics

Topics in the source

• Agent Run Forensics
• Workflow
• Hard rules
• Scripts
• References and assets

Portability: 3 stdlib Python CLIs and one hook. Read-only, no network, no model calls. Secrets in transcripts are redacted in every output, with no switch to turn that off. Agents are confidently wrong about their own history. Asked "why did you change config.yaml?", an agent answers from what it remembers, and memory drops the parts that matter: the test run that failed, the file a sed -i one-liner rewrote, the edit made after the last green run. The harness recorded all of it. This skill makes the answer come from that recording. The rule: when a question is about something that already happened, read the trace before answering. Step 3 prints two lists and you keep them apart in the answer: | Label | Means | Example | |---|---|---| | recorded | The harness wrote it down when it happened | the command, its exit code, the agent's words in the same message | | inferred | Derived now by a named rule | prior-write, read-before-write, retry-after-failure, target-seen-in-output | Say "the trace shows" only for recorded edges. Name an inferred edge as inferred, with its rule. The agent's own stated reason is recorded as a claim, not as the cause. Step 4 turns each sentence of a summary i

This is an excerpt. Refer to the complete source and its current requirements.