ck-howlisted

# CK How Explore the implementation to answer how something works. Produce enough explanation for the reader to follow the behavior and work in that area, without turning the answer into annotated source code. Investigation is read-only unless the task separately authorizes changes or experiments. ## Assess the question Identify the target and the user's purpose from the request and available context. If the scope is ambiguous but exploration can resolve it, state the interpretation briefly and proceed. - **Narrow question:** trace and explain directly. A single utility, pipeline stage, or ownership question usually needs no delegation. - **Cross-cutting question:** divide the work into distinct angles such as entry points, data transformations, persistence, scheduling, or component boundaries. Use independent explorers when supported and useful; otherwise trace these angles yourself. Inherit the current model and configuration unless the user requests otherwise. Match effort to the question. A full architecture inventory is unnecessary when one call path answers it. ## Trace the implementation For delegated exploration, use [references/explorer-prompt.md](references/explorer-prompt.md), giving each explorer the original question, its angle, and the relevant workspace. The same guide applies to direct investigation. Find the entry point, follow the execution and data flow, and identify the abstractions and boundaries that explain the behavior. Read implementations rat