Workflow mapping

Turn the supplied context into concrete scenario/result tables the user can inspect to decide whether the workflow behaves as intended. Use the domain's own names for actors, objects, events, and states.

1. Establish the boundaries

Use the conversation and relevant code, tests, and specifications to identify entry points, actors, state, relationships, triggers, completion conditions, and observable side effects. Follow the logic through the components that determine the outcome, including downstream updates and failure handling.

Distinguish intended behavior from implemented behavior: user decisions and specifications describe intent; code describes implementation; tests show which examples have assertions. When these disagree, preserve the disagreement.

Proceed once the workflow's boundaries and sources are identified. If missing context prevents a meaningful map, ask a focused question; otherwise carry the unknowns into the map.

2. Enumerate the paths

Build scenarios from reachable states and events. Each scenario names the starting conditions and the action or event sequence needed to distinguish its result. Follow the journey until completion, failure, cancellation, or a waiting state; for waiting states, identify what resumes progress.

Inspect these dimensions where the context supports them: