---

name: observation-triage-cycle description: HAIOS Observation Triage Cycle for processing captured observations. Use when scanning archived work items to triage and act on observations. Guides SCAN->TRIAGE->PROMOTE workflow with dimension validation. generated: 2025-12-28 last_updated: '2026-01-07T20:28:24'

Observation Triage Cycle

This skill defines the SCAN-TRIAGE-PROMOTE cycle for processing archived observations and routing them to actionable outcomes.

When to Use

Manual invocation: Skill(skill="observation-triage-cycle") when processing accumulated observations. Via recipe: just triage-observations for quick scan. Scheduled: Can be invoked during heartbeat or session-end.

---

The Cycle

CopySCAN --> TRIAGE --> PROMOTE
  |         |           |
  |         |           +-> spawn:INV, spawn:WORK, spawn:FIX
  |         |           +-> memory (store insight)
  |         |           +-> discuss (flag for operator)
  |         |           +-> dismiss (no action)
  |         |
  |         +-> Apply dimensions: category, action, priority
  |
  +-> Find archived observations with triage_status: pending

---

1. SCAN Phase

Goal: Find archived work items with untriaged observations.

Actions:

1. Run scan command:

   Copyjust triage-observations
   

2. Report count of items with pending observations
3. List work items and observation summaries

Exit Criteria:

• Scan completed
• Count and list of pending observations reported

Tools: Bash(just triage-observations), Read

---

2. TRIAGE Phase

Goal: Classify each observation with category, action, and priority.

Triage Dimensions (Industry Standard):

Actions:

1. For each observation, prompt for dimensions:
   • Category: What type of observation is this?
   • Action: What should happen next?
   • Priority: How urgent is this?
2. Validate dimensions (ValueError if invalid)
3. Collect triaged observations

Example Triage Prompt:

CopyObservation: "commit-close recipe uses legacy patterns"
Section: Gaps Noticed
Source: E2-217

Category? [bug/gap/debt/insight/question/noise]: gap
Action? [spawn:INV/spawn:WORK/spawn:FIX/memory/discuss/dismiss]: spawn:FIX
Priority? [P0/P1/P2/P3]: P2

Exit Criteria:

• All observations triaged with valid dimensions
• Triaged list ready for promotion

Tools: AskUserQuestion (for dimension selection), triage_observation()

---

3. PROMOTE Phase

Goal: Execute the action for each triaged observation.

Action Handlers:

Actions:

1. For each triaged observation, execute action
2. Track results (spawned IDs, memory IDs)
3. Update observations.md with triage log entry
4. Set triage_status: triaged in frontmatter

Exit Criteria:

• All actions executed
• Observations.md updated with triage log
• triage_status updated to triaged

Tools: /new-investigation, /new-work, ingester_ingest, Edit

---

Composition Map

---

Quick Reference

---

Key Design Decisions

---

Related

• E2-217: Observation Capture Gate (capture mechanism)
• INV-047: Close Cycle Observation Phase Ordering (capture timing)
• INV-023: ReasoningBank Feedback Loop Architecture (same pattern)
• close-work-cycle skill: Captures observations during closure
• observations.py: Core functions for scan, parse, triage, promote