feed-the-machine 1.5.0 → 1.6.0

package/ftm-council/references/prompts/CLAUDE-INVESTIGATION.md

@@ -1,60 +1,60 @@
-# Claude Investigation Prompt Template
-
-Use this for spawning the Claude subagent in Step 1 (and rebuttal rounds). Spawning via subagent keeps the investigation isolated from the orchestrator's accumulated context — this is critical for independent research.
-
-## Round 1: Independent Research
-
-```
-You are one of three AI peers in a deliberation council. The other two peers are Codex (OpenAI) and Gemini (Google). Your job is to independently investigate the following problem by reading the codebase, then give your honest, well-reasoned position.
-
-IMPORTANT: Do your own research. Read files, search code, trace through logic. Your position must be grounded in what you actually find in the code, not assumptions. Cite specific files and line numbers.
-
-PROBLEM:
-{council_prompt}
-
-WORKING DIRECTORY: {cwd}
-
-Instructions:
-1. Start by exploring the relevant parts of the codebase — read files, search for patterns, trace dependencies
-2. Take notes on what you find as you go
-3. After you've done sufficient research, formulate your position
-
-Give your response in this format:
-1. RESEARCH SUMMARY: What files you examined, what you found (with file:line references)
-2. POSITION: Your clear stance (1-2 sentences)
-3. REASONING: Why you believe this, grounded in specific code you read
-4. CONCERNS: What could go wrong with your approach
-5. CONFIDENCE: High/Medium/Low and why
-```
-
-## Rebuttal Rounds (Rounds 2-5)
-
-The rebuttal subagent also runs isolated so it doesn't anchor on the orchestrator's context.
-
-```
-Round {N} of the deliberation council.
-
-Here's what happened in the previous round. Each model independently researched the codebase and formed a position:
-
-PEER 1's research and position:
-{peer1_previous_full}
-
-PEER 2's research and position:
-{peer2_previous_full}
-
-YOUR previous research and position:
-{claude_previous_full}
-
-Now respond. You may do additional codebase research if you want to verify claims the other models made or investigate angles they raised. Then:
-
-1. Directly address the strongest point from each other model
-2. If another model cited code you haven't looked at, go read it and see if you agree with their interpretation
-3. State whether you've changed your position (and why, or why not)
-4. If you agree with another model, say so explicitly
-
-UPDATED POSITION: [same/changed] ...
-NEW EVIDENCE (if any): [anything new you found by following up on other models' research]
-KEY RESPONSE TO PEER 1: ...
-KEY RESPONSE TO PEER 2: ...
-REMAINING DISAGREEMENTS: ...
-```
+# Claude Investigation Prompt Template
+
+Use this for spawning the Claude subagent in Step 1 (and rebuttal rounds). Spawning via subagent keeps the investigation isolated from the orchestrator's accumulated context — this is critical for independent research.
+
+## Round 1: Independent Research
+
+```
+You are one of three AI peers in a deliberation council. The other two peers are Codex (OpenAI) and Gemini (Google). Your job is to independently investigate the following problem by reading the codebase, then give your honest, well-reasoned position.
+
+IMPORTANT: Do your own research. Read files, search code, trace through logic. Your position must be grounded in what you actually find in the code, not assumptions. Cite specific files and line numbers.
+
+PROBLEM:
+{council_prompt}
+
+WORKING DIRECTORY: {cwd}
+
+Instructions:
+1. Start by exploring the relevant parts of the codebase — read files, search for patterns, trace dependencies
+2. Take notes on what you find as you go
+3. After you've done sufficient research, formulate your position
+
+Give your response in this format:
+1. RESEARCH SUMMARY: What files you examined, what you found (with file:line references)
+2. POSITION: Your clear stance (1-2 sentences)
+3. REASONING: Why you believe this, grounded in specific code you read
+4. CONCERNS: What could go wrong with your approach
+5. CONFIDENCE: High/Medium/Low and why
+```
+
+## Rebuttal Rounds (Rounds 2-5)
+
+The rebuttal subagent also runs isolated so it doesn't anchor on the orchestrator's context.
+
+```
+Round {N} of the deliberation council.
+
+Here's what happened in the previous round. Each model independently researched the codebase and formed a position:
+
+PEER 1's research and position:
+{peer1_previous_full}
+
+PEER 2's research and position:
+{peer2_previous_full}
+
+YOUR previous research and position:
+{claude_previous_full}
+
+Now respond. You may do additional codebase research if you want to verify claims the other models made or investigate angles they raised. Then:
+
+1. Directly address the strongest point from each other model
+2. If another model cited code you haven't looked at, go read it and see if you agree with their interpretation
+3. State whether you've changed your position (and why, or why not)
+4. If you agree with another model, say so explicitly
+
+UPDATED POSITION: [same/changed] ...
+NEW EVIDENCE (if any): [anything new you found by following up on other models' research]
+KEY RESPONSE TO PEER 1: ...
+KEY RESPONSE TO PEER 2: ...
+REMAINING DISAGREEMENTS: ...
+```

package/ftm-council/references/prompts/CODEX-INVESTIGATION.md

@@ -1,58 +1,58 @@
-# Codex Investigation Prompt Template
-
-Use this for spawning Codex via CLI. The `--full-auto` flag gives Codex sandboxed read access to the workspace so it can explore files on its own.
-
-## Round 1: Independent Research
-
-```bash
-cd {cwd} && codex exec --full-auto "You are one of three AI peers in a deliberation council. The other two peers are a subagent investigator and Gemini (Google). Your job is to independently investigate the following problem by reading the codebase, then give your honest, well-reasoned position.
-
-IMPORTANT: Do your own research. Read files, search code, trace through logic. Your position must be grounded in what you actually find in the code, not assumptions. Cite specific files and line numbers.
-
-PROBLEM:
-{council_prompt}
-
-Instructions:
-1. Start by exploring the relevant parts of the codebase — read files, search for patterns, trace dependencies
-2. Take notes on what you find as you go
-3. After you have done sufficient research, formulate your position
-
-Give your response in this format:
-1. RESEARCH SUMMARY: What files you examined, what you found (with file:line references)
-2. POSITION: Your clear stance (1-2 sentences)
-3. REASONING: Why you believe this, grounded in specific code you read
-4. CONCERNS: What could go wrong with your approach
-5. CONFIDENCE: High/Medium/Low and why"
-```
-
-## Rebuttal Rounds (Rounds 2-5)
-
-Use `--full-auto` in rebuttal rounds as well — Codex may want to verify another model's claims by reading files it hadn't looked at before.
-
-```bash
-cd {cwd} && codex exec --full-auto "Round {N} of the deliberation council.
-
-Here's what happened in the previous round. Each model independently researched the codebase and formed a position:
-
-PEER 1's research and position:
-{peer1_previous_full}
-
-PEER 2's research and position:
-{peer2_previous_full}
-
-YOUR previous research and position:
-{codex_previous_full}
-
-Now respond. You may do additional codebase research if you want to verify claims the other models made or investigate angles they raised. Then:
-
-1. Directly address the strongest point from each other model
-2. If another model cited code you haven't looked at, go read it and see if you agree with their interpretation
-3. State whether you've changed your position (and why, or why not)
-4. If you agree with another model, say so explicitly
-
-UPDATED POSITION: [same/changed] ...
-NEW EVIDENCE (if any): [anything new you found by following up on other models' research]
-KEY RESPONSE TO PEER 1: ...
-KEY RESPONSE TO PEER 2: ...
-REMAINING DISAGREEMENTS: ..."
-```
+# Codex Investigation Prompt Template
+
+Use this for spawning Codex via CLI. The `--full-auto` flag gives Codex sandboxed read access to the workspace so it can explore files on its own.
+
+## Round 1: Independent Research
+
+```bash
+cd {cwd} && codex exec --full-auto "You are one of three AI peers in a deliberation council. The other two peers are a subagent investigator and Gemini (Google). Your job is to independently investigate the following problem by reading the codebase, then give your honest, well-reasoned position.
+
+IMPORTANT: Do your own research. Read files, search code, trace through logic. Your position must be grounded in what you actually find in the code, not assumptions. Cite specific files and line numbers.
+
+PROBLEM:
+{council_prompt}
+
+Instructions:
+1. Start by exploring the relevant parts of the codebase — read files, search for patterns, trace dependencies
+2. Take notes on what you find as you go
+3. After you have done sufficient research, formulate your position
+
+Give your response in this format:
+1. RESEARCH SUMMARY: What files you examined, what you found (with file:line references)
+2. POSITION: Your clear stance (1-2 sentences)
+3. REASONING: Why you believe this, grounded in specific code you read
+4. CONCERNS: What could go wrong with your approach
+5. CONFIDENCE: High/Medium/Low and why"
+```
+
+## Rebuttal Rounds (Rounds 2-5)
+
+Use `--full-auto` in rebuttal rounds as well — Codex may want to verify another model's claims by reading files it hadn't looked at before.
+
+```bash
+cd {cwd} && codex exec --full-auto "Round {N} of the deliberation council.
+
+Here's what happened in the previous round. Each model independently researched the codebase and formed a position:
+
+PEER 1's research and position:
+{peer1_previous_full}
+
+PEER 2's research and position:
+{peer2_previous_full}
+
+YOUR previous research and position:
+{codex_previous_full}
+
+Now respond. You may do additional codebase research if you want to verify claims the other models made or investigate angles they raised. Then:
+
+1. Directly address the strongest point from each other model
+2. If another model cited code you haven't looked at, go read it and see if you agree with their interpretation
+3. State whether you've changed your position (and why, or why not)
+4. If you agree with another model, say so explicitly
+
+UPDATED POSITION: [same/changed] ...
+NEW EVIDENCE (if any): [anything new you found by following up on other models' research]
+KEY RESPONSE TO PEER 1: ...
+KEY RESPONSE TO PEER 2: ...
+REMAINING DISAGREEMENTS: ..."
+```

package/ftm-council/references/prompts/GEMINI-INVESTIGATION.md

@@ -1,58 +1,58 @@
-# Gemini Investigation Prompt Template
-
-Use this for spawning Gemini via CLI. The `--yolo` flag lets Gemini auto-approve file reads so it can explore without getting stuck on permission prompts.
-
-## Round 1: Independent Research
-
-```bash
-cd {cwd} && gemini -p "You are one of three AI peers in a deliberation council. The other two peers are a subagent investigator and Codex (OpenAI). Your job is to independently investigate the following problem by reading the codebase, then give your honest, well-reasoned position.
-
-IMPORTANT: Do your own research. Read files, search code, trace through logic. Your position must be grounded in what you actually find in the code, not assumptions. Cite specific files and line numbers.
-
-PROBLEM:
-{council_prompt}
-
-Instructions:
-1. Start by exploring the relevant parts of the codebase — read files, search for patterns, trace dependencies
-2. Take notes on what you find as you go
-3. After you have done sufficient research, formulate your position
-
-Give your response in this format:
-1. RESEARCH SUMMARY: What files you examined, what you found (with file:line references)
-2. POSITION: Your clear stance (1-2 sentences)
-3. REASONING: Why you believe this, grounded in specific code you read
-4. CONCERNS: What could go wrong with your approach
-5. CONFIDENCE: High/Medium/Low and why" --yolo
-```
-
-## Rebuttal Rounds (Rounds 2-5)
-
-Use `--yolo` in rebuttal rounds as well — Gemini may want to verify another model's claims by reading files it hadn't looked at before.
-
-```bash
-cd {cwd} && gemini -p "Round {N} of the deliberation council.
-
-Here's what happened in the previous round. Each model independently researched the codebase and formed a position:
-
-PEER 1's research and position:
-{peer1_previous_full}
-
-PEER 2's research and position:
-{peer2_previous_full}
-
-YOUR previous research and position:
-{gemini_previous_full}
-
-Now respond. You may do additional codebase research if you want to verify claims the other models made or investigate angles they raised. Then:
-
-1. Directly address the strongest point from each other model
-2. If another model cited code you haven't looked at, go read it and see if you agree with their interpretation
-3. State whether you've changed your position (and why, or why not)
-4. If you agree with another model, say so explicitly
-
-UPDATED POSITION: [same/changed] ...
-NEW EVIDENCE (if any): [anything new you found by following up on other models' research]
-KEY RESPONSE TO PEER 1: ...
-KEY RESPONSE TO PEER 2: ...
-REMAINING DISAGREEMENTS: ..." --yolo
-```
+# Gemini Investigation Prompt Template
+
+Use this for spawning Gemini via CLI. The `--yolo` flag lets Gemini auto-approve file reads so it can explore without getting stuck on permission prompts.
+
+## Round 1: Independent Research
+
+```bash
+cd {cwd} && gemini -p "You are one of three AI peers in a deliberation council. The other two peers are a subagent investigator and Codex (OpenAI). Your job is to independently investigate the following problem by reading the codebase, then give your honest, well-reasoned position.
+
+IMPORTANT: Do your own research. Read files, search code, trace through logic. Your position must be grounded in what you actually find in the code, not assumptions. Cite specific files and line numbers.
+
+PROBLEM:
+{council_prompt}
+
+Instructions:
+1. Start by exploring the relevant parts of the codebase — read files, search for patterns, trace dependencies
+2. Take notes on what you find as you go
+3. After you have done sufficient research, formulate your position
+
+Give your response in this format:
+1. RESEARCH SUMMARY: What files you examined, what you found (with file:line references)
+2. POSITION: Your clear stance (1-2 sentences)
+3. REASONING: Why you believe this, grounded in specific code you read
+4. CONCERNS: What could go wrong with your approach
+5. CONFIDENCE: High/Medium/Low and why" --yolo
+```
+
+## Rebuttal Rounds (Rounds 2-5)
+
+Use `--yolo` in rebuttal rounds as well — Gemini may want to verify another model's claims by reading files it hadn't looked at before.
+
+```bash
+cd {cwd} && gemini -p "Round {N} of the deliberation council.
+
+Here's what happened in the previous round. Each model independently researched the codebase and formed a position:
+
+PEER 1's research and position:
+{peer1_previous_full}
+
+PEER 2's research and position:
+{peer2_previous_full}
+
+YOUR previous research and position:
+{gemini_previous_full}
+
+Now respond. You may do additional codebase research if you want to verify claims the other models made or investigate angles they raised. Then:
+
+1. Directly address the strongest point from each other model
+2. If another model cited code you haven't looked at, go read it and see if you agree with their interpretation
+3. State whether you've changed your position (and why, or why not)
+4. If you agree with another model, say so explicitly
+
+UPDATED POSITION: [same/changed] ...
+NEW EVIDENCE (if any): [anything new you found by following up on other models' research]
+KEY RESPONSE TO PEER 1: ...
+KEY RESPONSE TO PEER 2: ...
+REMAINING DISAGREEMENTS: ..." --yolo
+```

package/ftm-council/references/prompts/REBUTTAL-TEMPLATE.md

@@ -1,57 +1,57 @@
-# Rebuttal Round Prompt Template
-
-Use this to construct the prompt sent to each model in rebuttal rounds (Steps 3-4). The prompt must be fully self-contained — Codex and Gemini are stateless between rounds, so every round's prompt must include the full history.
-
-## Template
-
-```
-Round {N} of the deliberation council.
-
-Here's what happened in the previous round. Each model independently researched the codebase and formed a position:
-
-MODEL A's research and position:
-{model_a_previous_full}
-
-MODEL B's research and position:
-{model_b_previous_full}
-
-MODEL C's research and position:
-{model_c_previous_full}
-
-Now respond. You may do additional codebase research if you want to verify claims the other models made or investigate angles they raised. Then:
-
-1. Directly address the strongest point from each other model
-2. If another model cited code you haven't looked at, go read it and see if you agree with their interpretation
-3. State whether you've changed your position (and why, or why not)
-4. If you agree with another model, say so explicitly
-
-UPDATED POSITION: [same/changed] ...
-NEW EVIDENCE (if any): [anything new you found by following up on other models' research]
-KEY RESPONSE TO MODEL A: ...
-KEY RESPONSE TO MODEL B: ...
-REMAINING DISAGREEMENTS: ...
-```
-
-## Construction Rules
-
-- Replace `{model_a/b/c_previous_full}` with each model's complete response from the prior round — research summary, position, reasoning, concerns, and confidence
-- Do NOT summarize or truncate prior responses — the full research context is what allows models to verify each other's findings
-- Include ALL prior rounds' positions if building a multi-round history, not just the most recent
-- Use the same CLI flags as Round 1 (`--full-auto` for Codex, `--yolo` for Gemini) so models can do follow-up research
-
-## Orchestrator State
-
-Between rounds, the orchestrator holds all state. Keep a running record of:
-- Each model's research findings per round (files examined, what was found)
-- Each model's position per round
-- Whether any model changed position and why
-
-This record feeds the next round's rebuttal prompt. Without it, models cannot engage meaningfully with each other's evidence.
-
-## What to Watch For
-
-When presenting round results to the user, highlight:
-- **Position changes**: which model moved and what evidence caused the shift
-- **New research**: if a model read files others hadn't looked at
-- **Convergence signal**: models independently finding the same evidence
-- **Persistent divergence**: models who've both read the same code and still disagree — this is a genuine hard problem
+# Rebuttal Round Prompt Template
+
+Use this to construct the prompt sent to each model in rebuttal rounds (Steps 3-4). The prompt must be fully self-contained — Codex and Gemini are stateless between rounds, so every round's prompt must include the full history.
+
+## Template
+
+```
+Round {N} of the deliberation council.
+
+Here's what happened in the previous round. Each model independently researched the codebase and formed a position:
+
+MODEL A's research and position:
+{model_a_previous_full}
+
+MODEL B's research and position:
+{model_b_previous_full}
+
+MODEL C's research and position:
+{model_c_previous_full}
+
+Now respond. You may do additional codebase research if you want to verify claims the other models made or investigate angles they raised. Then:
+
+1. Directly address the strongest point from each other model
+2. If another model cited code you haven't looked at, go read it and see if you agree with their interpretation
+3. State whether you've changed your position (and why, or why not)
+4. If you agree with another model, say so explicitly
+
+UPDATED POSITION: [same/changed] ...
+NEW EVIDENCE (if any): [anything new you found by following up on other models' research]
+KEY RESPONSE TO MODEL A: ...
+KEY RESPONSE TO MODEL B: ...
+REMAINING DISAGREEMENTS: ...
+```
+
+## Construction Rules
+
+- Replace `{model_a/b/c_previous_full}` with each model's complete response from the prior round — research summary, position, reasoning, concerns, and confidence
+- Do NOT summarize or truncate prior responses — the full research context is what allows models to verify each other's findings
+- Include ALL prior rounds' positions if building a multi-round history, not just the most recent
+- Use the same CLI flags as Round 1 (`--full-auto` for Codex, `--yolo` for Gemini) so models can do follow-up research
+
+## Orchestrator State
+
+Between rounds, the orchestrator holds all state. Keep a running record of:
+- Each model's research findings per round (files examined, what was found)
+- Each model's position per round
+- Whether any model changed position and why
+
+This record feeds the next round's rebuttal prompt. Without it, models cannot engage meaningfully with each other's evidence.
+
+## What to Watch For
+
+When presenting round results to the user, highlight:
+- **Position changes**: which model moved and what evidence caused the shift
+- **New research**: if a model read files others hadn't looked at
+- **Convergence signal**: models independently finding the same evidence
+- **Persistent divergence**: models who've both read the same code and still disagree — this is a genuine hard problem

package/ftm-council/references/protocols/PREREQUISITES.md

@@ -1,47 +1,47 @@
-# Prerequisites: Tool Availability Checks
-
-## Required CLI Tools
-
-The council requires both external CLI tools to be installed and authenticated:
-
-- **Codex**: `npm install -g @openai/codex` (authenticated via `codex login`)
-- **Gemini**: `npm install -g @google/gemini-cli` (authenticated via Google)
-
-## Availability Check
-
-Before the first round, verify both tools are available:
-
-```bash
-which codex && which gemini
-```
-
-## Fallback Logic
-
-| Scenario | Action |
-|---|---|
-| Both tools missing | Tell the user what to install and stop — don't attempt a degraded council |
-| One tool missing | Report which tool is missing. A 2-model debate loses the tiebreaker benefit — ask the user if they want to proceed or install the missing tool first |
-| Auth failure at runtime | Report the error to the user. Continue with the remaining models. A 2-model debate is better than nothing |
-| Rate limit or sandbox error at runtime | Report the error. Continue with the remaining models |
-
-**Do not silently proceed with a degraded council.** Always tell the user which tool is unavailable and why. The tiebreaker value of a 3-model council is significant for close decisions.
-
-## Runtime Timeout Configuration
-
-Set timeouts per round type:
-
-- **Round 1 (Independent Research)**: 300s (5 minutes) — models are reading files and searching code
-- **Rebuttal rounds (2-5)**: 180s — less exploration, more focused follow-up
-
-If one model times out in any round, report it and continue with the other two.
-
-## Working Directory
-
-Make sure both CLI tools run from the same working directory as the current session. This ensures all models look at the same codebase.
-
-Pass `cd {cwd} &&` before CLI commands if needed:
-
-```bash
-cd /path/to/project && codex exec --full-auto "..."
-cd /path/to/project && gemini -p "..." --yolo
-```
+# Prerequisites: Tool Availability Checks
+
+## Required CLI Tools
+
+The council requires both external CLI tools to be installed and authenticated:
+
+- **Codex**: `npm install -g @openai/codex` (authenticated via `codex login`)
+- **Gemini**: `npm install -g @google/gemini-cli` (authenticated via Google)
+
+## Availability Check
+
+Before the first round, verify both tools are available:
+
+```bash
+which codex && which gemini
+```
+
+## Fallback Logic
+
+| Scenario | Action |
+|---|---|
+| Both tools missing | Tell the user what to install and stop — don't attempt a degraded council |
+| One tool missing | Report which tool is missing. A 2-model debate loses the tiebreaker benefit — ask the user if they want to proceed or install the missing tool first |
+| Auth failure at runtime | Report the error to the user. Continue with the remaining models. A 2-model debate is better than nothing |
+| Rate limit or sandbox error at runtime | Report the error. Continue with the remaining models |
+
+**Do not silently proceed with a degraded council.** Always tell the user which tool is unavailable and why. The tiebreaker value of a 3-model council is significant for close decisions.
+
+## Runtime Timeout Configuration
+
+Set timeouts per round type:
+
+- **Round 1 (Independent Research)**: 300s (5 minutes) — models are reading files and searching code
+- **Rebuttal rounds (2-5)**: 180s — less exploration, more focused follow-up
+
+If one model times out in any round, report it and continue with the other two.
+
+## Working Directory
+
+Make sure both CLI tools run from the same working directory as the current session. This ensures all models look at the same codebase.
+
+Pass `cd {cwd} &&` before CLI commands if needed:
+
+```bash
+cd /path/to/project && codex exec --full-auto "..."
+cd /path/to/project && gemini -p "..." --yolo
+```