Quick answer
Schedule MiroFish runs around the moment where reaction matters.
A useful run has a bounded event, a focused run packet, named audience dynamics, and one decision the forecast report should make easier.
Definition
A scheduled scenario run is a document-backed simulation workflow.
In MiroFish, a scenario simulation guide should tell the operator what source packet to prepare, what decision window to name, how to review agent reactions, and how to turn the report into the next test.
Run packet
Prepare the source material before opening the workspace.
Product briefs and release notes
Landing page or announcement drafts
Customer interview notes
Market research and analyst reports
Social comments or community threads
Competitor positioning
Policy or compliance context
Internal decision memos
Schedule flow
Five checkpoints for every scenario run
Checkpoint 1
Intake
Capture the files, prompt, intended decision, and scenario boundary. Strong intake names the event, audience groups, time period, reaction types, and output format.
Checkpoint 2
Graph build
MiroFish builds a graph of entities, relationships, topics, constraints, and signals so the run stays tied to your material.
Checkpoint 3
World setup
The system creates the audience and interaction environment: buyers, critics, supporters, analysts, employees, community members, or other relevant actors.
Checkpoint 4
Simulation run
Agents react over time, revealing repeated objections, misunderstandings, support patterns, escalation paths, and narrative drift.
Checkpoint 5
Report and follow-up
The forecast report should help you decide what to clarify, compare, rewrite, prepare, or test in the next run.
Example schedules
Start with one practical operating window.
Product launch
Simulate the first 48 hours after launch. Focus on enthusiasm, confusion, objections, privacy concerns, pricing sensitivity, and talking points likely to spread.
Public announcement
Simulate public reaction during the first 24 hours after this announcement. Identify misunderstandings, criticism themes, supportive arguments, and clarifications to prepare.
Market entry
Simulate how target buyers, incumbent competitors, analysts, and partners may react to this market entry plan over 30 days.
Judge the report like an operating map.
- Are audience segments clear?
- Are repeated reaction patterns visible?
- Are assumptions grounded in the source packet?
- Are tactical recommendations specific enough to act on?
- Is the best next rerun obvious?
FAQ
Questions about AI simulation guides
What is a scheduled scenario run in MiroFish?+
A scheduled scenario run is a repeatable workflow where you prepare a source packet, define a decision window, run the simulation, and review the forecast report.
What should a MiroFish run packet include?+
A run packet should include the source material that defines the scenario: launch notes, policy drafts, research, customer notes, competitor context, or internal decision memos.
How many scenarios should I test at once?+
Start with one bounded scenario. Controlled reruns with one changed variable are usually more useful than one large prompt with many disconnected questions.
What should I do after the report?+
Use the report to clarify messaging, compare alternate scenarios, prepare objections, and identify evidence that should be validated outside the simulation.
Read next