The simulator works backwards from your decision, not from a fixed playbook. Pick a decision type below, define the goal, declare your constraints, and the engine will activate the relevant dimensions from the 515-library and generate scenario alternatives. Every output downstream — scenarios, action plan, tracking — is tailored to what you input here.
First-time users may prefer a guided flow.
Decision type
Decision identity
01
Human label. Appears in headers and exports.
The goal — read this back to yourself
02
Pick a decision type to begin.
Baseline — the starting reality
03
Every projection is calibrated against where you are today. Inaccurate baseline → inaccurate everything downstream.
Constraints — what cannot change
04
Activate the constraints that bind this decision. The simulator excludes scenarios and actions that would violate them. Be honest here — over-constraining produces a thin scenario set; under-constraining produces unrealistic recommendations.
Data tier — what evidence will the engine have?
05
Per Document 02's three-tier architecture. Tier choice determines what dimensions are accessible — and therefore how tight the simulation's intervals can credibly be. The honest answer here matters more than the optimistic one. If you mark T3 but only have T1 data, the engine produces over-confident output and the boardroom finds out later.
Dimensions — what do you actually know?
06
These dimensions are the analytical inputs your decision-type cares about. Mark each as Available (you have the data), Estimable (you can guess), or Unknown (no data, no estimate). The engine adjusts every interval based on this. A plan built on dimensions you've all marked unknown will show wide intervals — that's the engine being honest, not malfunctioning.