aether-colony 3.1.17 → 5.0.0

package/.opencode/commands/ant/continue.md

@@ -95,7 +95,7 @@ If `state != "EXECUTING"`:
 
 **The Iron Law:** No phase advancement without fresh verification evidence.
 
-Before ANY phase can advance, execute the 6-phase verification loop. See `.aether/verification-loop.md` for full reference.
+Before ANY phase can advance, execute the 6-phase verification loop. See `.aether/docs/disciplines/verification-loop.md` for full reference.
 
 #### 1. Command Resolution (Priority Chain)
 
@@ -125,8 +125,10 @@ If no build system detected, skip build/test/type/lint checks but still verify s
 Execute all applicable phases and capture output:
 
 ```
-Phase {id} Verification Loop
-============================
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+👁️🐜 V E R I F I C A T I O N   L O O P
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Phase {id} — Checking colony work...
 ```
 
 **Phase 1: Build Check** (if command exists):
@@ -184,23 +186,28 @@ For EACH criterion:
 
 Display:
 ```
-VERIFICATION LOOP REPORT
-========================
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+👁️🐜 V E R I F I C A T I O N   R E P O R T
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Phase 1: Build      [PASS/FAIL]
-Phase 2: Types      [PASS/FAIL] (X errors)
-Phase 3: Lint       [PASS/FAIL] (X warnings)
-Phase 4: Tests      [PASS/FAIL] (X/Y passed)
-         Coverage   {percent}% (target: 80%)
-Phase 5: Security   [PASS/FAIL] (X issues)
-Phase 6: Diff       [X files changed]
+🔨 Build        [PASS/FAIL/SKIP]
+🔍 Types        [PASS/FAIL/SKIP] (X errors)
+🧹 Lint         [PASS/FAIL/SKIP] (X warnings)
+🧪 Tests        [PASS/FAIL/SKIP] (X/Y passed)
+   Coverage     {percent}% (target: 80%)
+🔒 Security     [PASS/FAIL] (X issues)
+📋 Diff         [X files changed]
 
-Success Criteria:
+──────────────────────────────────────────────────
+🐜 Success Criteria
+──────────────────────────────────────────────────
   ✅ {criterion 1}: {specific evidence}
   ✅ {criterion 2}: {specific evidence}
   ❌ {criterion 3}: {what's missing}
 
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Overall: READY / NOT READY
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
 #### 3. Gate Decision
@@ -208,14 +215,16 @@ Overall: READY / NOT READY
 **If NOT READY (any of: build fails, tests fail, critical security issues, success criteria unmet):**
 
 ```
-⛔ VERIFICATION FAILED - PHASE BLOCKED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⛔🐜 V E R I F I C A T I O N   F A I L E D
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Phase {id} cannot advance until issues are resolved.
 
-Issues Found:
+🚨 Issues Found:
 {list each failure with specific evidence}
 
-Required Actions:
+🔧 Required Actions:
   1. Fix the issues listed above
   2. Run /ant:continue again to re-verify
 
@@ -232,12 +241,12 @@ Use AskUserQuestion to confirm they understand what needs to be fixed:
 **If READY (all checks pass with evidence):**
 
 ```
-✅ VERIFICATION PASSED
+✅🐜 VERIFICATION PASSED
 
 All checks completed with evidence:
 {list each check and its evidence}
 
-Proceeding to phase advancement.
+Proceeding to gate checks...
 ```
 
 Continue to Step 1.6.
@@ -260,17 +269,19 @@ grep -c "watcher" .aether/data/spawn-tree.txt 2>/dev/null || echo "0"
 **HARD REJECTION - If spawn_count == 0 and phase had 3+ tasks:**
 
 ```
-⛔ SPAWN GATE FAILED - PHASE BLOCKED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⛔🐜 S P A W N   G A T E   F A I L E D
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 This phase had {task_count} tasks but spawn_count: 0
 The Prime Worker violated the spawn protocol.
 
-The colony metaphor requires actual parallelism:
+🐜 The colony requires actual parallelism:
   - Prime Worker MUST spawn specialists for non-trivial work
   - A single agent doing everything is NOT a colony
   - "Justifications" for not spawning are not accepted
 
-Required Actions:
+🔧 Required Actions:
   1. Run /ant:build {phase} again
   2. Prime Worker MUST spawn at least 1 specialist
   3. Re-run /ant:continue after spawns complete
@@ -288,17 +299,19 @@ bash .aether/aether-utils.sh error-flag-pattern "no-spawn-violation" "Prime Work
 **HARD REJECTION - If watcher_count == 0 (no testing separation):**
 
 ```
-⛔ WATCHER GATE FAILED - PHASE BLOCKED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⛔👁️🐜 W A T C H E R   G A T E   F A I L E D
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 No Watcher ant was spawned for testing/verification.
 Testing MUST be performed by a separate agent, not the builder.
 
-Why this matters:
+🐜 Why this matters:
   - Builders verify their own work = confirmation bias
   - Independent Watchers catch bugs builders miss
   - "Build passing" ≠ "App working"
 
-Required Actions:
+🔧 Required Actions:
   1. Run /ant:build {phase} again
   2. Prime Worker MUST spawn at least 1 Watcher
   3. Watcher must independently verify the work
@@ -311,12 +324,7 @@ The phase will NOT advance until a Watcher validates.
 **If spawn_count >= 1 AND watcher_count >= 1:**
 
 ```
-✅ SPAWN GATE PASSED
-
-Spawns: {spawn_count} workers
-Watchers: {watcher_count} (independent verification)
-
-Proceeding to runtime verification.
+✅🐜 SPAWN GATE PASSED — {spawn_count} workers | {watcher_count} watchers
 ```
 
 Continue to Step 1.7.
@@ -334,20 +342,18 @@ Run for each file in `files_created` and `files_modified` from Prime Worker outp
 **Anti-Pattern Report:**
 
 ```
-Anti-Pattern Scan
-=================
-Files scanned: {count}
+🔍🐜 Anti-Pattern Scan — {count} files scanned
 
 {if critical issues:}
-🛑 CRITICAL ISSUES (must fix):
+🛑 CRITICAL (must fix):
 {list each with file:line and description}
 
 {if warnings:}
-⚠️ WARNINGS (review recommended):
+⚠️ WARNINGS:
 {list each with file:line and description}
 
 {if clean:}
-✅ No anti-patterns detected
+✅🐜 No anti-patterns detected
 ```
 
 **CRITICAL issues block phase advancement:**
@@ -364,9 +370,9 @@ Files scanned: {count}
 If CRITICAL issues found, display:
 
 ```
-⛔ ANTI-PATTERN GATE FAILED
+⛔🐜 ANTI-PATTERN GATE FAILED
 
-Critical anti-patterns detected that must be fixed:
+Critical anti-patterns detected:
 {list issues with file paths}
 
 Run /ant:build {phase} again after fixing.
@@ -390,21 +396,20 @@ find . -name "*.test.*" -o -name "*_test.*" -o -name "*Tests.swift" -o -name "te
 **If Prime Worker claimed tests_added > 0 but no test files found:**
 
 ```
-⛔ TDD GATE FAILED - FABRICATED METRICS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⛔🧪🐜 T D D   G A T E   F A I L E D
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Prime Worker claimed:
   tests_added: {claimed_count}
   tests_total: {claimed_total}
-  coverage_percent: {claimed_coverage}%
+  coverage: {claimed_coverage}%
 
 But no test files were found in the codebase.
 
-This is a CRITICAL violation:
-  - TDD metrics were fabricated
-  - No actual tests were written
-  - "All passing: true" was a lie
+🚨 CRITICAL violation — fabricated TDD metrics.
 
-Required Actions:
+🔧 Required Actions:
   1. Run /ant:build {phase} again
   2. Actually write test files (not just claim them)
   3. Tests must exist and be runnable
@@ -430,10 +435,11 @@ Before advancing, the user must confirm the application actually runs.
 Use AskUserQuestion:
 
 ```
-Runtime Verification Required
-=============================
+──────────────────────────────────────────────────
+🐜 Runtime Verification Required
+──────────────────────────────────────────────────
 
-Build and compile checks passed, but we need to verify the app actually works.
+Build checks passed — but does the app actually work?
 
 Have you tested the application at runtime?
 ```
@@ -446,18 +452,13 @@ Options:
 
 **If "Yes, tested and working":**
 ```
-✅ RUNTIME VERIFICATION PASSED
-
-User confirmed application runs correctly.
-Proceeding to phase advancement.
+✅🐜 RUNTIME VERIFIED — User confirmed app works.
 ```
 Continue to Step 2.
 
 **If "Yes, tested but has issues":**
 ```
-⛔ RUNTIME GATE FAILED
-
-User reported runtime issues. The phase cannot advance with a broken app.
+⛔🐜 RUNTIME GATE FAILED — User reported issues.
 
 Please describe the issues so they can be addressed:
 ```
@@ -471,17 +472,12 @@ Do NOT proceed to Step 2.
 
 **If "No, haven't tested yet":**
 ```
-⏸️ RUNTIME VERIFICATION PENDING
+⏸️🐜 RUNTIME PENDING — Test the app, then run /ant:continue again.
 
-Please test the application and run /ant:continue again.
-
-Testing checklist:
   - [ ] App launches without crashing
   - [ ] Core features work as expected
   - [ ] UI responds to user interaction
   - [ ] No freezes or hangs
-
-Come back when you've tested.
 ```
 
 Do NOT proceed to Step 2.
@@ -518,19 +514,19 @@ Parse result for `blockers`, `issues`, and `notes` counts.
 **If blockers > 0:**
 
 ```
-⛔ FLAGS GATE FAILED - BLOCKERS ACTIVE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+⛔🚩🐜 F L A G S   G A T E   F A I L E D
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-{blockers} blocking flag(s) must be resolved before phase advancement.
+{blockers} blocker(s) must be resolved first.
 
-Active Blockers:
+🚩 Active Blockers:
 {list each blocker flag with ID, title, and description}
 
-Required Actions:
+🔧 Required Actions:
   1. Fix the issues described in each blocker
   2. Resolve flags: /ant:flags --resolve {flag_id} "resolution message"
   3. Run /ant:continue again after resolving all blockers
-
-The phase will NOT advance with active blockers.
 ```
 
 **CRITICAL:** Do NOT proceed to Step 2. Do NOT advance the phase.
@@ -538,15 +534,11 @@ The phase will NOT advance with active blockers.
 **If blockers == 0 but issues > 0:**
 
 ```
-⚠️ FLAGS GATE: ISSUES NOTED
-
-No blockers, but {issues} issue(s) are active.
-These don't block advancement but should be addressed.
+⚠️🐜 FLAGS: {issues} issue(s) noted (non-blocking)
 
-Active Issues:
 {list each issue flag}
 
-Use /ant:flags to review and acknowledge or resolve.
+Use /ant:flags to review.
 ```
 
 Continue to Step 2.
@@ -554,9 +546,7 @@ Continue to Step 2.
 **If all clear (no blockers or issues):**
 
 ```
-✅ FLAGS GATE PASSED
-
-No blocking flags. Proceeding to phase advancement.
+✅🐜 FLAGS GATE PASSED — No blockers.
 ```
 
 Continue to Step 2.

package/.opencode/commands/ant/entomb.md

@@ -121,6 +121,51 @@ Entombment cancelled. Colony remains active.
 ```
 Stop here.
 
+### Step 4.5: Check XML Tools
+
+XML archiving is required for entombment. Check tool availability before proceeding.
+Uses `command -v xmllint` directly — consistent with seal.md's tool check.
+
+```bash
+if command -v xmllint >/dev/null 2>&1; then
+  xmllint_available=true
+else
+  xmllint_available=false
+fi
+```
+
+**If xmllint is NOT available:**
+
+Ask the user:
+```
+xmllint is not installed — XML archiving requires it.
+
+Install now?
+  - macOS: xcode-select --install (or brew install libxml2)
+  - Linux: apt-get install libxml2-utils
+
+Install xmllint? (yes/no)
+```
+
+Use AskUserQuestion with yes/no options.
+
+If yes:
+- On macOS: Run `xcode-select --install` or `brew install libxml2`
+- On Linux: Run `sudo apt-get install -y libxml2-utils`
+- After install attempt, re-check: `command -v xmllint >/dev/null 2>&1`
+- If still not available after install:
+  ```
+  xmllint installation failed. Cannot entomb without XML archiving.
+  Install xmllint manually and try again.
+  ```
+  Stop here.
+
+If no:
+```
+Entombment requires XML archiving. Install xmllint and try again.
+```
+Stop here.
+
 ### Step 5: Create Chamber
 
 Generate chamber name:
@@ -165,6 +210,35 @@ bash .aether/aether-utils.sh chamber-create \
   '{learnings_json}'
 ```
 
+### Step 6.5: Export XML Archive (hard-stop)
+
+Export combined XML archive to the chamber. This is a HARD REQUIREMENT — entomb fails if XML export fails.
+
+```bash
+chamber_dir=".aether/chambers/$chamber_name"
+xml_result=$(bash .aether/aether-utils.sh colony-archive-xml "$chamber_dir/colony-archive.xml" 2>&1)
+xml_ok=$(echo "$xml_result" | jq -r '.ok // false' 2>/dev/null)
+
+if [[ "$xml_ok" != "true" ]]; then
+  # HARD STOP — remove the chamber and abort
+  rm -rf "$chamber_dir"
+  echo "XML archive export failed. Colony NOT entombed."
+  echo ""
+  echo "Error: $(echo "$xml_result" | jq -r '.error // "Unknown error"' 2>/dev/null)"
+  echo ""
+  echo "The chamber has been cleaned up. Fix the XML issue and try again."
+  # Do NOT proceed to state reset or any further steps
+fi
+```
+
+If xml_ok is true, store for display:
+```bash
+xml_pheromone_count=$(echo "$xml_result" | jq -r '.result.pheromone_count // 0' 2>/dev/null)
+xml_archive_line="XML Archive: colony-archive.xml (${xml_pheromone_count} active signals)"
+```
+
+**Critical behavior:** If XML export fails, entomb STOPS. The chamber directory is removed (cleanup). The colony state is NOT reset. The user sees a clear error and can retry after fixing the issue.
+
 ### Step 7: Verify Chamber Integrity
 
 Run verification:
@@ -190,24 +264,25 @@ Backup current state:
 cp .aether/data/COLONY_STATE.json .aether/data/COLONY_STATE.json.bak
 ```
 
-Reset state while preserving memory (pheromones):
+Reset state (including memory fields, already promoted to QUEEN.md):
 ```bash
-jq '
-  .goal = null |
-  .state = "IDLE" |
-  .current_phase = 0 |
-  .plan.phases = [] |
-  .plan.generated_at = null |
-  .plan.confidence = null |
-  .build_started_at = null |
-  .session_id = null |
-  .initialized_at = null |
-  .events = [] |
-  .errors.records = [] |
-  .errors.flagged_patterns = [] |
-  .signals = [] |
-  .graveyards = []
-' .aether/data/COLONY_STATE.json.bak > .aether/data/COLONY_STATE.json
+# Resolve jq template path (hub-first)
+jq_template=""
+for path in \
+  "$HOME/.aether/system/templates/colony-state-reset.jq.template" \
+  ".aether/templates/colony-state-reset.jq.template"; do
+  if [[ -f "$path" ]]; then
+    jq_template="$path"
+    break
+  fi
+done
+
+if [[ -z "$jq_template" ]]; then
+  echo "Template missing: colony-state-reset.jq.template. Run aether update to fix."
+  exit 1
+fi
+
+jq -f "$jq_template" .aether/data/COLONY_STATE.json.bak > .aether/data/COLONY_STATE.json
 ```
 
 Verify reset succeeded:
@@ -230,37 +305,22 @@ rm -f .aether/data/COLONY_STATE.json.bak
 
 After entombing the colony, write the final handoff documenting the archived colony:
 
-```bash
-cat > .aether/HANDOFF.md << 'HANDOFF_EOF'
-# Colony Session — ENTOMBED
+Resolve the handoff template path:
+  Check ~/.aether/system/templates/handoff.template.md first,
+  then .aether/templates/handoff.template.md.
 
-## ⚰️ Colony Archived
-**Status:** Entombed in Chambers — Colony work preserved
+If no template found: output "Template missing: handoff.template.md. Run aether update to fix." and stop.
 
-## Chamber Location
-.aether/chambers/{chamber_name}/
+Read the template file. Fill all {{PLACEHOLDER}} values:
+  - {{CHAMBER_NAME}} → chamber_name
+  - {{GOAL}} → goal
+  - {{PHASES_COMPLETED}} → phases completed count
+  - {{TOTAL_PHASES}} → total phases count
+  - {{MILESTONE}} → milestone
+  - {{ENTOMB_TIMESTAMP}} → current ISO-8601 UTC timestamp
 
-## Colony Summary
-- Goal: "{goal}"
-- Phases: {completed} completed of {total}
-- Milestone: {milestone}
-- Entombed At: {timestamp}
-
-## Chamber Contents
-- colony-state.json — Full colony state
-- manifest.json — Archive metadata
-- activity.log — Colony activity history
-- spawn-tree.txt — Worker spawn records
-- flags.json — Project flags (if existed)
-
-## Session Note
-This colony has been entombed and the active state reset.
-The colony rests. Its learnings are preserved in the chamber.
-
-To start anew: /ant:lay-eggs "<new goal>"
-To explore chambers: /ant:tunnels
-HANDOFF_EOF
-```
+Remove the HTML comment lines at the top of the template.
+Write the result to .aether/HANDOFF.md using the Write tool.
 
 This handoff serves as the record of the entombed colony.
 
@@ -278,6 +338,7 @@ This handoff serves as the record of the entombed colony.
 🏆 Milestone: {milestone}
 
 📦 Chamber: .aether/chambers/{chamber_name}/
+{xml_archive_line}
 
 🐜 The colony rests. Its learnings are preserved.
 

package/.opencode/commands/ant/init.md

@@ -66,18 +66,29 @@ Check if `.aether/aether-utils.sh` exists using the Read tool.
 **If the file already exists** — skip this step entirely. System files are present.
 
 **If the file does NOT exist:**
-- Check if `~/.aether/system/` exists (expand `~` to the user's home directory)
+- Check if `~/.aether/system/aether-utils.sh` exists (expand `~` to the user's home directory)
 - **If the hub exists:** Run using the Bash tool:
+  ```bash
+  mkdir -p .aether/docs .aether/utils .aether/templates .aether/schemas .aether/exchange .claude/rules && \
+  cp -f ~/.aether/system/aether-utils.sh .aether/ && \
+  cp -f ~/.aether/system/workers.md .aether/ 2>/dev/null || true && \
+  cp -f ~/.aether/system/CONTEXT.md .aether/ 2>/dev/null || true && \
+  cp -f ~/.aether/system/model-profiles.yaml .aether/ 2>/dev/null || true && \
+  cp -Rf ~/.aether/system/docs/* .aether/docs/ 2>/dev/null || true && \
+  cp -Rf ~/.aether/system/utils/* .aether/utils/ 2>/dev/null || true && \
+  cp -Rf ~/.aether/system/templates/* .aether/templates/ 2>/dev/null || true && \
+  cp -Rf ~/.aether/system/schemas/* .aether/schemas/ 2>/dev/null || true && \
+  cp -Rf ~/.aether/system/exchange/* .aether/exchange/ 2>/dev/null || true && \
+  cp -Rf ~/.aether/system/rules/* .claude/rules/ 2>/dev/null || true && \
+  chmod +x .aether/aether-utils.sh
   ```
-  bash ~/.aether/system/aether-utils.sh bootstrap-system
-  ```
-  This copies system files from the global hub into `.aether/`. Display:
+  This copies system files from the global hub into `.aether/` and rules into `.claude/rules/`. Display:
   ```
   Bootstrapped system files from global hub.
   ```
 - **If the hub does NOT exist:** Output:
   ```
-  No Aether system files found locally or in ~/.aether/.
+  No Aether system files found locally or in ~/.aether/system/.
   Run `aether install` or `npx aether-colony install` to set up the global hub first.
   ```
   Stop here. Do not proceed.
@@ -124,9 +135,23 @@ If no instincts meet the threshold, display:
 
 Generate a session ID in the format `session_{unix_timestamp}_{random}` and an ISO-8601 UTC timestamp.
 
-Use the Write tool to write `.aether/data/COLONY_STATE.json` with the v3.0 structure.
+Resolve the colony-state template path:
+  Check `~/.aether/system/templates/colony-state.template.json` first,
+  then `.aether/templates/colony-state.template.json`.
+
+If no template found: output "Template missing: colony-state.template.json. Run aether update to fix." and stop.
+
+Read the template file. Follow its `_instructions` field.
+Replace all `__PLACEHOLDER__` values:
+  - `__GOAL__` → the user's goal from $normalized_args
+  - `__SESSION_ID__` → the generated session ID (format: `session_{unix_timestamp}_{random}`)
+  - `__ISO8601_TIMESTAMP__` → the current ISO-8601 UTC timestamp (used in both `initialized_at` and the events entry)
+  - `__PHASE_LEARNINGS__` → JSON array from Step 2.5, or `[]` if none
+  - `__INSTINCTS__` → JSON array from Step 2.5, or `[]` if none
+
+IMPORTANT: `__PHASE_LEARNINGS__` and `__INSTINCTS__` must be JSON array values (e.g., `[]` not `"[]"`).
 
-**If Step 2.5 found instincts to inherit**, convert each into the instinct format and seed the `memory.instincts` array. Each inherited instinct should have:
+**If Step 2.5 found instincts to inherit**, convert each into the instinct format for the `__INSTINCTS__` array. Each inherited instinct should have:
 - `id`: `instinct_inherited_{index}`
 - `trigger`: inferred from the instinct description
 - `action`: the instinct description
@@ -139,56 +164,29 @@ Use the Write tool to write `.aether/data/COLONY_STATE.json` with the v3.0 struc
 - `applications`: 0
 - `successes`: 0
 
-**If Step 2.5 found validated learnings**, seed `memory.phase_learnings` with each as:
+**If Step 2.5 found validated learnings**, seed the `__PHASE_LEARNINGS__` array with each as:
 - `phase`: `"inherited"`
 - `learning`: the learning text
 - `status`: `"validated"`
 - `source`: `"inherited:completion-report"`
 
-**If Step 2.5 was skipped or found nothing**, use empty arrays as before.
-
-```json
-{
-  "version": "3.0",
-  "goal": "<the user's goal>",
-  "state": "READY",
-  "current_phase": 0,
-  "session_id": "<generated session_id>",
-  "initialized_at": "<ISO-8601 timestamp>",
-  "build_started_at": null,
-  "plan": {
-    "generated_at": null,
-    "confidence": null,
-    "phases": []
-  },
-  "memory": {
-    "phase_learnings": "<inherited learnings or []>",
-    "decisions": [],
-    "instincts": "<inherited instincts or []>"
-  },
-  "errors": {
-    "records": [],
-    "flagged_patterns": []
-  },
-  "signals": [],
-  "graveyards": [],
-  "events": [
-    "<ISO-8601 timestamp>|colony_initialized|init|Colony initialized with goal: <the user's goal>"
-  ]
-}
-```
+**If Step 2.5 was skipped or found nothing**, use empty arrays `[]` for both `__PHASE_LEARNINGS__` and `__INSTINCTS__`.
+
+Remove ALL keys starting with underscore (`_template`, `_version`, `_instructions`, `_comment_*`).
+Write the resulting JSON to `.aether/data/COLONY_STATE.json` using the Write tool.
 
 ### Step 4: Initialize Constraints
 
-Write `.aether/data/constraints.json`:
+Resolve the constraints template path:
+  Check `~/.aether/system/templates/constraints.template.json` first,
+  then `.aether/templates/constraints.template.json`.
 
-```json
-{
-  "version": "1.0",
-  "focus": [],
-  "constraints": []
-}
-```
+If no template found: output "Template missing: constraints.template.json. Run aether update to fix." and stop.
+
+Read the template file. Follow its `_instructions` field.
+No placeholder substitution needed — the data keys are written as-is.
+Remove ALL keys starting with underscore (`_template`, `_version`, `_instructions`, `_comment_*`).
+Write the resulting JSON to `.aether/data/constraints.json` using the Write tool.
 
 ### Step 5: Validate State File
 

package/.opencode/commands/ant/organize.md

@@ -50,12 +50,12 @@ If no active signals after filtering:
   (no active pheromones)
 ```
 
-### Step 3: Spawn Archivist (Architect-Ant)
+### Step 3: Spawn Archivist (Keeper-Ant)
 
-Read `.aether/workers.md` and extract the `## Architect` section.
+Read `.aether/workers.md` and extract the `## Keeper` section.
 
 Spawn via **Task tool** with `subagent_type="general-purpose"`:
-# NOTE: Claude Code uses aether-architect; OpenCode uses general-purpose with role injection
+# NOTE: Claude Code uses aether-keeper; OpenCode uses general-purpose with role injection
 
 ```
 --- WORKER SPEC ---
@@ -171,7 +171,7 @@ CONSTRAINTS:
 
 ### Step 4: Display Report
 
-After the architect-ant returns, display header:
+After the keeper-ant returns, display header:
 
 ```
 🧹🐜🏛️🐜🧹 ═══════════════════════════════════════════════════
@@ -187,7 +187,7 @@ bash -c 'printf "\e[37m|  CODEBASE HYGIENE REPORT                            |\e
 bash -c 'printf "\e[37m+=====================================================+\e[0m\n\n"'
 ```
 
-Then display the architect-ant's full report verbatim.
+Then display the keeper-ant's full report verbatim.
 
 ### Step 5: Persist Report