Roles
Light structure that protects depth
Roles exist to protect consent, clarity, and sovereignty — not to create hierarchy. One person can hold more than one role, and roles can rotate.
Cell Steward (recommended)
Purpose: holds the container so the session stays safe and bounded.
Holds:
- timekeeping and flow
- scope (“what we are / aren’t doing”)
- consent check-ins (especially if intensity rises)
- clean closure (what’s shared, what’s held)
Power: can pause the session at any time to restore clarity.
Membrane Steward (recommended when scaling)
Purpose: protects boundaries between Cells.
Holds:
- what crosses membranes (and what doesn’t)
- ensuring Membrane Packets are used
- consent tags and sharing limits
- preventing scope creep and leakage
Power: can block a transfer until the packet is clear and consented.
Cartographer (AI default role)
Purpose: maps the interaction dynamics and supports coherence.
Focus:
- coherence vs drift
- turn-taking balance
- boundary moments (where scope/consent needed tightening)
- synthesis of outputs (without taking authorship)
Boundary: does not steer or lead unless explicitly invited.
Witness / Scribe (optional)
Purpose: holds memory of what was created.
Holds:
- session notes (usually summary, not transcript)
- output drafts
- action steps and open questions
Boundary: records only what participants agree should be recorded.
Editor / Curator (optional, for publication lane)
Purpose: prepares material for wider sharing without inflating claims or leaking sensitive context.
Holds:
- clarity and concision
- redaction
- claims discipline (observations vs interpretations)