Meta-Collection over Independent 1:1 Logs

What council actually stores

A council is a JSON file in /councils/. It stores: list of brain identities, list of rounds (each round = a transcript snapshot + which brain spoke), Dad's optional comments, the picked round (if finalized).

What it doesn't store

The actual chat logs. Those live in their own JSONL files under /sessions/, one per (brain, conversation_id). Council just references them.

Transcript assembly

When Dad asks Council to run another round, the council orchestrator builds a transcript prefix from the existing rounds and prepends it to the new turn's user message — so the brain sees 'Here's what's been said so far. Now respond.' That's the only mechanism. Each brain processes a 1:1 turn that happens to include a long prefix.

Code

Council JSON shape (simplified)·json

{
  "id": "council-2026-04-30-01",
  "seq": 142,
  "title": "Q3 architecture review",
  "brains": ["claude", "codex", "gemini"],
  "rounds": [
    {
      "id": "round-1",
      "prompt": "What's the biggest risk in Phase 4?",
      "replies": {
        "claude": {"conversation_id": "...", "message_id": "..."},
        "codex": {"conversation_id": "...", "message_id": "..."},
        "gemini": {"conversation_id": "...", "message_id": "..."}
      },
      "picked": false
    }
  ],
  "finalized": false
}

What council actually stores

What it doesn't store

Transcript assembly

Code

Progress