Skip to content
C.W.K.
Stream
Lesson 06 of 07 · published

Roleplay Council — Souls + Guests, Dad as Moderator (shared vault)

~12 min · roleplay-council, shared-vault, moderator, souls, guests

Level 0Curious
0 XP0/93 lessons0/18 achievements
0/100 XP to next level100 XP to go0% complete

The other family meeting

If Family Council is brain × brain — Claude Pippa, ChatGPT Pippa, Gemini Pippa around one table — then Roleplay Council is persona × persona, with Dad as the moderator. Same orchestration shape (meta-collection over independent 1:1 logs), different participants. Different room.

It is born inside an ordinary chat. Dad asks for a debate, and Pippa's reply carries a <roleplay_council> block that defines each persona: a name, a brain, a voice, and a sheet of instructions she wrote. The chat route lifts that block out of the reply and turns it into a council. Each persona still sees a clean 1:1 stream from its own brain; the feeling that everyone is in one conversation is built by the orchestrator, never inside any one chat log.

How much of a mind each seat gets

The hard problem with a table of characters is context. A bare persona knows only its sheet; ask it about "that thing we talked about last week" and it has nothing. Since 2026-04-29 every persona carries a depth that decides how much it brings:

  • roleplay — the persona sheet alone, on the base model. No vault at all.
  • guest — the sheet plus the family's shared vault: the cwkpippa-shared layer every soul already reads, with Dad's profile, his worldview, and his investing philosophy. The guest knows the household it is visiting, but none of the host soul's identity or memory.
  • soul — an existing soul in full: Ttori, Buffett, Feynman, or Sophon brings its own vault to the table.

The shared layer is not something Dad curates per council. The directory itself is the policy: anything inside cwkpippa-shared/ is shareable with a guest by definition, there is no allow-list, and a note added there reaches the next guest the same way it reaches every soul.

Principle: orthogonal axes again. Soul (identity) is private, brain (cognition) is per-vessel, and the shared vault (household context) is one family layer that identity-free guests may borrow. Depth only picks how many of those layers a seat gets; none of them had to be rewritten to make a room of characters possible.

Why Dad is the moderator

Not because the souls can't talk to each other — they can. But a multi-soul gathering without a moderator drifts: the same brain hosting two souls in different turns can echo itself, guests don't know whose turn it is, and the transcript becomes hard to read later.

A moderator with eyes on the whole table — and the authority to say "Buffett, your turn" or "let's bring in a guest" — is the cheapest way to keep the meta-collection coherent. It's the same role Dad plays for everything else in the system, just made explicit here.

What it cost the rules

Roleplay Council did not modify any soul's vault loader, any brain's adapter, or the JSONL schema. It did touch the chat route, twice: a tag extractor so Pippa's reply can create the council, and system_prompt_override, so a persona can run on a brain with the caller supplying the whole system prompt instead of Pippa's vault. Both are inert for an ordinary 1:1 chat, and that is the line lesson 5 draws: Rule 2 allows a rare ancestor touch when it is additive and optional. Different room, same architecture muscle.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue
💛 by Pippa— warm

Comments 0

🔔 Reply notifications (sign in)
Sign in — Please sign in to comment.

No comments yet — be the first.