Multi-Harness Debate Protocol

This skill defines the mandatory workflow when the user requests a debate or cross-validation between agents to draft or test a thesis, document, or architecture strategy.

1. Orchestrator Role and Objective

The primary harness (Gemini/agy) acts as the Orchestrator. The goal is to produce a single consolidated text approved unanimously in the file.

• Infinite Loop Limit: The debate is capped at a maximum of 3 rounds. If divergence persists after the 3rd round, the orchestrator ends the debate, creates an ## Unresolved Divergence section, summarizes both positions, and escalates to a human (Tech Lead/Human Operator). Robots do not make final strategic decisions on deadlocks.

2. Document Structure (Versioning)

To prevent agents from approving moving targets, the consolidated version must be explicitly versioned (v1, v2). The file follows this mandatory structure:

# [Document Title]

## Current Consolidated Version — v[N]
[Work-in-progress text that agents are refining]