convergence-debugger

Diagnose convergence failures in AI Counsel deliberation transcripts and configurations.

Updated Dec 14, 2025
One-click install
npx skills add https://github.com/Raudbjorn/cognitive-construct --skill convergence-debugger-raudbjorn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convergence-debugger
Source: https://github.com/Raudbjorn/cognitive-construct/tree/main/rhetoric/scripts/ai-counsel/.claude/skills/convergence-debugger
Command: npx skills add https://github.com/Raudbjorn/cognitive-construct --skill convergence-debugger-raudbjorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When AI models in a deliberation system fail to converge or stop early as expected, it leads to wasted API calls, prolonged debates, and inconclusive results. This Skill provides a systematic debugging guide to diagnose and resolve these issues.

Core Features & Use Cases

  • Transcript Analysis: Learn to interpret deliberation transcripts for convergence information, similarity scores, and voting outcomes.
  • Configuration Checks: Verify key settings like semantic_similarity_threshold, min_rounds_before_check, and early_stopping parameters.
  • Backend Selection: Understand how the system selects similarity backends (SentenceTransformer, TF-IDF, Jaccard) and ensure the best one is installed for accurate semantic comparison.
  • Voting vs. Semantic Conflicts: Diagnose conflicts between model voting outcomes and semantic similarity status, understanding precedence rules.
  • Use Case: Your multi-model debate consistently runs for the maximum number of rounds, even when responses appear similar. Use this skill to check if min_rounds_before_check is too high, if a less accurate similarity backend is being used, or if models are failing to signal continue_debate: false in their votes.

Quick Start

Begin by examining the deliberation transcript (transcripts/*.md) for the "Convergence Information" section to check the reported status and similarity scores.

Frequently Asked Questions about convergence-debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my AI deliberation system keep running for maximum rounds instead of stopping early?

Early stopping failures usually stem from `min_rounds_before_check` set too high, an inaccurate similarity backend (like TF-IDF instead of SentenceTransformer), or models failing to signal `continue_debate: false` in their votes. Check your convergence transcript's similarity scores and voting outcomes to diagnose which factor is preventing consensus.

How do I interpret convergence information in deliberation transcripts?

Deliberation transcripts contain a dedicated Convergence Information section reporting similarity scores, voting outcomes, and stopping signals across rounds. Examine these metrics to identify where the system diverges: semantic similarity may show consensus while votes conflict, or vice versa. Understand precedence rules to diagnose voting versus semantic conflicts.

What convergence configuration settings affect how quickly AI models reach consensus?

Key settings include `semantic_similarity_threshold` (consensus trigger), `min_rounds_before_check` (delay before evaluation), `consecutive_stable_rounds` (stability window), and `early_stopping` flag (enable/disable). Misconfigured thresholds or minimum rounds directly prolong deliberation and waste API calls by preventing or delaying convergence detection.

How do I choose the right similarity backend for accurate semantic comparison in deliberations?

The system selects from SentenceTransformer, TF-IDF, and Jaccard backends. SentenceTransformer provides the most accurate semantic similarity; TF-IDF and Jaccard are less precise but faster. Verify which backend is installed and active; a lower-accuracy backend may fail to detect genuine consensus, forcing extra rounds.

When voting outcomes and semantic similarity disagree, which signal takes precedence in convergence?

Convergence debugging requires understanding conflict precedence: identify whether models are voting to continue debate despite high semantic similarity, or vice versa. This diagnostic step reveals whether the issue is misconfigured voting logic, threshold misalignment, or backend accuracy problems affecting consensus detection.

What validation steps confirm a convergence issue is resolved?

After adjusting thresholds, backends, or voting logic, re-run the deliberation and check the transcript's Convergence Information section for improved similarity scores, earlier consensus detection, and reduced round count. Validate backend installation and configuration against recommended settings to confirm the fix prevents future failures.