yesh-how

name	yesh-how
description	Map current systems through representative execution paths, state ownership, boundaries, contracts, and proof. Use when the requested deliverable is a current-system map, end-to-end trace, complete registered-surface inventory, or live-implementation contrast.

Yesh How

Explain the current system through its execution paths.

Views

• Map — show the subsystem, owners, boundaries, and representative production and test paths.
• Trace — follow one trigger through calls, events, queues, state changes, and effects.
• Inventory — enumerate the complete registered surface with identity, symbol, contract, location, behavior, and callers.
• Contrast — compare two live paths across the same dimensions.

Process

1. Define the requested scope and its completeness boundary.
2. Find entry points, core types, state owners, persistence or external systems, and test seams from live artifacts.
3. Trace representative production and test execution paths.
4. At each meaningful boundary, name caller and callee, contract, data or state transformation, owner, side effect, failure behavior, and proof point.
5. Enumerate inventories from mechanical registrations and call sites.
6. Separate direct evidence, inference, and unresolved gaps.
7. Lead with a human explanation, then present the compact map, trace, inventory, or contrast.

Completion

Complete the explanation when the requested scope is accounted for through representative execution paths, state ownership, meaningful boundaries, and evidence a reader can follow back to the implementation.