Council

council

A council is four to five subagents that hold different positions on one decision. Each round runs them in parallel and feeds every member the rounds before it. The run ends with one recommendation and the position that lost.

Council weighs options against each other. To attack a single proposal, use red-team.

Adapted from the Council skill in LifeOS by Daniel Miessler (https://github.com/danielmiessler/LifeOS), MIT.

Procedure

Copy this checklist and track progress:

- [ ] 1. State the decision in one sentence
- [ ] 2. Pick DEBATE or QUICK
- [ ] 3. Pick a preset, or compose a council
- [ ] 4. Collect the evidence the members need
- [ ] 5. Run the rounds
- [ ] 6. Check every round with the clerk
- [ ] 7. Write the synthesis

1 — State the decision. Write the question the council answers and the options on the table. A question with one factual answer is not a council topic. Answer it directly and stop.

2 — Pick the mode.

Default to QUICK. Escalate to DEBATE when the members disagree about facts, not about taste.

3 — Pick a preset. Read the one file that matches the topic. Do not read the others.

If no preset fits, read references/compose.md and write the briefs there. If the caller names the members, use those names and skip this step.

Never launch the same brief twice. Identical members agree, and agreement carries no information.

4 — Collect the evidence. Each preset names what its members demand. Gather it before round 1 and put it in every member prompt. A member that has to guess produces an unverified claim, and step 6 discards it.

5 — Run the rounds. Read references/rounds.md for the per-round prompts and the subagent type each member runs as. Launch every member of one round in a single message, one Agent call each. Print each round before the next round starts.

6 — Check every round with the clerk. Launch council-clerk on the round text as soon as the round is printed. It resolves every citation the members wrote and reports the claims the evidence does not support. Apply its verdicts to the transcript before the next round runs, so round 2 challenges a corrected round 1. references/rounds.md carries the clerk prompt.

7 — Write the synthesis. Read references/output-format.md. The synthesis ends with one recommendation and the minority position, named and attributed to the member who holds it.

Evidence rule

A council member states a position. The evidence rule decides which of its claims survive.

• The topic is a repository, a dataset or a document. A member cites a file path, a line number, a command output or a quoted figure for every factual claim.
• The topic is a choice about the world — a trip, a portfolio, a purchase. A member cites the fare, the fact sheet, the schedule or the rule text that it read.
• A claim with no pointer is marked [unverified] in the transcript, at the claim.
• Keep the marked claim. Do not delete it and do not repair it. A load-bearing claim that nobody can check is itself a finding, and the synthesis reports it as one.
• A member marks its own claims, so a member that wants to win simply does not mark them. The council-clerk agent in step 6 is what makes the rule real: it re-reads every pointer and returns resolves, narrower, contradicted, missing or uncited per claim. The clerk's verdict overrides the member's own mark, in both directions.

Error handling

• Every member agrees in round 1. Say so, stop, and report the agreement. A debate with no disagreement is a receipt, not a deliberation.
• A member cites a file that does not exist. The clerk returns missing. Drop the claim, and name the member and the path in the synthesis.
• The clerk returns narrower or contradicted. Keep the claim, annotate it in the transcript with what the source actually says, and let the next round argue against the corrected version. A member whose evidence says less than it claimed is a finding the synthesis reports.
• The harness has no council-* subagent types. They ship in this Pack's agents/ directory and only a harness with native subagents installs them. Fall back to general-purpose for every member and for the clerk, and paste the read-only contract into each prompt: read only, never edit, cite or mark, return the round text alone.
• A member argues a position it was not given. Keep the argument and record the drift. Do not re-run the member to make it stay in role.
• The caller wants an attack, not a comparison. Stop and use red-team.