Simulation input
Before graph construction, personas, and reports, MiroFish needs seed material. The better the seed packet, the easier it is to inspect why a scenario report says what it says.
Seed material means the documents and notes that define the world of a simulation. It can be a product brief, market memo, transcript, strategy note, news summary, policy draft, fictional world bible, research packet, or any focused source set that explains the situation.
The most common mistake is uploading too much. A smaller, cleaner seed packet often produces better graph construction, more coherent agent personas, and a report that is easier to challenge.
Use these steps to move from a broad phrase to a reviewable scenario, report, or clarification.
The question decides which parts of the seed material matter.
Delete duplicated notes, obsolete claims, private details, and unrelated background.
Identify the groups whose reactions should appear in personas and reports.
Keep dates and source labels so the report can distinguish evidence from assumption.
Draft the first MiroFish run on this page before opening a workspace.
These checkpoints keep the page tightly matched to the exact search phrase while staying useful for a real MiroFish run.
For seed material, the strongest starting point is not a long prompt. It is a small operating brief that says what changed, who is affected, what evidence is known, and what decision the reader needs to make. Keep the first run narrow enough that a reviewer can trace every major output back to the source packet.
Use the preparation note on this page as the boundary for the first packet: One primary question, a short source packet, dates, named actors, known constraints, competing interpretations, and the assumption you are most willing to test. A good packet also labels dates, separates facts from assumptions, and avoids private or stale material that would make the report difficult to trust.
The report should be treated as a working document. When it makes a claim, ask whether the claim came from the uploaded context, an inferred relationship, an agent reaction, or a gap that still needs outside verification. That habit keeps the workflow practical for teams that need a reviewable answer rather than a dramatic prediction.
Before acting on a MiroFish output, check whether the scenario stayed inside the question you asked. The most useful output for this page is: A grounded simulation setup: extracted entities, relationships, initial context, agent persona seeds, and a report path that can point back to the material. The key limit is equally important: Seed material is not automatically true. MiroFish can structure it, but humans still need to remove outdated, private, or misleading material.
Use these checkpoints to turn the first MiroFish result into a grounded next action.
The video starts with the homepage, shows seed material upload, moves through graph construction and agent setup, and ends with a professional report screen.
These images come from the notepad MiroFish image set and are used as concrete workflow references rather than decoration.
For a market-entry simulation, seed material might include the target segment, competitor positioning, buyer objections, launch timing, and pricing assumptions. It should not include every old brainstorming note unless the note changes the decision.
The value of the page is practical: define the job, prepare the right input, read the output with its limits visible, and choose a next step that can be checked outside the page.
Read a MiroFish report as a map of assumptions and reactions. Mark source-backed claims, uncertain claims, and follow-up questions separately. Then choose one change for the next run instead of accepting the first report as final.
Use the table to decide what belongs in the page, what belongs in MiroFish, and what still needs outside verification.
| Part | What it means | Why it helps | Check before acting |
|---|---|---|---|
| Brief | What decision is being tested | Keeps the run focused | One sentence is enough |
| Sources | Facts, quotes, notes, and context | Grounds graph construction | Label dates and origins |
| Actors | Customers, competitors, regulators, fans, critics, or teams | Shapes agent personas | Avoid private dossiers |
| Constraints | Budget, timing, policy, geography, or risk limits | Makes the report actionable | Mark unknowns |
These related MiroFish pages keep the workflow connected from the homepage to the current topic and back into action.
Continue the MiroFish workflow with this related guide.
Open guideContinue the MiroFish workflow with this related guide.
Open guideContinue the MiroFish workflow with this related guide.
Open guideContinue the MiroFish workflow with this related guide.
Open guideShort answers for readers who need the useful boundary before opening a MiroFish workspace.
Any focused source packet that explains the scenario MiroFish should simulate.
You can, but a concise packet is usually easier to inspect and less likely to dilute the result.
Yes, but label assumptions clearly so the report does not treat them like proven facts.