What Is the Problem Restate Gate in the Council of High Intelligence Protocol?

The Problem Restate Gate is a mandatory first checkpoint in the Council of High Intelligence protocol that requires every council member to produce parallel restatements of the problem before analysis begins, catching wrong-question failures early and ensuring diverse analytical perspectives.

The Problem Restate Gate serves as the foundational validation layer in the Council of High Intelligence, an open-source deliberation framework maintained at 0xNyk/council-of-high-intelligence. As defined in [SKILL.md](https://github.com/0xNyk/council-of-high-intelligence/blob/main/SKILL.md#L209), this gate operates at Step 1.5 of the protocol, forcing a hard stop for problem clarification before any model inference occurs. Its implementation prevents the council from wasting computational cycles on malformed questions by surfacing interpretive divergences immediately.

Core Purpose: Catching Wrong Questions Early

The primary function of the Problem Restate Gate is to detect wrong-question failures before the council enters multi-round deliberation. According to the repository's [README.md](https://github.com/0xNyk/council-of-high-intelligence/blob/main/README.md#L75), the gate addresses the critical risk that ambiguous or misguided prompts will propagate through expensive inference cycles.

When the coordinator initializes a session, it spawns parallel restatement requests to all members. Each member must generate two specific outputs:

1. Restatement – A single sentence capturing the core question from the member's analytical perspective.
2. Alternative framing – A single sentence re-phrasing the problem to expose angles missed in the original wording.

These outputs are collected and displayed in the Round 1 prompt, allowing the coordinator to detect significant divergences from the original problem statement.

How the Gate Ensures Analytical Diversity

The gate leverages the distinct identities defined in the agents/*.md files to ensure diverse perspectives from the start. Each council member—whether embodying Socrates, Feynman, or Watts—encodes their unique analytical lens directly into their restatement.

This diversity serves two functions:

• Validation through divergence: If three independent perspectives produce incompatible restatements, the coordinator flags the ambiguity to the user.
• Perspective preservation: The restatements are embedded in the transcript, making the council's interpretive framework transparent to users.

Source Code Implementation

The Problem Restate Gate is formally specified in [SKILL.md at line 209](https://github.com/0xNyk/council-of-high-intelligence/blob/main/SKILL.md#L209), which defines the exact wording, parallel spawn logic, and checkpoint review process. A variant for Codex execution mode exists in [SKILL.codex.md](https://github.com/0xNyk/council-of-high-intelligence/blob/main/SKILL.codex.md).

The coordinator script implements this logic by iterating through council members and injecting the restatement block before analysis. The automated validation is tested via [scripts/council-simulation-checklist.sh](https://github.com/0xNyk/council-of-high-intelligence/blob/main/scripts/council-simulation-checklist.sh), which verifies gate execution during simulated sessions.

Practical Implementation Example

The coordinator constructs the restatement prompt dynamically based on each member's definition. Below is a conceptual bash snippet illustrating how the coordinator injects the Problem Restate Gate before analytical steps:

# Coordinator snippet (conceptual)

for member in "${council_members[@]}"; do
  cat <<EOF | run_member "$member"
The problem under deliberation:
${PROBLEM}

Before you begin analysis, restate this problem in TWO parts:
1. Your restatement (one sentence).
2. Alternative framing (one sentence).

Do NOT begin analysis yet. 50 words max total.
EOF
done

A concrete output from a council member (e.g., Watts) would appear as:

**Restatement (Watts):** "Is the perceived problem actually a symptom of a deeper misunderstanding about the system's purpose?"

**Alternative framing:** "Maybe the question assumes a fixed goal, but the goal itself might need redefining."

These restatements are automatically included in the Round 1 prompt, after which the coordinator proceeds with parallel analysis only if the gate check passes.

Benefits of the Problem Restate Gate

The Problem Restate Gate provides four critical advantages to the deliberation workflow:

• Early detection of malformed questions: By forcing three or more independent framings, the gate surfaces ambiguity before costly model inference begins.
• Compute efficiency: Wrong questions are caught at Step 1.5, preventing the multi-round deliberation from running on irrelevant material.
• Transparency: Restatements appear in the transcript, giving users clear visibility into how the council interpreted their query.
• Diverse foundation: Each member's lens is encoded in their restatement, ensuring subsequent analysis builds on distinct viewpoints.

Summary

• The Problem Restate Gate is the mandatory first checkpoint in the Council of High Intelligence protocol, operating at Step 1.5 before any analysis occurs.
• It requires every council member to produce two parallel restatements: a core restatement and an alternative framing.
• The gate is defined in [SKILL.md](https://github.com/0xNyk/council-of-high-intelligence/blob/main/SKILL.md#L209) and leverages member definitions from agents/*.md to ensure diverse perspectives.
• Divergence detection prevents wasted compute by catching wrong questions early in the deliberation cycle.
• Implementation includes automated testing via [scripts/council-simulation-checklist.sh](https://github.com/0xNyk/council-of-high-intelligence/blob/main/scripts/council-simulation-checklist.sh).

Frequently Asked Questions

What happens if council members disagree on the problem restatement?

If the coordinator detects significant divergence between the original problem and any member's restatement, or between the restatements themselves, the gate flags the issue to the user. This triggers a clarification request, allowing the user to rephrase the query before the council proceeds to analytical rounds. The transcript preserves all restatements to show exactly where interpretations differed.

How does the Problem Restate Gate reduce computational waste?

By enforcing validation at Step 1.5—before any analytical inference occurs—the gate prevents the council from executing expensive multi-round deliberations on malformed or ambiguous questions. This early exit condition, implemented in the coordinator logic described in [SKILL.md](https://github.com/0xNyk/council-of-high-intelligence/blob/main/SKILL.md#L209), ensures computational resources are only spent on well-defined problems.

Where is the Problem Restate Gate defined in the source code?

The gate's protocol definition resides in [SKILL.md at line 209](https://github.com/0xNyk/council-of-high-intelligence/blob/main/SKILL.md#L209), which specifies the exact restatement requirements and checkpoint logic. The repository's [README.md at line 75](https://github.com/0xNyk/council-of-high-intelligence/blob/main/README.md#L75) provides the high-level design rationale. A Codex-specific variant appears in [SKILL.codex.md](https://github.com/0xNyk/council-of-high-intelligence/blob/main/SKILL.codex.md).

Can the Problem Restate Gate be modified or disabled?

While the core protocol in [SKILL.md](https://github.com/0xNyk/council-of-high-intelligence/blob/main/SKILL.md#L209) treats the gate as mandatory for standard council operations, the open-source nature of 0xNyk/council-of-high-intelligence allows forked implementations to adjust the validation logic. However, disabling the gate would remove the early detection safeguard against wrong-question failures, increasing the risk of wasted compute on ambiguous queries.

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