01
The Keeper holds final authority.
No recommendation is a decision until a human ratifies it.
How it works
Four phases.
One verdict.
The chamber separates deliberation from execution. Reasoning happens in one place, with rules. Execution happens elsewhere, with you in charge. That boundary is the product.
Time to verdict
~4 min
Median for a 4-seat, 3-round session on engineering questions.
Seats per session
3—7
Pick the council per question. No fixed lineup.
01
Pose
Phase 1
Pose what you'd otherwise decide alone.
Architecture choices. Security tradeoffs. Refactors that ripple. The chamber accepts the question with whatever context fits — a diff, a doc, a spec. Project memory loads automatically.
- ▸ Provenance recorded
- ▸ Read-only sandbox
- ▸ Prior decisions injected
02
Assemble
Phase 2
Pick the seats per task.
Code review gets a different bench than policy work. Frontier CLI seats sit alongside open-weight API seats. Each seat carries a role: prosecutor, advocate, principal — the role shapes the prompt, not the model.
- ▸ Claude · GPT · Gemini · DeepSeek
- ▸ API + CLI + OpenRouter
- ▸ Per-task council assembly
03
Deliberate
Phase 3
Seats reason. Disagree. On the record.
Questions route through seats in parallel, then in counter-rounds. Models read each other's reasoning, push back, change their minds. The transcript captures all of it: timing, tokens, costs, retractions.
- ▸ Parallel + counter-rounds
- ▸ Audit-grade transcript
- ▸ Visual disagreement surfaced
04
Ratify
Phase 4
You ratify. Override. Or send it back.
The chamber delivers a draft verdict with dissent itemized. You hold final authority. The decision becomes a durable record — PDF for stakeholders, Markdown for the repo.
- ▸ Three-button Keeper action
- ▸ Exports to PDF · DOCX · MD
- ▸ Joins project memory
Operating principles
Six rules.
They do not bend.
02
Dissent is preserved verbatim.
The chamber may not synthesize disagreement into consensus.
03
Deliberation does not execute.
Seats reason. Execution requires the Keeper and the Keeper's tools.
04
The sandbox is read-only.
The chamber may inspect project files. It may not mutate them.
05
Provenance is always recorded.
Every session knows where it originated and what it touched.
06
The chamber runs locally.
Single-user by design. Transcripts do not leave your machine.