Repository navigation
v0.1.0 — a council that has to agree before you approve
Open Council runs three AI CLIs as a council with separated powers, and hands you exactly one decision.
- Lead PM (Gemini, via the Antigravity CLI) researches the repository and writes a Product Brief + PRD.
- Chief Engineer (Claude Code) verifies every claim against the actual code, objects with
file:lineevidence, and refuses to ratify what it cannot test. - Chief Architect (Grok) arbitrates deadlocks, rules on anything the standards leave undefined, and audits the spec against a 12-point industry-standards checklist.
- You approve the finished PRD. That is the only human step, and nothing is written before it.
A document only reaches you when all three seats have signed off the byte-identical file: the Engineer with zero objections, the Architect with zero concerns, the Lead last. finalize and approve both re-check that against the SHA-256, and the PRD is handed over as a PDF. After approval the Chief Engineer implements in an isolated clone, the harness merges your base branch, runs your verification gates, and only then pushes and opens the pull request. Anything that fails is reported as BLOCKED — never as done.
Verification gates
Standards are checked by commands, not by a model's word:
verification:
gates:
- name: "test"
command: "npm test"
standard: "12-point #4 Testing & Release Engineering"
- name: "dependency-audit"
command: "npm audit --audit-level=high"
standard: "12-point #3 Software Supply Chain"Every run writes an evidence record to the session and a gate summary into the pull request body.
It has done this to itself
The council specified a feature for this repository, Claude implemented it, the gates passed, and it opened PR #1. That PR then failed CI on a semantic merge conflict the harness had not checked for — so the harness now merges the base branch before its gates run, and the feature it wrote (council gates) is in this release.
Honest limits
- A full council takes roughly 10–40 minutes and uses real subscription quota.
- Live runs so far are single digits; one in five stalled without producing a document.
- macOS and Linux only (gates run through a POSIX shell). CI covers Node 18/20/22 on Ubuntu and macOS.
gemini-cliis unusable on current individual Gemini tiers — useagyfor Gemini seats.- The Ollama adapter has never been run.
- Neither Antigravity nor
gemini-clican be stripped of tools, so neither may hold the zero-tool Architect seat;doctorwarns about this.
Getting started
npm install -g https://github.com/goshtasb/OpenCouncil/releases/download/v0.1.0/open-council-0.1.0.tgz
council init
council doctor
council backlog add "..." --priority 1
council open my-change --item 001 && council deliberate <session>Contributions welcome — see CONTRIBUTING.md. Provider adapters, gate recipes for other stacks, and reports of councils that went wrong are the most useful right now.