roundtablelisted

# Round Table **IMPORTANT: Start your response by telling the user:** > **Round table** — Convening the fixed roster (Claude, Antigravity, > Codex). You chair; I moderate. Up to 3 rounds. ## What It Does A moderated deliberation (Phase 1 of `docs/specs/agent-round-table`): the user poses a question, each roster member answers headlessly and independently, the moderator (this session) posts every message to the Redis board, synthesizes, and presents the result. Only the chair — the user — promotes anything into a tracked artifact. Invariants (ratified — do not improvise around them): - **R1** Members are text-in/text-out. They never touch Redis, files, or shell. All board I/O goes through the moderator via the `Board` client (`attune.roundtable`). - **R3** Board state lives only under `attune:roundtable:*` (TTL 7 days). Never write `attune:memory:*`. - **R4** Nothing reaches a tracked file without explicit per-item chair approval. No auto-promotion, ever. - **D3** Hard ceiling: 3 rounds per question. Halt early when positions converge or a round adds no information. ## Shared command workspace (preferred) When the generic command-workspace tools are available, use them as the chair-facing surface for the lifecycle below. They do not replace the board or grant seats new authority: 1. Open adapter `roundtable` with `command_workspace_open`, passing the question, thread slug, expected rounds, and maximum seat invocations. 2. Present its widget, or its return