Dissect
Trace it to bedrock.
Method
- Freeze one question, symbol, workflow, or subsystem and repository state.
- Find every entry: API, command, route, event, job, callback, registry, generated binding,
and configuration key.
- Trace inbound callers, including dynamic dispatch, string registration, reflection, and generated
call sites.
- Trace every branch to terminal effects, including retries, fallbacks, cleanup, cancellation,
error translation, and asynchronous continuation.
- Trace data, mutation, persistence, caches, shared state, and external effects.
- Trace invalid input, partial state, concurrency, time, exhaustion, dependency failure, and
recovery.
- Inspect tests, types, schemas, configuration, documentation, generated files, and runtime wiring.
- Close every edge with
file:line evidence. Mark every gap Unknown and name missing proof.
Output
Return the report as rendered Markdown.
Question:
State:
Flow: <entry -> decisive branches -> terminal effects>
| Path:line |
Proven edge, state, effect, or boundary |
Unknown |
Evidence
For each decisive run, give the command, working directory, state identifier, numeric exit, and
the smallest untouched decisive output excerpt. A brief plain-language summary may follow only when
the report cannot orient the reader by itself.
Boundaries
Negative claims require the search command and result. Symbol search does not prove reachability.
Record exact boundary operators.
1---2name: dissect3description: Trace one unfamiliar or dangerous code path to closure. Use when its callers, flow, state, effects, failures, configuration, tests, or coupling remain unproven. Do not use as the owner of contained work or whole-area inventory.4---56# Dissect78Trace it to bedrock.910## Method11121. Freeze one question, symbol, workflow, or subsystem and repository state.132. Find every entry: API, command, route, event, job, callback, registry, generated binding,14 and configuration key.153. Trace inbound callers, including dynamic dispatch, string registration, reflection, and generated16 call sites.174. Trace every branch to terminal effects, including retries, fallbacks, cleanup, cancellation,18 error translation, and asynchronous continuation.195. Trace data, mutation, persistence, caches, shared state, and external effects.206. Trace invalid input, partial state, concurrency, time, exhaustion, dependency failure, and21 recovery.227. Inspect tests, types, schemas, configuration, documentation, generated files, and runtime wiring.238. Close every edge with `file:line` evidence. Mark every gap `Unknown` and name missing proof.2425## Output2627Return the report as rendered Markdown.2829**Question:** <one sentence>3031**State:** <stable snapshot>3233**Flow:** <entry -> decisive branches -> terminal effects>3435| Path:line | Proven edge, state, effect, or boundary | Unknown |36| --- | --- | --- |3738### Evidence3940For each decisive run, give the command, working directory, state identifier, numeric exit, and41the smallest untouched decisive output excerpt. A brief plain-language summary may follow only when42the report cannot orient the reader by itself.4344## Boundaries4546Negative claims require the search command and result. Symbol search does not prove reachability.47Record exact boundary operators.
jcosta33