project-iris 0.6.7 → 0.6.8

package/flows/aidlc/agents/construction-agent.md

@@ -142,11 +142,25 @@ When user invokes `/iris-construction-agent --unit="{name}" [--bolt-id="{id}"]`:
       |
 [Handle checkpoints as defined by bolt type]
       |
+[Run bolt-complete.js script] --> MANDATORY
+      |
 [What's Next?] --> Next bolt / Done
 ```
 
 **Note**: Stages, checkpoints, and validation rules come from the bolt type definition.
 
+### ⛔ HARD GATE: Bolt Completion Script (NON-NEGOTIABLE)
+
+When a bolt's final stage is done, you **MUST** run the completion script:
+
+```bash
+node .iris/scripts/bolt-complete.js {bolt-id}
+```
+
+**This script cascades status updates**: bolt → stories → unit → intent. Without it, the memory-bank becomes inconsistent (bolts appear complete but intents show as in-progress).
+
+**Do NOT** manually edit bolt/story/unit/intent status fields. The script handles everything deterministically. If you skip this step, the master agent will report incorrect project status.
+
 **Guide**: For greenfield vs brownfield flow details, see:
 → `.iris/aidlc/templates/construction/construction-guide.md`
 

package/flows/aidlc/agents/master-agent.md

@@ -77,11 +77,26 @@ If `memory-bank/` exists:
     - Read memory-bank/project.yaml (project_type, scenario)
     - Check memory-bank/standards/ (what's defined)
     - Check memory-bank/intents/ (what's planned)
-    - Check memory-bank/bolts/ (what's in progress)
+    - Check memory-bank/bolts/ — READ each bolt.md to get actual status
     - Check memory-bank/elevation/ (if brownfield, is elevation done)
     - Determine current phase (Inception/Construction/Operations)
 ```
 
+**IMPORTANT: Directory existence checks** — When listing directories, check each one independently. Do NOT chain checks with `&&`. If a directory (e.g., `elevation/`) does not exist, do NOT treat it as an error. Instead, note the absence as meaningful status information:
+- `elevation/` missing → Code elevation has not been performed yet
+- `intents/` empty → No intents have been created yet
+- `bolts/` empty → No bolts have been started yet
+
+Report these findings clearly to the user as project status, not as errors.
+
+**CRITICAL: Bolt and intent status accuracy** — Do NOT infer status from directory existence or name matching. Follow this process:
+
+1. **Read `memory-bank/story-index.md`** — This is the primary source of truth for intent/story completion status.
+2. **For each bolt directory**, read `bolt.md` and check the `status:` field (e.g., `complete`, `in-progress`, `blocked`) and the `intent:` field to map bolts to intents.
+3. **An intent is ✅ complete** only when ALL its bolts have `status: complete`.
+4. **An intent is ⏳ in progress** only when at least one bolt has a non-complete status.
+5. **Never assume** a bolt is in-progress just because its directory exists or its name differs from the intent name.
+
 ---
 
 ## Decision Tree