Trace the runtime baseline

Type: types/instruction.md

Give later analysts a source-grounded account of how the selected target performs consequential work within the frozen boundary.

Trace and challenge

Establish the consequential claimed work, shipped entry paths, one ordinary invocation end to end, material routes, load-bearing guarantees and their enforcement points, distributed-parametric components, and mechanisms admitting changes to the product, retained knowledge, capabilities or production machinery.

A guarantee covers only paths its enforcement point covers. Enumerate materially equivalent alternate paths before judging it: direct model calls, provider-native tools, host callbacks, shell access, extension code, subprocesses or remote workers, manual graph control and durable variants. Inspect the smallest warranted set of forcing cases, ordinarily two to four for a full code-grounded analysis, and state what remains unobserved. Distinguish the capability surface, current grant set and deployed isolation envelope. Leave memory revisions to the memory analyst.

Inspect permissions, approval, delegation, dynamic extension, reliability, observability, providers, packaging and performance only where they change claimed work, a control path, evidence strength or a result later analysts will rely on. This report is not a product inventory.