Model committee sol

Model Committee (Sol-chaired)

Run GPT-5.6 "Terra" and Claude Opus 5 as a deliberating committee with GPT-5.6 "Sol" as the chair. Keep the line to model-council-voting sharp: a council measures independent disagreement, while this committee deliberately exposes each member to the other's argument and returns one decision.

Read reference/protocol.md completely before running a committee. It carries the use-case gate, the brief template, the three round contracts, the decision rule, and the decision.md schema.

Sol chairs here because it is neither deliberating member — cross-family to the Opus member and a distinct 5.6 tier from the Terra member, so of the three chairs it is the least entangled with the Claude-family member's reasoning. It is not independent of the GPT-family member. Siblings: model-committee (Opus 5 chairs) and model-committee-fable (Fable 5 chairs).

Gate the workflow

Run only when the user invokes /model-committee-sol or asks for a Sol-chaired Terra / Opus deliberation. The external calls draw plan credits or API spend on both providers — surface that and get confirmation unless the user has already accepted it. Apply the protocol's use-case gate first; if the task does not qualify, name the right alternative and call no model.

Before the first call:

1. Confirm the decision that must be returned.
2. Confirm the material may be sent to both providers — both members and the Sol chair are external calls.
3. Precommit the evaluation criteria, weights, and tie rule.

Preflight members and chair

Resolve SKILL_DIR as the directory containing this SKILL.md, then run:

"$SKILL_DIR/scripts/codex-member.sh" --check
"$SKILL_DIR/scripts/claude-member.sh" --check

Default pins:

• GPT member: gpt-5.6-terra (reasoning effort: xhigh) — deliberately the balanced 5.6 tier, not gpt-5.6-sol, because the chair below is Sol and a chair identical to a member would defeat the point of this variant
• Claude member: claude-opus-5 (reasoning effort: high)
• Chair: gpt-5.6-sol (Sol), reasoning effort: xhigh

These are exact pins, not moving aliases. --check above only confirms the CLI is installed; whether a specific pin such as gpt-5.6-sol is actually available surfaces on the first real call, not at preflight. If a pin is unavailable, report it and ask whether to stop or use a named replacement — and if gpt-5.6-sol is missing on this machine, stop and ask rather than falling back to gpt-5.6-terra for the chair.

Run the committee

Create a temporary working directory such as .committee-tmp/<slug>/. Follow the protocol's prompt contracts and produce these artifacts:

brief.md
round-1-gpt.prompt.md       round-1-gpt.md
round-1-opus.prompt.md      round-1-opus.md
round-2-gpt.prompt.md       round-2-gpt.md
round-2-opus.prompt.md      round-2-opus.md
round-3-gpt.prompt.md       round-3-gpt.md
round-3-opus.prompt.md      round-3-opus.md
chair.prompt.md             decision.md

Invoke each member through the bundled read-only driver:

"$SKILL_DIR/scripts/codex-member.sh" \
  --prompt-file <prompt.md> --out <output.md> --effort xhigh -C <working-directory>

"$SKILL_DIR/scripts/claude-member.sh" \
  --prompt-file <prompt.md> --out <output.md> --effort high -C <working-directory>

Launch both calls in a round concurrently when the runtime supports it. Sequential execution is acceptable only if the second prompt was frozen before the first result arrived — otherwise round 1 stops being blind.

Chair with Sol, without becoming a third debater

Inside a Codex/Sol session, chair directly. Otherwise — the common case in Claude Code — delegate only the post-round-3 chair step, bundling the brief and all round outputs into chair.prompt.md under the protocol's decision-rule and output contracts:

"$SKILL_DIR/scripts/codex-member.sh" \
  --prompt-file chair.prompt.md --out decision.md --model gpt-5.6-sol --effort xhigh -C <working-directory>

Chairing is procedural: validate the round outputs against the protocol's schemas, aggregate the predeclared weighted scores, apply the precommitted tie rule, and synthesize only components both revisions explicitly marked compatible. Never introduce a new substantive option, and never break a tie by confidence, eloquence, or model identity. If the evidence stays genuinely unresolved, return the exact fork to the user; a forced but unsupported answer is not committee consensus.

Delegating the chair does not delegate the process. Check the chair's arithmetic against the round-3 score tables and confirm its decision matches the precommitted rule before delivering.

Deliver

Return a compact decision record containing:

1. use case and why committee treatment was justified;
2. decision and decision rule (note that Sol chaired);
3. strongest reasons and evidence;
4. what changed during deliberation;
5. surviving dissent or uncertainty;
6. implementation or verification next step.

Delete .committee-tmp/ after delivery unless the user wants the full transcript kept. Implement only once the decision is accepted.