build-consensus
À propos
Cette compétence permet de parvenir à un accord distribué sans autorité centrale en utilisant des mécanismes tels que le vote à seuil et la détection de quorum. Elle couvre la génération de propositions, la dynamique de plaidoyer et la résolution des blocages pour les scénarios où un groupe doit décider sans leader désigné. Les développeurs peuvent l'utiliser lorsque la prise de décision centralisée constitue un goulot d'étranglement ou lors de la conception de systèmes automatisés, comme les bases de données distribuées ou les IA multi-agents, qui nécessitent un consensus.
Installation rapide
Claude Code
Recommandénpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/build-consensusCopiez et collez cette commande dans Claude Code pour installer cette compétence
Documentation
Build Consensus
Collective agreement across distributed agents w/o central authority — scout advocacy, threshold quorum sensing, commit dynamics from honeybee swarm decisions.
Use When
- Group must decide between many options w/o designated leader
- Centralized decision = bottleneck or single point of failure
- Stakeholders diff info/perspectives must be integrated
- Past decisions suffered groupthink (premature conv) or analysis paralysis (no conv)
- Designing auto systems needing consensus (distributed DBs, multi-agent AI)
- Complements
coordinate-swarmwhen coordination needs explicit collective decisions
In
- Required: Decision (binary, select from N, param set)
- Required: Participating agents (team, services, voters)
- Optional: Known options w/ prelim quality assessments
- Optional: Urgency (time budget)
- Optional: Acceptable err rate (group occasionally pick 2nd-best?)
- Optional: Current failure mode (groupthink, deadlock, flip-flop)
Do
Step 1: Generate Proposals — Independent Scouting
Decision space explored before advocacy begins.
- Assign scouts to independently explore:
- Each scout evaluates w/o knowing others' findings
- Independent eval prevents early herding → popular-but-mediocre
- Scout count: min 3 per serious option (reliability)
- Scouts produce structured assessments:
- Option ID
- Quality score (normalized 0-100 or categorical: poor/fair/good/excellent)
- Key strengths + risks
- Confidence (how thoroughly evaluated?)
- Aggregate reports w/o filter — all above min quality enter advocacy
→ Independently evaluated proposals w/ scores + assessments. No option eliminated by single evaluator; perspective diversity preserved.
If err: Scouts converge on same option w/o independent eval → scouting not truly independent. Rerun w/ explicit info barriers. Too many survive → raise min threshold. Too few → lower or add scouts.
Step 2: Advocacy Dynamics (Waggle Dance)
Scouts advocate preferred options, intensity proportional to quality.
- Each scout advocates top-rated:
- Intensity proportional to quality (better → more vigorous)
- Public — all observe
- Present evidence + quality, not just pref
- Uncommitted observe + evaluate:
- Follow up by inspecting independently
- Own inspection confirms → join advocacy
- Inspection shows lower quality → don't join
- Cross-inspection dynamics:
- Weaker advocates naturally lose followers as agents verify
- Stronger gain through confirmed quality
- Self-correcting: exaggerated advocacy fails verification
Advocacy Dynamics:
┌─────────────────────────────────────────────────────────┐
│ Scout A advocates Option 1 (quality 85) ──→ ◉◉◉◉◉ │
│ Scout B advocates Option 2 (quality 70) ──→ ◉◉◉ │
│ Scout C advocates Option 3 (quality 45) ──→ ◉ │
│ │
│ Uncommitted agents inspect: │
│ Agent D inspects Option 1 → confirms → joins ◉◉◉◉◉◉ │
│ Agent E inspects Option 2 → confirms → joins ◉◉◉◉ │
│ Agent F inspects Option 3 → disagrees → inspects Opt 1│
│ → confirms → joins ◉◉◉◉◉◉◉│
│ │
│ Over time: Option 1 advocacy grows, Option 3 fades │
└─────────────────────────────────────────────────────────┘
→ Advocacy for best option(s) grows as agents verify. Weaker fades. Group converges naturally w/o any agent dictating.
If err: No convergence (2 options neck-and-neck) → genuinely equivalent, proceed to quorum w/ either or tiebreaker. Converges too fast on mediocre → increase eval independence (more scouts, stricter barriers) + mandatory cross-inspection.
Step 3: Quorum Threshold + Commit
Commit threshold → collective action.
- Set quorum:
- Simple: 50% + 1
- Important: 66-75%
- Critical/irreversible: 80%+
- Rule: higher stakes → higher quorum → slower but more reliable
- Monitor commit accumulation:
- Track # committed per option over time
- Transparent (all see state)
- No commit withdrawal mid-cycle (prevents oscillation)
- Quorum reached:
- Winning option = collective decision
- Losers ack (no rogue agents)
- Implement immediately — delay erodes commit
→ Clear quorum moment, enough agents independently committed. Legitimate because emerged from independent eval, not authority.
If err: Quorum never reached in time → escalate Step 4. Reached but agents unhappy → advocacy too short, committed w/o adequate eval. Wrong consensus (discovered after) → independent scouting insufficient, increase scout diversity + eval thoroughness next cycle.
Step 4: Deadlock Resolution
Break gridlock when natural process stalls.
- Diagnose type:
- Genuine tie: Equally good → flip coin; delay cost exceeds picking "wrong" equal
- Info deficit: Can't eval well → invest more scouting before re-advocacy
- Faction: Entrenched subgroups refuse to cross-inspect → mandatory rotation, advocates inspect opposing
- Option proliferation: Too many fragment commit → eliminate bottom 50%, re-advocate
- Apply resolution:
- Tie: random or merge if compatible
- Deficit: time-boxed scouting extension
- Faction: forced cross-inspection round
- Proliferation: ranked elimination tournament
- After res, reset quorum clock, re-run Step 3
→ Deadlock resolved via intervention. Visible + accepted as fair process even if indiv preferred diff outcome.
If err: Deadlocks recur on same decision → framing wrong. Step back: decomposable into smaller independent decisions? Scope reduction? "Try both and see"? Sometimes best consensus = "time-boxed experiment".
Step 5: Consensus Quality
Eval whether process produced good decision, not just decision.
- Post-decision:
- Winning option independently verified by ≥N agents?
- Speed appropriate (not too fast/groupthink, not too slow/paralysis)?
- Process surfaced info missed by single decider?
- Agents committed to impl or merely compliant?
- Health metrics:
- Time to quorum: decreasing = learning; increasing = complexity/dysfunction
- Scout-to-commit ratio: scouting per commit. High = difficult or low trust
- Post-decision regret rate: how often group wishes diff?
- Feed learnings back:
- Adjust thresholds based on importance + past accuracy
- Adjust scout count based on complexity
- Adjust time budgets based on historical time-to-quorum
→ Feedback loop improves quality over time. Group learns to scout better, advocate honestly, commit confidently.
If err: Poor metrics (high regret, slow) → audit for structural fails: insufficient scout diversity, advocacy w/o verification, thresholds too low. Rebuild failing stage vs overhauling whole.
Check
- Proposals via independent scouting (no herding)
- Advocacy proportional to assessed quality
- Uncommitted verified advocated options
- Quorum appropriate for importance
- Quorum reached + implemented promptly
- Deadlock mechanism available (even if unused)
- Post-decision quality assessment done
Traps
- Skip independent scouting: Jump to advocacy → groupthink. Consensus quality = eval quality
- Equal advocacy, unequal options: Same advocacy regardless of quality → random selection. Must be proportional
- Commit withdrawal: Un-commit → oscillation. Once committed in cycle, stay until resolves
- Consensus = unanimity confusion: Consensus = sufficient agreement, not total. Waiting 100% = permanent deadlock
- Ignore losing side: Losers have info group needs. Concerns should inform impl even if don't block
→
coordinate-swarm— foundational coordination framework supporting signal-based consensusdefend-colony— collective defense often needs rapid consensus under threatscale-colony— consensus mechanisms adapt when group size changes significantlydissolve-form— morphic controlled dismantling; consensus before dissolution criticalplan-sprint— sprint planning involves team consensus on scopeconduct-retrospective— retrospectives = consensus-building about process improvementbuild-coherence— AI self-app variant; maps bee democracy to single-agent multi-path reasoning
Dépôt GitHub
Compétences associées
content-collections
MétaCette compétence propose une configuration éprouvée en production pour Content Collections, un outil axé sur TypeScript qui transforme des fichiers Markdown/MDX en collections de données typées de manière sûre avec une validation Zod. Utilisez-la lors de la création de blogs, de sites de documentation ou d'applications Vite + React riches en contenu pour garantir la sécurité de typage et la validation automatique du contenu. Elle couvre tout, de la configuration du plugin Vite et de la compilation MDX à l'optimisation des déploiements et la validation des schémas.
polymarket
MétaCette compétence permet aux développeurs de créer des applications avec la plateforme de marchés prédictifs Polymarket, incluant l'intégration d'API pour le trading et les données de marché. Elle fournit également une diffusion de données en temps réel via WebSocket pour surveiller les transactions en direct et l'activité du marché. Utilisez-la pour mettre en œuvre des stratégies de trading ou pour créer des outils traitant les mises à jour de marché en direct.
creating-opencode-plugins
MétaCette compétence aide les développeurs à créer des plugins OpenCode qui s'interconnectent avec plus de 25 types d'événements tels que les commandes, les fichiers et les opérations LSP. Elle fournit la structure du plugin, les spécifications de l'API événementielle et les modèles d'implémentation pour les modules JavaScript/TypeScript. Utilisez-la lorsque vous avez besoin d'intercepter, de surveiller ou d'étendre le cycle de vie de l'assistant IA OpenCode avec une logique personnalisée pilotée par les événements.
sglang
MétaSGLang est un framework de service LLM haute performance spécialisé dans la génération rapide et structurée pour les workflows JSON, regex et agentiques grâce à son cache de préfixe RadixAttention. Il offre une inférence nettement plus rapide, particulièrement pour les tâches avec des préfixes répétés, ce qui le rend idéal pour les sorties complexes et structurées ainsi que les conversations multi-tours. Choisissez SGLang plutôt que des alternatives comme vLLM lorsque vous avez besoin d'un décodage contraint ou que vous construisez des applications avec un partage étendu de préfixes.
