feed-the-machine 1.6.1 → 1.7.1

package/ftm-council/references/protocols/STEP-0-FRAMING.md

@@ -1,46 +1,46 @@
-# Step 0: Frame the Problem
-
-> **Note:** This step is skipped in auto-invocation mode. If a structured conflict payload was provided, proceed directly to Step 1 using the payload as the council prompt.
-
-Take the user's request and distill it into a clear **council prompt** — a self-contained problem statement that makes sense without conversation history. The prompt should describe the problem and what a good answer looks like, but it should NOT include pre-read code. The models will read the code themselves.
-
-## What to Include
-
-- The specific question or decision to be made
-- File paths or areas of the codebase to start investigating (as pointers, not content)
-- Error messages or symptoms if it's a debugging problem
-- Decision criteria — what a good answer looks like
-- Any constraints the user has mentioned
-
-## What to Exclude
-
-- Pre-read file contents (each model reads files itself)
-- Your own analysis or opinion about the problem
-- Summaries of what the code does (let each model discover that)
-
-## Confirmation Gate
-
-Show the user the framed prompt before proceeding: "Here's what I'll send to the council — does this capture the problem?" Wait for confirmation or edits.
-
-## Structured Payload Format
-
-When creating the council prompt, use this structure:
-
-```
-PROBLEM:
-[Clear statement of the question or decision]
-
-CODEBASE ENTRY POINTS:
-[File paths or directories to investigate — no content, just paths]
-
-SYMPTOMS / ERROR MESSAGES:
-[If debugging: exact error text, stack traces, reproduction steps]
-
-DECISION CRITERIA:
-[What a good answer looks like — what tradeoffs matter here]
-
-CONSTRAINTS:
-[Any hard requirements, technology restrictions, or non-negotiables]
-```
-
-The prompt must be fully self-contained. A model dropped into a fresh session with only this prompt should know exactly what to investigate and what success looks like.
+# Step 0: Frame the Problem
+
+> **Note:** This step is skipped in auto-invocation mode. If a structured conflict payload was provided, proceed directly to Step 1 using the payload as the council prompt.
+
+Take the user's request and distill it into a clear **council prompt** — a self-contained problem statement that makes sense without conversation history. The prompt should describe the problem and what a good answer looks like, but it should NOT include pre-read code. The models will read the code themselves.
+
+## What to Include
+
+- The specific question or decision to be made
+- File paths or areas of the codebase to start investigating (as pointers, not content)
+- Error messages or symptoms if it's a debugging problem
+- Decision criteria — what a good answer looks like
+- Any constraints the user has mentioned
+
+## What to Exclude
+
+- Pre-read file contents (each model reads files itself)
+- Your own analysis or opinion about the problem
+- Summaries of what the code does (let each model discover that)
+
+## Confirmation Gate
+
+Show the user the framed prompt before proceeding: "Here's what I'll send to the council — does this capture the problem?" Wait for confirmation or edits.
+
+## Structured Payload Format
+
+When creating the council prompt, use this structure:
+
+```
+PROBLEM:
+[Clear statement of the question or decision]
+
+CODEBASE ENTRY POINTS:
+[File paths or directories to investigate — no content, just paths]
+
+SYMPTOMS / ERROR MESSAGES:
+[If debugging: exact error text, stack traces, reproduction steps]
+
+DECISION CRITERIA:
+[What a good answer looks like — what tradeoffs matter here]
+
+CONSTRAINTS:
+[Any hard requirements, technology restrictions, or non-negotiables]
+```
+
+The prompt must be fully self-contained. A model dropped into a fresh session with only this prompt should know exactly what to investigate and what success looks like.

package/ftm-council-chat.yml

@@ -0,0 +1,2 @@
+name: ftm-council-chat
+description: AIM-styled browser chatroom where Claude, Codex, and Gemini hold real-time conversations with the user as a full participant. Use when user says "chatroom", "aim chat", "council chat", "live debate", "open the chatroom", or "council-chat".

package/ftm-council.yml

@@ -1,2 +1,2 @@
-name: ftm-council
-description: Multi-AI deliberation council that sends problems to Claude, Codex, and Gemini as equal peers, then loops through rounds of debate until 2-of-3 agree on a decision. Use when the user wants a second (and third) opinion, says "council this", "get other opinions", "what would other AIs think", "debate this", "multi-model", "ftm-council", or wants to cross-check a decision, architecture choice, debugging approach, or any problem where diverse AI perspectives would reduce blind spots. Especially valuable for debugging hard problems, architecture decisions, code review, and any situation where confirmation bias from a single model is a risk. Even if the user just says "I'm not sure about this approach" or "sanity check this", consider invoking the council.
+name: ftm-council
+description: Multi-AI deliberation council that sends problems to Claude, Codex, and Gemini as equal peers, then loops through rounds of debate until 2-of-3 agree on a decision. Use when the user wants a second (and third) opinion, says "council this", "get other opinions", "what would other AIs think", "debate this", "multi-model", "ftm-council", or wants to cross-check a decision, architecture choice, debugging approach, or any problem where diverse AI perspectives would reduce blind spots. Especially valuable for debugging hard problems, architecture decisions, code review, and any situation where confirmation bias from a single model is a risk. Even if the user just says "I'm not sure about this approach" or "sanity check this", consider invoking the council.

package/ftm-dashboard/SKILL.md

@@ -1,163 +1,163 @@
----
-name: ftm-dashboard
-description: Session and weekly analytics dashboard for the FTM skill ecosystem. Reads events.log and blackboard state to show skills invoked, plans presented, approval rates, experiences recorded, and patterns promoted. Use when user says "dashboard", "analytics", "stats", "ftm-dashboard", "show session stats", or "how's the system doing".
----
-
-# FTM Dashboard
-
-Provides analytics about FTM system usage by reading the event log and blackboard state.
-
-## Commands
-
-### `/ftm-dashboard` (default: current session)
-
-Shows stats for the current session:
-
-```
-━━━━━━━━━━━ FTM Session Dashboard ━━━━━━━━━━━
-
-Session started: [timestamp]
-Duration: [hours:minutes]
-
-Skills Invoked:
-  ftm-mind      ████████████  12
-  ftm-debug     ████          4
-  ftm-executor  ██            2
-  ftm-brainstorm █            1
-
-Plans:
-  Presented: 5
-  Approved: 4 (80%)
-  Modified before approval: 2
-  Saved as playbook: 1
-
-Experiences Recorded:
-  Total: 8
-  From LLM: 5 (rich)
-  From git hook: 3 (minimal)
-
-Patterns:
-  Active: 12
-  Reinforced this session: 3
-  Aging (>30 days): 2
-  Decayed: 0
-
-Context Budget:
-  Orient mode: Full (conversation ~25% used)
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-### `/ftm-dashboard week`
-
-Shows aggregate stats for the past 7 days:
-
-```
-━━━━━━━━━━ FTM Weekly Dashboard ━━━━━━━━━━━━━
-
-Period: [date] — [date]
-
-Tasks by Complexity:
-  Micro:  ██████████████████  18
-  Small:  ████████████        12
-  Medium: ██████              6
-  Large:  ██                  2
-
-Top Skills:
-  1. ftm-mind (45 invocations)
-  2. ftm-executor (12 invocations)
-  3. ftm-debug (8 invocations)
-  4. ftm-brainstorm (6 invocations)
-  5. ftm-audit (4 invocations)
-
-Playbooks:
-  Created: 2
-  Reused: 3
-  Parameterized: 0
-
-Learning:
-  Experiences recorded: 38
-  Patterns promoted: 1
-  Patterns decayed: 0
-  Sizing corrections: 0
-
-Approval Rate: 85% (34/40 plans approved on first presentation)
-Average plan modifications: 1.2 per plan
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-## Data Sources
-
-### events.log (`~/.claude/ftm-state/events.log`)
-- JSONL format, one entry per line
-- Each entry has: timestamp, event_type, tool_name, session_id, skill_context
-- Filter by session_id for current session, by date range for weekly
-
-### Blackboard State
-- `~/.claude/ftm-state/blackboard/context.json` — current session metadata
-- `~/.claude/ftm-state/blackboard/experiences/index.json` — experience counts and types
-- `~/.claude/ftm-state/blackboard/patterns.json` — pattern health
-
-### Playbooks (`~/.ftm/playbooks/`)
-- Count `.yml` files for total playbooks
-- Check `use_count` field for reuse stats
-- Check `parameterized` field for parameterization stats
-
-## Implementation
-
-1. Read the relevant data sources
-2. Compute aggregates
-3. Render as markdown tables with ASCII bar charts
-4. Output directly — no approval gates needed (read-only operation)
-
-## Rendering
-
-- Use Unicode block characters for bar charts: █ ▓ ░
-- Tables in markdown format for terminal rendering
-- Keep output concise — one screen max
-- If data sources are empty (fresh install), show: "No data yet. Use FTM for a few sessions and check back."
-
-## Events
-
-### Listens To
-- `task_completed` — for session stats tracking
-
-### Blackboard Read
-- `context.json` — session metadata
-- `experiences/index.json` — experience inventory
-- `patterns.json` — pattern health
-
-## Requirements
-
-- reference: `~/.claude/ftm-state/events.log` | optional | JSONL event log for skill invocation tracking
-- reference: `~/.claude/ftm-state/blackboard/context.json` | required | current session metadata
-- reference: `~/.claude/ftm-state/blackboard/experiences/index.json` | optional | experience inventory and counts
-- reference: `~/.claude/ftm-state/blackboard/patterns.json` | optional | pattern health for weekly stats
-- reference: `~/.ftm/playbooks/` | optional | playbook use counts and stats
-
-## Risk
-
-- level: read_only
-- scope: reads event log and blackboard state only; does not modify any files
-- rollback: no mutations to reverse
-
-## Approval Gates
-
-- complexity_routing: micro → auto | small → auto | medium → auto | large → auto | xl → auto
-
-## Fallbacks
-
-- condition: events.log missing or empty | action: show "No session events recorded yet" for relevant sections
-- condition: blackboard context.json missing | action: show "No session data available" and suggest using FTM skills first
-- condition: experiences/index.json missing | action: skip experience stats sections
-- condition: playbooks directory missing | action: show 0 for all playbook stats
-
-## Capabilities
-
-- env: none required
-
-## Event Payloads
-
-### (none)
-ftm-dashboard is read-only and does not emit events directly. It listens to task_completed for session tracking only.
+---
+name: ftm-dashboard
+description: Session and weekly analytics dashboard for the FTM skill ecosystem. Reads events.log and blackboard state to show skills invoked, plans presented, approval rates, experiences recorded, and patterns promoted. Use when user says "dashboard", "analytics", "stats", "ftm-dashboard", "show session stats", or "how's the system doing".
+---
+
+# FTM Dashboard
+
+Provides analytics about FTM system usage by reading the event log and blackboard state.
+
+## Commands
+
+### `/ftm-dashboard` (default: current session)
+
+Shows stats for the current session:
+
+```
+━━━━━━━━━━━ FTM Session Dashboard ━━━━━━━━━━━
+
+Session started: [timestamp]
+Duration: [hours:minutes]
+
+Skills Invoked:
+  ftm-mind      ████████████  12
+  ftm-debug     ████          4
+  ftm-executor  ██            2
+  ftm-brainstorm █            1
+
+Plans:
+  Presented: 5
+  Approved: 4 (80%)
+  Modified before approval: 2
+  Saved as playbook: 1
+
+Experiences Recorded:
+  Total: 8
+  From LLM: 5 (rich)
+  From git hook: 3 (minimal)
+
+Patterns:
+  Active: 12
+  Reinforced this session: 3
+  Aging (>30 days): 2
+  Decayed: 0
+
+Context Budget:
+  Orient mode: Full (conversation ~25% used)
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+### `/ftm-dashboard week`
+
+Shows aggregate stats for the past 7 days:
+
+```
+━━━━━━━━━━ FTM Weekly Dashboard ━━━━━━━━━━━━━
+
+Period: [date] — [date]
+
+Tasks by Complexity:
+  Micro:  ██████████████████  18
+  Small:  ████████████        12
+  Medium: ██████              6
+  Large:  ██                  2
+
+Top Skills:
+  1. ftm-mind (45 invocations)
+  2. ftm-executor (12 invocations)
+  3. ftm-debug (8 invocations)
+  4. ftm-brainstorm (6 invocations)
+  5. ftm-audit (4 invocations)
+
+Playbooks:
+  Created: 2
+  Reused: 3
+  Parameterized: 0
+
+Learning:
+  Experiences recorded: 38
+  Patterns promoted: 1
+  Patterns decayed: 0
+  Sizing corrections: 0
+
+Approval Rate: 85% (34/40 plans approved on first presentation)
+Average plan modifications: 1.2 per plan
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+## Data Sources
+
+### events.log (`~/.claude/ftm-state/events.log`)
+- JSONL format, one entry per line
+- Each entry has: timestamp, event_type, tool_name, session_id, skill_context
+- Filter by session_id for current session, by date range for weekly
+
+### Blackboard State
+- `~/.claude/ftm-state/blackboard/context.json` — current session metadata
+- `~/.claude/ftm-state/blackboard/experiences/index.json` — experience counts and types
+- `~/.claude/ftm-state/blackboard/patterns.json` — pattern health
+
+### Playbooks (`~/.ftm/playbooks/`)
+- Count `.yml` files for total playbooks
+- Check `use_count` field for reuse stats
+- Check `parameterized` field for parameterization stats
+
+## Implementation
+
+1. Read the relevant data sources
+2. Compute aggregates
+3. Render as markdown tables with ASCII bar charts
+4. Output directly — no approval gates needed (read-only operation)
+
+## Rendering
+
+- Use Unicode block characters for bar charts: █ ▓ ░
+- Tables in markdown format for terminal rendering
+- Keep output concise — one screen max
+- If data sources are empty (fresh install), show: "No data yet. Use FTM for a few sessions and check back."
+
+## Events
+
+### Listens To
+- `task_completed` — for session stats tracking
+
+### Blackboard Read
+- `context.json` — session metadata
+- `experiences/index.json` — experience inventory
+- `patterns.json` — pattern health
+
+## Requirements
+
+- reference: `~/.claude/ftm-state/events.log` | optional | JSONL event log for skill invocation tracking
+- reference: `~/.claude/ftm-state/blackboard/context.json` | required | current session metadata
+- reference: `~/.claude/ftm-state/blackboard/experiences/index.json` | optional | experience inventory and counts
+- reference: `~/.claude/ftm-state/blackboard/patterns.json` | optional | pattern health for weekly stats
+- reference: `~/.ftm/playbooks/` | optional | playbook use counts and stats
+
+## Risk
+
+- level: read_only
+- scope: reads event log and blackboard state only; does not modify any files
+- rollback: no mutations to reverse
+
+## Approval Gates
+
+- complexity_routing: micro → auto | small → auto | medium → auto | large → auto | xl → auto
+
+## Fallbacks
+
+- condition: events.log missing or empty | action: show "No session events recorded yet" for relevant sections
+- condition: blackboard context.json missing | action: show "No session data available" and suggest using FTM skills first
+- condition: experiences/index.json missing | action: skip experience stats sections
+- condition: playbooks directory missing | action: show 0 for all playbook stats
+
+## Capabilities
+
+- env: none required
+
+## Event Payloads
+
+### (none)
+ftm-dashboard is read-only and does not emit events directly. It listens to task_completed for session tracking only.

package/ftm-dashboard.yml

@@ -1,4 +1,4 @@
----
-name: ftm-dashboard
-description: Session and weekly analytics dashboard for the FTM skill ecosystem. Reads events.log and blackboard state to show skills invoked, plans presented, approval rates, experiences recorded, and patterns promoted. Use when user says "dashboard", "analytics", "stats", "ftm-dashboard", "show session stats", or "how's the system doing".
----
+---
+name: ftm-dashboard
+description: Session and weekly analytics dashboard for the FTM skill ecosystem. Reads events.log and blackboard state to show skills invoked, plans presented, approval rates, experiences recorded, and patterns promoted. Use when user says "dashboard", "analytics", "stats", "ftm-dashboard", "show session stats", or "how's the system doing".
+---