Synthetic Persona Research

Operating facts

Keep persona layers and interview script limits visible before opening the console.

Persona layers workflowSeed material and graph context let persona layers and interview script react inside a bounded MiroFish world.

Interview script boundaryTreat interview script reactions as decision support, not as a guaranteed prediction.

Useful inputThe first useful run needs persona layers, interview script, cohort pattern, timing, constraints, and the strongest contrary signal.

Scenario readiness check

Check whether the persona layers brief is ready for a MiroFish run around persona-led interviews with explicit evidence limits.

Use this quick tool before opening the console for persona layers and interview script. A strong first run names cohort pattern, the pressure point, a review owner, and one outside validation move.

Preparation detail

Give persona layers enough context to produce a useful disagreement.

For persona-led interviews with explicit evidence limits, begin with the moment when persona layers can change the path. Add what interview script already knows, what cohort pattern might ignore, and which constraint would make the decision reversible. A narrow persona layers brief helps the report produce disagreement you can inspect instead of a smooth interview script story that feels confident but cannot guide the next action.

Use concrete material from persona layers, interview script, cohort pattern, timing, constraints, and the strongest contrary signal and label the parts that are still weak. If the persona layers note is old, the interview script move is speculative, the cohort pattern 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 interview script changing the interpretation of persona-led interviews with explicit evidence limits and then check persona layers against cohort pattern before treating the branch as useful. That outside check for cohort pattern 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 persona layers, interview script, and cohort pattern anchored to the same facts. For persona-led interviews with explicit evidence limits, 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 persona layers what would make persona-led interviews with explicit evidence limits feel urgent, ask interview script what proof would be dismissed, and ask cohort pattern which missing fact would reverse the branch. Then record the exact persona layers 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.

Synthetic Persona Research brief naming

Sharpen the synthetic persona research brief before the run starts.

The synthetic persona research run should stay tied to one decision boundary, one source packet, and one validation owner. Use the phrase in the working title so persona layers, interview script, and cohort pattern all review the same question instead of drifting into a general brainstorm.

synthetic persona research: baselineUse this label for the branch where the expected story still holds around persona-led interviews with explicit evidence limits.

synthetic persona research: resistanceUse this label when signals from interview script change the interpretation or expose a weak assumption.

synthetic persona research: validationUse this label for the outside check that tests whether cohort pattern would change the next move.

Keep synthetic persona research notes separate from generic MiroFish notes in the report archive. That makes the next synthetic persona research rerun easier to compare: same actors, same evidence boundary, one changed condition, and a clearer reason to continue or stop.

Scenario angle

The useful question is where persona-led interviews with explicit evidence limits breaks.

This 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

Decide what would change the next run.

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

Use a structured world instead of a loose answer.

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

Pick source material that can be challenged later.

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 opening the console so the report does not treat a weak claim as settled.

Source packet

Bring the material that makes the run inspectable.

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.

Good packet

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

A useful report makes pressure points visible.

Reaction path

Which of persona layers, interview script, cohort pattern moves first, which group amplifies the issue, and what evidence changes the path.

Assumption register

What the simulation inferred about persona-led interviews with explicit evidence limits, what the source actually supports, and what remains unknown.

Follow-up question

The next prompt should change one condition, not restart the whole scenario.

Outside check

Leave with one verification move, not a pile of guesses.

The best next step after the first report 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

Give reviewers a concrete job.

Domain owner

Checks whether actors and constraints match reality.

Evidence owner

Checks whether the source packet supports the strongest claims.

Decision owner

Decides which branch changes the plan.

Review owner

Name the person who can say the branch is weak.

Before using the 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