domains / families / agent-tooling / polis-protocol

polis-protocol

separate

Coordinate multi-vendor AI agents as a self-improving team — a learning router assigns work by track record and citizens can amend the protocol's own rules.

When to use

• Use when 2+ agents (especially across vendors) work on one project and "who should do this" is a real question.
• Use when you want the team to measurably improve over time — routing that adapts from outcomes, not static role labels.
• Use when you need a durable, git-auditable record of who did what, what was learned, and which rules changed.
• Use when Antigravity's default orchestration is too rigid and you want routing + governance on top of it.

When not to use

• Routing quality depends on accurate citizen capability cards and enough settled work history to learn from.
• The protocol coordinates agent work but does not replace review, tests, or explicit maintainer approval.
• Multi-agent voting and amendments can add process overhead for small, single-owner tasks.
• The upstream scripts are external code; pin to a reviewed commit and run `--dry-run` before allowing writes to a project.

Skill page

Source