# Capture semantic boundaries, not only raw logs

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Capture semantic boundaries, not only raw logs

ID: MHC-D-RESEARCH-1159 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/capture-semantic-boundaries-not-only-raw-logs

A log can be complete and still omit the boundary where meaning changed.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

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

### Avoid when

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

### Explanation

Record the inputs and outputs at the model and tool boundaries that matter to the task: model request and response identifiers, parsed arguments, tool results, policy decisions and the state carried into the next step. This creates an execution envelope that can replay the bad decision against repaired code.

### Checklist

- Capture the model decision that selected the action.
- Capture the exact parsed tool arguments and returned result.
- Record policy or validation decisions around the call.
- Keep enough state to replay the boundary without storing unrelated sensitive data.

### Example

A trading assistant interpreted dollars as shares. The useful trace preserves the model's action, parsed amount, tool contract and validation result at the order boundary.

### Check

A developer can replay the consequential boundary without inventing missing inputs or re-prompting the model for a similar decision.

### Limits

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

### Evidence and sources

- supports: Recording semantic model and tool boundaries can preserve the decision context needed to replay a production failure against repaired enforcement code. — RS-F0FB27D3E1B6C4A1. Capturing more data is not automatically useful or safe; retain only the boundaries needed for diagnosis while respecting privacy and secret-handling requirements. (4:51-13:14, recover the run, record semantic boundaries, replay the bad decision and retain the execution envelope)
- RS-F0FB27D3E1B6C4A1: Your Agent Failed in Prod. Good Luck Reproducing It. — https://ai.engineer/talks/Lc8zRh9muoY-your-agent-failed-in-prod-good-luck

### Vedokrok editorial review

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.

#### 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.

**Editorial takeaway:** 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.

#### Editorial evidence

- supports: The speakers demonstrate recording boundary inputs and outputs, stubbing a model decision and checking repaired tool enforcement. — RS-F0FB27D3E1B6C4A1. 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. (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. — chronicle-readme. Selected current README sections read on 2026-10-04. This documents the product contract; no library was installed or run. (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. — chronicle-readme. 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. (README, How it works, Envelope black-box description; FAQ on live cut-points)
- RS-F0FB27D3E1B6C4A1: Your Agent Failed in Prod. Good Luck Reproducing It. — https://ai.engineer/talks/Lc8zRh9muoY-your-agent-failed-in-prod-good-luck
- chronicle-readme: Chronicle: boundary recording and cut-point replay — https://github.com/theagentplane/chronicle

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/track-tool-errors-tool-calls-runtime-and-tokens-as-agent-diagnostics
