Follow the Running Code

Replace folder-tree summaries with a replayable chain of evidence from one real entry point to one observable effect.

What the resource contains

8-stage execution-trace progression

8 production-ready Claude Code prompts

Entry, boundary, state, and contradiction ledgers

Failure trace and independent replay gate

Selected preview

Choose the behavior

Anchor the investigation to one example input, one reachable entry, and one observable effect before looking at the repository shape.

One behavior and environment

Explicit start and end signals

Read-only permission boundary

Stop when the charter is ambiguous

Walk one happy path

Follow the example value one caller-to-callee edge at a time. Every arrow must name how it was proven.

At every hop record: caller symbol, callee symbol, input shape, transformation, output or side effect, and edge evidence. Stop at the first unsupported edge rather than jumping to a plausible downstream component.

Make it replayable

The last stage gives a fresh reviewer everything needed to reproduce the trace without hidden chat context.

Ordered file-and-symbol citations

Boundary and state ledgers

Contradictions preserved as open

GO only when change-critical edges are verified

Hunt the contradiction

A second evidence source must challenge every critical edge before the trace can be trusted.

Search for evidence that the edge is disabled, bypassed, shadowed, version-skewed, test-only, environment-specific, or called with a different value shape. Preserve unresolved conflicts instead of selecting the convenient source.