aether-colony 5.3.1 → 5.3.3

package/.aether/commands/claude/council.md

@@ -1,507 +0,0 @@
-<!-- Generated from .aether/commands/council.yaml - DO NOT EDIT DIRECTLY -->
----
-name: ant:council
-description: "📜🐜🏛️🐜📜 Convene council for intent clarification via multi-choice questions"
----
-
-You are the **Queen Ant Colony**. Convene the council to clarify user intent and inject guidance as pheromones.
-
-## Instructions
-
-Parse `$ARGUMENTS`:
-- If starts with `--deliberate`: set `deliberate_mode = true`, extract proposal text after `--deliberate`
-- If contains `--no-visual`: set `visual_mode = false` (visual is ON by default)
-- Otherwise: set `visual_mode = true`
-
-**If `deliberate_mode` is true:** Skip to [Deliberation Mode](#deliberation-mode) and stop after it.
-
----
-
-## Deliberation Mode
-
-When `--deliberate "<proposal>"` is passed, run a structured Advocate/Challenger/Sage deliberation.
-
-### Step D1: Check Budget
-
-Run using the Bash tool with description "Checking deliberation budget...":
-```bash
-bash .aether/aether-utils.sh council-budget-check
-```
-
-Parse result. If `allowed` is `false`:
-```
-📜🐜🏛️🐜📜 COUNCIL — BUDGET EXHAUSTED
-
-Spawn budget is fully allocated. Complete or close existing deliberations before starting new ones.
-Run /ant:council to review existing deliberations.
-```
-Stop here.
-
-### Step D2: Open Deliberation
-
-Run using the Bash tool with description "Opening deliberation...":
-```bash
-bash .aether/aether-utils.sh council-deliberate --proposal "<proposal>"
-```
-
-Capture `deliberation_id` from `result.id`.
-
-Display:
-```
-📜🐜🏛️🐜📜 COUNCIL DELIBERATION OPENED
-
-Proposal: "<proposal>"
-ID: {deliberation_id}
-Budget: {budget} spawns available
-
-Convening Advocate, Challenger, and Sage...
-```
-
-### Step D3: Spawn Advocate Scout
-
-Spawn an Advocate scout to argue **in favor** of the proposal.
-
-
-Use the Task tool to spawn a scout with the following system prompt:
-```
-You are the Advocate on the Ant Colony council.
-Your role is to argue STRONGLY IN FAVOR of the proposal.
-Present the strongest possible case for why this proposal should be adopted.
-Be specific. Focus on concrete benefits and outcomes.
-Keep your argument under 200 words.
-Reply with ONLY your argument text — no preamble or meta-commentary.
-```
-
-And user message:
-```
-Proposal: "<proposal>"
-
-Present your strongest argument in favor of this proposal.
-```
-
-Capture the advocate's argument as `advocate_argument`.
-
-
-Record the argument:
-```bash
-bash .aether/aether-utils.sh council-advocate \
-  --deliberation-id "<deliberation_id>" \
-  --argument "<advocate_argument>"
-```
-
-Display:
-```
-⚖️  ADVOCATE:
-{advocate_argument}
-```
-
-### Step D4: Spawn Challenger Scout
-
-Spawn a Challenger scout to argue **against** the proposal.
-
-
-Use the Task tool to spawn a scout with the following system prompt:
-```
-You are the Challenger on the Ant Colony council.
-Your role is to argue STRONGLY AGAINST the proposal.
-Present the strongest possible case for why this proposal should be rejected or deferred.
-Be specific. Focus on concrete risks, costs, and downsides.
-Keep your argument under 200 words.
-Reply with ONLY your argument text — no preamble or meta-commentary.
-```
-
-And user message:
-```
-Proposal: "<proposal>"
-
-Present your strongest argument against this proposal.
-```
-
-Capture the challenger's argument as `challenger_argument`.
-
-
-Record the argument:
-```bash
-bash .aether/aether-utils.sh council-challenger \
-  --deliberation-id "<deliberation_id>" \
-  --argument "<challenger_argument>"
-```
-
-Display:
-```
-⚔️  CHALLENGER:
-{challenger_argument}
-```
-
-### Step D5: Spawn Sage Scout
-
-Spawn a Sage scout to synthesize both positions and provide a recommendation.
-
-
-Use the Task tool to spawn a scout with the following system prompt:
-```
-You are the Sage on the Ant Colony council.
-You have heard both the Advocate and Challenger arguments.
-Your role is to synthesize both positions into balanced wisdom and provide a clear recommendation.
-Your recommendation must be one of: adopt, reject, defer, or adopt-with-conditions.
-Keep your synthesis under 150 words.
-Reply with JSON only:
-{"synthesis": "<your balanced synthesis>", "recommendation": "adopt|reject|defer|adopt-with-conditions"}
-```
-
-And user message:
-```
-Proposal: "<proposal>"
-
-Advocate argued: "<advocate_argument>"
-
-Challenger argued: "<challenger_argument>"
-
-Synthesize both positions and provide your recommendation.
-```
-
-Parse the JSON response. Capture `synthesis` and `recommendation`.
-
-
-Record the sage synthesis:
-```bash
-bash .aether/aether-utils.sh council-sage \
-  --deliberation-id "<deliberation_id>" \
-  --synthesis "<synthesis>" \
-  --recommendation "<recommendation>"
-```
-
-### Step D6: Display Result
-
-```
-📜🐜🏛️🐜📜 COUNCIL DELIBERATION COMPLETE
-
-Proposal: "<proposal>"
-
-⚖️  Advocate:
-{advocate_argument}
-
-⚔️  Challenger:
-{challenger_argument}
-
-🧙 Sage Synthesis:
-{synthesis}
-
-Recommendation: {recommendation}
-```
-
-If recommendation is `adopt` or `adopt-with-conditions`:
-```
-✅ Council recommends proceeding.
-   Run /ant:focus "<proposal summary>" to inject guidance for the colony.
-```
-
-If recommendation is `reject`:
-```
-❌ Council recommends against this proposal.
-   Run /ant:redirect "<proposal summary>" if you want to make this a hard constraint.
-```
-
-If recommendation is `defer`:
-```
-⏸️  Council recommends deferring this decision.
-   Return when more context is available.
-```
-
----
-
-
-
-### Step 0: Initialize Visual Mode (if enabled)
-
-If `visual_mode` is true, run using the Bash tool with description "Initializing council display...":
-
-### Step 1: Read Current State
-
-Read `.aether/data/COLONY_STATE.json`.
-
-If file doesn't exist or `goal` is null:
-```
-📜🐜🏛️🐜📜 COUNCIL
-
-No colony initialized. Run /ant:init first.
-```
-Stop here.
-
-If `milestone` == `"Crowned Anthill"`:
-```
-This colony has been sealed. Start a new colony with /ant:init "new goal".
-```
-Stop here.
-
-Capture the current state for context:
-- `prior_state` = state field value (READY, EXECUTING, PLANNING, etc.)
-- `current_phase` = current_phase field value
-- `goal` = goal field value
-
-### Step 2: Display Council Header
-
-
-```
-📜🐜🏛️🐜📜 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-             A N T   C O U N C I L
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📜🐜🏛️🐜📜
-
-
-
-👑 Queen convenes the council for guidance
-
-   Colony Goal: "{goal}"
-   Current State: {prior_state}
-   Phase: {current_phase}
-```
-
-If `prior_state` is `EXECUTING`:
-```
-⚡ Note: Build in progress. New guidance will apply to future work.
-   Current workers continue with existing constraints.
-```
-
-### Step 3: Present Category Menu
-
-Use the **AskUserQuestion** tool to ask:
-
-```
-question: "What would you like to clarify with the council?"
-header: "Topic"
-options:
-  - label: "Project Direction"
-    description: "Clarify project type, architecture, or tech stack choices"
-  - label: "Quality Priorities"
-    description: "Define tradeoffs: speed vs robustness vs simplicity"
-  - label: "Constraints & Boundaries"
-    description: "Set rules about what to avoid or require"
-  - label: "Custom Topic"
-    description: "Describe something specific you want to discuss"
-multiSelect: false
-```
-
-Wait for user response.
-
-### Step 4: Drill Down Based on Selection
-
-Based on the user's selection, ask follow-up questions:
-
-**If "Project Direction":**
-```
-question: "What aspect of project direction needs clarification?"
-header: "Direction"
-options:
-  - label: "Architecture Pattern"
-    description: "Monolith vs microservices, MVC vs functional, etc."
-  - label: "Tech Stack"
-    description: "Framework, database, or library choices"
-  - label: "Code Style"
-    description: "Naming conventions, file organization, patterns"
-  - label: "Testing Approach"
-    description: "TDD, integration-first, coverage requirements"
-multiSelect: true
-```
-
-**If "Quality Priorities":**
-```
-question: "What's most important for this project?"
-header: "Priority"
-options:
-  - label: "Speed of Development"
-    description: "Get it working fast, iterate later"
-  - label: "Robustness"
-    description: "Handle edge cases, thorough error handling"
-  - label: "Simplicity"
-    description: "Minimal code, easy to understand and maintain"
-  - label: "Performance"
-    description: "Optimize for speed and efficiency"
-multiSelect: true
-```
-
-**If "Constraints & Boundaries":**
-```
-question: "What constraints should the colony follow?"
-header: "Constraints"
-options:
-  - label: "Security Requirements"
-    description: "Auth patterns, data handling, secrets management"
-  - label: "Compatibility"
-    description: "Browser support, Node version, API compatibility"
-  - label: "Dependencies"
-    description: "Prefer/avoid certain libraries or frameworks"
-  - label: "Patterns to Avoid"
-    description: "Anti-patterns, deprecated approaches"
-multiSelect: true
-```
-
-**If "Custom Topic":**
-```
-question: "Describe what you want to clarify:"
-header: "Custom"
-options:
-  - label: "Type your topic below"
-    description: "Use the 'Other' option to enter your specific topic"
-multiSelect: false
-```
-
-Wait for user response. Based on answers, ask 1-2 more specific follow-up questions to get actionable guidance.
-
-### Step 5: Translate Answers to Pheromones
-
-Based on all gathered answers, determine which pheromones to inject:
-
-**FOCUS signals** (areas to emphasize):
-- Architecture choices → FOCUS on that pattern
-- Quality priorities → FOCUS on that approach
-- Specific requirements → FOCUS on those areas
-
-**REDIRECT signals** (patterns to avoid):
-- Patterns to avoid → REDIRECT away
-- Incompatible approaches → REDIRECT away
-- Security concerns → REDIRECT away from risky patterns
-
-**FEEDBACK signals** (guidance to remember):
-- Style preferences → FEEDBACK as instinct
-- General guidance → FEEDBACK for colony memory
-
-### Step 6: Inject Pheromones
-
-Read `.aether/data/constraints.json`. Create if doesn't exist:
-```json
-{"version": "1.0", "focus": [], "constraints": []}
-```
-
-**For each FOCUS area identified:**
-- Check for duplicates (case-insensitive match in existing focus array)
-- If not duplicate, append to `focus` array
-- Keep max 5 entries (remove oldest if exceeded)
-
-**For each REDIRECT pattern identified:**
-- Generate ID: `c_<unix_timestamp_ms>`
-- Append to `constraints` array:
-```json
-{
-  "id": "<generated_id>",
-  "type": "AVOID",
-  "content": "<pattern to avoid>",
-  "source": "council:redirect",
-  "created_at": "<ISO-8601 timestamp>"
-}
-```
-- Keep max 10 constraints (remove oldest if exceeded)
-
-Write constraints.json.
-
-**For each FEEDBACK identified:**
-Read `.aether/data/COLONY_STATE.json`.
-
-Append to `signals` array:
-```json
-{
-  "id": "feedback_<timestamp_ms>",
-  "type": "FEEDBACK",
-  "content": "<feedback message>",
-  "priority": "low",
-  "source": "council:feedback",
-  "created_at": "<ISO-8601>",
-  "expires_at": "phase_end"
-}
-```
-
-Create instinct in `memory.instincts`:
-```json
-{
-  "id": "instinct_<timestamp>",
-  "trigger": "<inferred from context>",
-  "action": "<the guidance>",
-  "confidence": 0.7,
-  "domain": "<inferred: testing|architecture|code-style|debugging|workflow>",
-  "source": "council:feedback",
-  "evidence": ["Council session guidance"],
-  "created_at": "<ISO-8601>",
-  "last_applied": null,
-  "applications": 0,
-  "successes": 0
-}
-```
-
-Keep max 30 instincts (remove lowest confidence if exceeded).
-
-Write COLONY_STATE.json.
-
-### Step 7: Log Council Event
-
-Append to COLONY_STATE.json `events` array:
-```
-<ISO-8601>|council_session|council|Council convened: <brief summary of topics discussed>
-```
-
-Keep max 100 events.
-
-### Step 8: Display Summary
-
-```
-📜🐜🏛️🐜📜 COUNCIL ADJOURNED
-
-Pheromones Injected:
-```
-
-For each FOCUS added:
-```
-  🎯 FOCUS: "{content}"
-```
-
-For each REDIRECT added:
-```
-  🚫 REDIRECT: "{content}"
-```
-
-For each FEEDBACK added:
-```
-  💬 FEEDBACK: "{content}"
-     🧠 Instinct: [{confidence}] {domain}: {action summary}
-```
-
-If no pheromones were injected:
-```
-  (No new constraints needed based on discussion)
-```
-
-Then:
-```
-🐜 Colony guidance updated. Resuming {prior_state} state.
-```
-
-If `prior_state` was EXECUTING:
-```
-⚡ Active workers will complete with prior constraints.
-   New spawns will use updated guidance.
-
-   /ant:status    📊 View current progress
-   /ant:continue  ⏭️  Check for phase completion
-```
-
-If `prior_state` was READY:
-```
-   /ant:plan     📋 Generate or refine plan
-   /ant:build    🔨 Start building a phase
-   /ant:status   📊 View colony status
-```
-
-If `prior_state` was PLANNING:
-```
-   Planning will continue with new guidance.
-```
-
-
-### Step 9: Next Up
-
-Generate the state-based Next Up block by running using the Bash tool with description "Generating Next Up suggestions...":
-```bash
-state=$(jq -r '.state // "IDLE"' .aether/data/COLONY_STATE.json)
-current_phase=$(jq -r '.current_phase // 0' .aether/data/COLONY_STATE.json)
-total_phases=$(jq -r '.plan.phases | length' .aether/data/COLONY_STATE.json)
-bash .aether/aether-utils.sh print-next-up "$state" "$current_phase" "$total_phases"
-```
-

package/.aether/commands/claude/data-clean.md

@@ -1,81 +0,0 @@
-<!-- Generated from .aether/commands/data-clean.yaml - DO NOT EDIT DIRECTLY -->
----
-name: ant:data-clean
-description: "Scan and remove test artifacts from colony data files"
----
-
-You are the **Queen Ant Colony**. Run the data cleaner to scan for and remove test/synthetic artifacts from colony data files.
-
-
-> **Note:** `$ARGUMENTS` is unused. This command always scans all data files.
-
-
-
-## Instructions
-
-### Step 1: Scan
-
-Run using the Bash tool with description "Scanning colony data for test artifacts...":
-```bash
-bash .aether/aether-utils.sh data-clean --dry-run
-```
-
-Display the output to the user. This shows artifact counts per data file without modifying anything.
-
-### Step 2: Decision Gate
-
-Parse the scan output for "Total artifacts: N".
-
-**If total is 0:**
-Display:
-```
-Colony data is clean. No artifacts found.
-```
-Skip to Step 5.
-
-**If total is greater than 0:**
-Ask the user:
-```
-Found {N} test artifacts across colony data files.
-Remove these artifacts? (yes/no)
-```
-
-If user says no, display "No changes made." and skip to Step 5.
-
-### Step 3: Clean
-
-If user confirmed, run using the Bash tool with description "Removing test artifacts...":
-```bash
-bash .aether/aether-utils.sh data-clean --confirm
-```
-
-### Step 4: Summary
-
-Display the cleanup results showing what was removed from each file.
-
-For example:
-```
-Data Clean Complete
-===================
-Removed {total} artifacts:
-  - pheromones.json: {N} test signals
-  - QUEEN.md: {N} test entries
-  - learning-observations.json: {N} test observations
-  - midden.json: {N} test entries
-  - spawn-tree.txt: {N} test worker lines
-  - constraints.json: {N} test focus entries
-
-Run /ant:status to verify colony state.
-```
-
-
-### Step 5: Next Up
-
-Generate the state-based Next Up block by running using the Bash tool with description "Generating Next Up suggestions...":
-```bash
-state=$(jq -r '.state // "IDLE"' .aether/data/COLONY_STATE.json)
-current_phase=$(jq -r '.current_phase // 0' .aether/data/COLONY_STATE.json)
-total_phases=$(jq -r '.plan.phases | length' .aether/data/COLONY_STATE.json)
-bash .aether/aether-utils.sh print-next-up "$state" "$current_phase" "$total_phases"
-```
-