How to Interpret the Vote Tally in the Final Council Verdict

The vote tally in a Council of High Intelligence verdict displays weighted votes from each panel member, applies a two-thirds consensus threshold to the total weight, and reveals which specific members backed each option to ensure fully transparent decision-making.

The council-of-high-intelligence repository by 0xNyk implements a deliberative AI panel system where the final verdict includes a machine-readable vote tally that makes the decision-making process auditable. Understanding how to read this tally requires knowing how member weights are assigned, how the consensus threshold is calculated, and how the STANCE lines are parsed into the final weighted totals.

How Weighted Votes Are Assigned

Every panel member contributes a default weight of 1.0 to the final tally. However, the member designated as the domain-weight seat—selected during STEP 0 in SKILL.md—carries an additional 0.5× multiplier, resulting in a total weight of 1.5.

In a standard triad configuration, this creates a W_total of 3.5 (two members at 1.0 plus one domain-weight seat at 1.5). This weighting mechanism ensures that the domain expert has decisive influence while maintaining collective governance.

Parsing STANCE Lines from STEP 5

During STEP 5 (Final Crystallization), each council member emits a machine-parseable line in the following format:

STANCE: <option> | CONFIDENCE: <high|med|low> | DEALBREAKER: <yes|no>

The coordinator extracts these lines from the deliberation log and performs two critical operations:

1. Label normalization – Synonymous labels (e.g., "monorepo" versus "single repo") are canonicalized to a single option identifier.
2. Abstention handling – Members who vote abstain are excluded from option-specific tallies, but their 1.0 weight is still counted toward W_total for the consensus calculation.

Calculating Consensus Thresholds

The consensus test occurs in STEP 6 (Tie-Breaking) and follows a strict mathematical rule. An option reaches consensus only if:

W_option ≥ (2/3) × W_total

For the triad example with W_total = 3.5, the threshold becomes 2.333. The highest-weight option that meets or exceeds this value becomes the verdict. If no option clears this bar, the tally records the split and the verdict states "No consensus reached."

Reading the Vote Tally Fields

The final verdict renders the tally using a structured format defined in verdict-template.md. Here is an example excerpt from the "Council Verdict (Full Mode)" template:

### Vote Tally

- `monorepo — 2.5 (Ada [1.5×, domain], Feynman)` ✅ cleared 2.333 threshold
- `polyrepo — 1.0 (Torvalds)`
- **W_total** 3.5 · **threshold** 2.333 · **monorepo carries**

Each field carries specific meaning:

• <option> — <weight> – The canonical label and total weighted vote count for that option.
• (<backer> [<weight>×, domain]) – Lists supporting members. The domain-weight seat is explicitly marked with [1.5×, domain].
• ✅ cleared <threshold> – Indicates the option satisfied the two-thirds consensus rule.
• W_total <value> – The sum of all member weights, including abstentions.
• threshold <value> – The numeric target calculated as 2/3 × W_total.

Summary

• Weighted voting assigns 1.0 to standard members and 1.5 to the domain-weight seat selected in STEP 0.
• STANCE lines in STEP 5 provide the raw data that the coordinator normalizes and tallies, filtering out abstentions from option counts while keeping their weight in W_total.
• Consensus requires an option to reach at least two-thirds of W_total (e.g., 2.333 for a 3.5 total).
• Source files defining this logic include SKILL.md (execution steps), verdict-template.md (output formatting), and agent files in agents/ (weight definitions).

Frequently Asked Questions

What happens if no option clears the two-thirds threshold?

If no option meets the 2/3 × W_total requirement, the Vote Tally lists each option with its accumulated weight and explicitly notes that "no option cleared 2/3 → escalated to user." The verdict then records "No consensus reached" and the decision is escalated to human review rather than returning a panel recommendation.

How is the domain-weight seat determined?

The domain-weight seat is selected during STEP 0 (Parse Mode and Select Panel) based on the specific domain expertise required for the deliberation. According to the source code in SKILL.md, this seat receives the 1.5× weight multiplier. The selection logic examines agent definitions in the agents/ directory (e.g., council-ada.md), where each agent's front-matter specifies their domain and model weight eligibility.

Are abstain votes counted in the final tally?

Yes, but with an important distinction. In STEP 5, abstain entries are discarded from the option-specific tallies (W_option), meaning they do not contribute to any particular choice. However, the weight of abstaining members (1.0 each) is still included in W_total when calculating the consensus threshold, ensuring the two-thirds bar reflects the full panel composition.

Where is the consensus logic implemented in the codebase?

The consensus calculation and tally generation logic resides in STEP 6 of SKILL.md, specifically within the Tie-Breaking section. This section defines how W_total and W_option are computed, applies the 2/3 threshold test, and assembles the final output using the "Council Verdict (Full Mode)" template that inserts the computed values into the Vote Tally block.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}