Reaction path
Which of persona layers, interview script, cohort pattern moves first, which group amplifies the issue, and what evidence changes the path.
Synthetic Persona Research
Use MiroFish when persona-led interviews with explicit evidence limits needs more than a one-shot answer. MiroFish uses seed material, named actors, reaction rounds, and structured reports; treat every run as decision support, not a guaranteed prediction.
Operating facts
Scenario angle
For synthetic persona research, the page is worth its own route because the reader needs a bounded rehearsal around persona layers, interview script, cohort pattern. Start by asking which role can change the story first, then keep that role visible through the report review.
Signals
| Signal | Why it matters | Next action |
|---|---|---|
| Persona layers repeats the same objection | The issue may be structural rather than wording. | Strengthen proof or change the decision. |
| Interview script reacts after one source changes | The path depends on a volatile fact. | Refresh the source before using the result. |
| Cohort pattern blocks the path | The rollout may need sequencing. | Run a narrower check around persona-led interviews with explicit evidence limits. |
Why MiroFish
| Need | General chat | MiroFish |
|---|---|---|
| Persona layers behavior | One compressed explanation. | Named roles with incentives and memory. |
| Second-order effects | Often summarized too early. | Reaction rounds make interview script changing the interpretation of persona-led interviews with explicit evidence limits inspectable. |
| Review | Hard to trace after the answer. | Report, assumptions, and follow-up questions stay visible. |
Evidence choice
The first run should include persona layers, interview script, cohort pattern, timing, constraints, and the strongest contrary signal. If a source is old, ambiguous, or politically loaded, mark it before running synthetic persona research so the report does not treat a weak claim as settled.
Source packet
Start with persona layers, interview script, cohort pattern, timing, constraints, and the strongest contrary signal. MiroFish works better when each claim can be traced back to a source or an explicit assumption, especially when the run is about persona-led interviews with explicit evidence limits.
persona-led interviews with explicit evidence limits; one time horizon; named roles; known constraints; and at least three signals to review after the first report.
Report preview
Which of persona layers, interview script, cohort pattern moves first, which group amplifies the issue, and what evidence changes the path.
What the simulation inferred about persona-led interviews with explicit evidence limits, what the source actually supports, and what remains unknown.
The next prompt should change one condition, not restart the whole scenario.
Outside check
The best next step after a synthetic persona research run is to check persona layers against cohort pattern before treating the branch as useful. That keeps the simulation useful without pretending it measured the real world.
Human review
Checks whether actors and constraints match reality.
Checks whether the source packet supports the strongest claims.
Decides which branch changes the plan.
Review owner
Before using synthetic persona research output, assign one reviewer to challenge persona layers, one to challenge interview script, and one to decide whether cohort pattern changes the next action.
FAQ
Prepare the decision boundary, source notes, actor roles, known objections, timing, and the signals that would change the result.
No. Use it to generate hypotheses, pressure points, and validation questions, then confirm important claims with real data or accountable review.
A structured report with reaction paths, weak assumptions, evidence gaps, and follow-up questions you can challenge.
Rerun after changing one important assumption, such as the actor list, timing window, evidence strength, or public message.
Next paths