Domain owner
Checks whether actors and constraints match reality.
Policy Impact Simulation
Policy Impact Simulation for evidence-led scenario rehearsal
Use MiroFish when policy effects across affected groups depends on policy option, affected groups, and tradeoffs reacting differently. Bring seed material for policy option, run reaction rounds around affected groups, and review tradeoffs changes as decision support, not a guaranteed prediction.
Operating facts
Keep policy option and affected groups limits visible before opening the console.
Policy option workflowSeed material and graph context let policy option and affected groups react inside a bounded MiroFish world.
Affected groups boundaryTreat affected groups reactions as decision support, not as a guaranteed prediction.
Useful inputThe first useful run needs policy option, affected groups, tradeoffs, timing, constraints, and the strongest contrary signal.
Scenario readiness check
Check whether the policy option brief is ready for a MiroFish run around policy effects across affected groups.
Use this quick tool before opening the console for policy option and affected groups. A strong first run names tradeoffs, the pressure point, a review owner, and one outside validation move.
Preparation detail
Give policy option enough context to produce a useful disagreement.
For policy effects across affected groups, begin with the moment when policy option can change the path. Add what affected groups already knows, what tradeoffs might ignore, and which constraint would make the decision reversible. A narrow policy option brief helps the report produce disagreement you can inspect instead of a smooth affected groups story that feels confident but cannot guide the next action.
Use concrete material from policy option, affected groups, tradeoffs, timing, constraints, and the strongest contrary signal and label the parts that are still weak. If the policy option note is old, the affected groups move is speculative, the tradeoffs source is ambiguous, or the signal came from a small sample, say that directly. MiroFish can then keep strong evidence separate from convenient assumptions while it builds reaction rounds.
Before acting, compare the report with affected groups changing the interpretation of policy effects across affected groups and then check policy option against tradeoffs before treating the branch as useful. That outside check for tradeoffs should be small enough to complete quickly: one customer call, one support search, one analytics pull, one expert read, or one revised prompt with a single changed condition. The point of the first run is to improve judgment, not to outsource it.
MiroFish uses seed material from the brief to keep policy option, affected groups, and tradeoffs anchored to the same facts. For policy effects across affected groups, that means the report should show which claim each actor accepted, which claim each actor resisted, and which missing detail changed the branch. If the report cannot name those links, improve the input before spending attention on a larger run.
Notebook prompt: ask policy option what would make policy effects across affected groups feel urgent, ask affected groups what proof would be dismissed, and ask tradeoffs which missing fact would reverse the branch. Then record the exact policy option sentence in the report that changed your confidence. If no sentence changes confidence, the next move is not a bigger run; it is a better source packet, a narrower actor list, or a validation check outside the tool.
Scenario angle
The useful question is where policy effects across affected groups breaks.
This page is worth its own route because the reader needs a bounded rehearsal around policy option, affected groups, tradeoffs. Start by asking which role can change the story first, then keep that role visible through the report review.
Human review
Give reviewers a concrete job.
Evidence owner
Checks whether the source packet supports the strongest claims.
Decision owner
Decides which branch changes the plan.
Validation plan
Turn output into real checks.
Interview
Ask policy option whether the strongest assumption is real.
Evidence pull
Refresh facts that may have changed since the source packet was written.
Rerun
Change one assumption around policy effects across affected groups and compare the new branch map with the original.
Evidence choice
Pick source material that can be challenged later.
The first run should include policy option, affected groups, tradeoffs, timing, constraints, and the strongest contrary signal. If a source is old, ambiguous, or politically loaded, mark it before opening the console so the report does not treat a weak claim as settled.
Boundary
This is rehearsal, not measurement.
The MiroFish run can expose plausible reactions and research questions, but it cannot replace recruited participants, live market behavior, expert review, legal review, medical advice, financial advice, or accountable judgment.
Workflow
Move from brief to review in four deliberate steps.
Frame policyFrame policy effects across affected groups with one decision boundary.
Build anBuild an actor graph for Policy option, Affected groups, Tradeoffs.
Run reactionRun reaction rounds and watch for affected groups changing the interpretation of policy effects across affected groups.
Question theQuestion the report and check policy option against tradeoffs before treating the branch as useful.
Outside check
Leave with one verification move, not a pile of guesses.
The best next step after the first report is to check policy option against tradeoffs before treating the branch as useful. That keeps the simulation useful without pretending it measured the real world.
Branches
Test three paths instead of asking for one verdict.
Base pathpolicy effects across affected groups follows the expected story.
Friction pathaffected groups reframes the decision and slows adoption.
Surprise pathaffected groups changing the interpretation of policy effects across affected groups becomes the dominant interpretation.
Review owner
Name the person who can say the branch is weak.
Before using the output, assign one reviewer to challenge policy option, one to challenge affected groups, and one to decide whether tradeoffs changes the next action.
FAQ
Policy Impact Simulation FAQ
What should I prepare for policy impact simulation?
Prepare the decision boundary, source notes, actor roles, known objections, timing, and the signals that would change the result.
Can policy impact simulation replace real evidence?
No. Use it to generate hypotheses, pressure points, and validation questions, then confirm important claims with real data or accountable review.
What does MiroFish return?
A structured report with reaction paths, weak assumptions, evidence gaps, and follow-up questions you can challenge.
When should I rerun it?
Rerun after changing one important assumption, such as the actor list, timing window, evidence strength, or public message.
Next paths