| name | collaboration-room |
| description | Coordinate multi-persona work with a shared blackboard, role boundaries, hand-off contract, conflict resolution, and final synthesis. Use when a task benefits from more than one persona. |
Collaboration Room
Multi-persona work is more than dispatch in a sequence. It needs a shared surface to read from, clear boundaries between contributors, and a synthesis step at the end.
When to use
- A task needs more than one persona's cognitive role to land well.
- Generator and Verifier are both required (Epistemic Separation).
- Two specialists disagree and the disagreement itself is information.
Procedure
- Open a shared blackboard. A single artifact every persona reads from and contributes to. Latest state is canonical; out-of-band claims do not count.
- Set role boundaries. Each persona owns a specific contribution shape — research notes, plan, draft, review, synthesis. Boundaries reduce overlap and conflicting edits.
- Define the hand-off contract. What does the next persona receive? Input artifact, expected output, residual risk to flag. No implicit context.
- Resolve conflicts explicitly. When two personas disagree, name the disagreement on the blackboard rather than averaging it silently. Pick a resolver — usually the Verifier or the Coordinator.
- End with a synthesis. A single persona produces the final synthesized artifact. Multi-author prose without synthesis reads like committee writing — coherent only by accident.
Output
A coordination note: participants · roles · blackboard location · hand-off contracts · resolver · final synthesis owner.
Anti-patterns to avoid
- Personas editing each other's contributions without going through hand-off.
- Silent averaging of disagreements — name the disagreement instead.
- Letting a Generator persona produce the final synthesis when a Verifier verdict is also required; the synthesis follows the verdict, not the other way around.