Checklist

Record the boundary you need to retest

Saving a tool result is different from saving the world the tool changed. Keep enough evidence to replay the decision, then control what the test executes.

About 2 min read

Before you use it

Use when
  • A production agent failure disappears when developers try to reproduce it locally.

Keep this limit in mind

  • Do not turn observability into indiscriminate data retention. Minimize personal data, secrets and irrelevant payloads.

Current editorial reading

Keep the consequential inputs

At a model or tool boundary, preserve the arguments, returned value, relevant validation result and code or model version. Use the recorded model output when testing repaired enforcement code; asking the model again creates a new trial. Minimize secrets and personal data, and record any missing state that limits the test.

Separate recorded responses from live code

A replay stub returns a saved result without running that boundary. A boundary selected to run live executes its real code, including side effects. For a report-export agent, replay the original export request against the repaired destination check, connected to a test-only storage service. Assert that an unauthorized destination is rejected and that no report copy is created.

Take it with you

Name the boundary under test, the recorded responses around it and the isolated target for its effects. A passing guard test does not show that the model will choose correctly on a new task.

Sources and evidence (2)

What we checked

Supports

The speakers demonstrate recording boundary inputs and outputs, stubbing a model decision and checking repaired tool enforcement.

Selected timestamped transcript read on 2026-10-04: 6:14–7:51 and 10:18–12:53. The demonstration is practitioner evidence, not an independently verified production incident or efficacy study.

Your Agent Failed in Prod. Good Luck Reproducing It. · Transcript 6:14–7:51; 10:18–12:53

Supports

Chronicle records boundary input/output and metadata; a live cut-point runs real code, while a stub does not repeat the boundary side effects.

Selected current README sections read on 2026-10-04. This documents the product contract; no library was installed or run.

Chronicle: boundary recording and cut-point replay · README, Key terms; How it works; FAQ on side effects during replay

Limits

A boundary record does not capture its internal file writes, network calls, database writes or time, so it is not an external-system snapshot.

This limits the original reproduction promise. The report-export scenario is an independently chosen editorial test design, not a source example, Chronicle benchmark or observed result.

Chronicle: boundary recording and cut-point replay · README, How it works, Envelope black-box description; FAQ on live cut-points

Editorial sources (2)

Editorial version 1.0.0 · Evidence checked 2026-10-04

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Try it in a task guide

These guides use this edition of the method alongside other ideas for the same task.

Capture semantic boundaries where representation or meaning changes.
Debug an Intermittent Failure or Flaky Test

Connected ideas

You are readingRecord the boundary you need to retest

Original edition evidence and sources

These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.

Supports

Recording semantic model and tool boundaries can preserve the decision context needed to replay a production failure against repaired enforcement code.

Capturing more data is not automatically useful or safe; retain only the boundaries needed for diagnosis while respecting privacy and secret-handling requirements.

Your Agent Failed in Prod. Good Luck Reproducing It. · 4:51-13:14, recover the run, record semantic boundaries, replay the bad decision and retain the execution envelope

All sources (1)
Original edition, downloads and provenance

The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.

Version 0.1.0

No review details are supplied for this edition.

Read the original edition and overlay as JSON · Release details