5dive-ai

5dive Council — AI skill for Claude Code

AI community

Governance for AI agents: a multi-agent council that deliberates, votes by quorum on a bar scaled to the stakes, seals every decision to a verifiable receipt, and keeps a human veto.

How to install 5dive Council

This entry records only its repository, not the path inside it, so there is no exact command to give. Open 5dive-ai/5dive-council and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What 5dive Council does

Governance for AI agents: a multi-agent council that deliberates, votes by quorum on a bar scaled to the stakes, seals every decision to a verifiable receipt, and keeps a human veto. Self-hosted 5dive plugin for Claude Code and Codex agent teams.

Alternatives in AI

Claude Skills LLM Council — LLM Council — a Claude Code skill that runs your decisions through 5 AI advisors with peer review 1.7k ★
Room — Open-source earning-focused swarm intelligence engine 838 ★
LLM Council Skill — A skill to claude code that enables brainstorming with other LLMs (ChatGPT, Gemini) before presenting the impl 416 ★

README

5dive council

**Governance for AI agents, with a human veto.** What a council is and how it decides — quorum, a vote bar that scales with the stakes, sealed receipts, the final human veto: **[5dive.ai/council](https://5dive.ai/council)**.

A sealed deliberation council for your 5dive agents, as a plugin: convene a panel of seats on a question, run seat motions and constitutional amendments, give a founder a veto, and keep every verdict in a tamper-evident lineage.

sudo 5dive plugin add 5dive-ai/5dive-council
5dive council --help

What moved, and what did not

Council used to be built into the core CLI. It is now opt-in: a box that never convenes a council no longer parses ~12k lines of it on every `5dive` call.

**What stays in core** is everything a box needs whether or not it runs a council: the constitution file, its one parser, the tier-2 human-gate floor `5dive task need` enforces, and the *reader* of the seal. Core decides whether to trust `constitution.yaml` by reading the newest `constitutionDigest` in `/var/lib/5dive/council/lineage.jsonl` as data. Installing or removing this plugin changes nothing about how gates are enforced.

**What this plugin is** is the deliberation that *writes* that lineage: `convene`, `bench`, `schedule`, `roster`, `promote|demote|expel`, `amend`, `veto`, `gate-clear`, `rot-triage`, `record`, `verify`, `sign-vote`, `ballot-tap`.

**Your existing council keeps working.** The state lives where it always did (`/var/lib/5dive/council/`: genesis, lineage, receipts, benches, schedules). A lineage sealed by the built-in council verifies under this plugin, and records this plugin seals verify under core — `tests/council_plugin_unit.sh` P5 proves both directions against the last core release that carried council.

Which core you need

On a core that still has the built-in `council` verb, this install is **refused** (`council` is already a 5dive command) — that is correct, the two cannot both claim the verb. Install it