all-scenarios-storm

# All scenarios storm ## Contract | Field | Bound contract | |---|---| | Trigger | User wants to enumerate plausible designs, configurations, scenarios, and implementation paths and diagram the finished field before choosing. | | Authority | Chat-only: no local artifacts are written. No remote, VCS-history, credential, paid, published, or deployed mutation. | | Side effect | An exhaustive field of designs/configs/scenarios/paths and a diagram. | | Done | An exhaustive field is enumerated and diagrammed before a choice is made. | ## Inputs - Decision subject: the design, system, or problem whose solution space is being stormed. - Enumeration dimensions: designs, configurations, scenarios, implementation paths, or a subset. - **Bounds** (optional): constraints, known invariants, or excluded paths. ## Procedure 1. State the decision subject and the dimensions the user named. If the user did not name any, default to all four: designs, configurations, scenarios, and implementation paths. Done when: the subject and dimensions are named. 2. Bound the field. List the constraints, invariants, and explicitly excluded paths the user supplied. Mark anything unbounded as an assumption, not a fact. Done when: constraints and excluded paths are listed; unbounded items are marked as assumptions. 3. Exhaustively enumerate every plausible option in each dimension. For every option, record a one-line description and the key tradeoff or risk that distinguishes it from neighboring options. ...