hive.colony-progress-tracker

1## Operational Protocol: Colony Progress Tracker
2 
3**Applies when** your spawn message has `db_path:` and `colony_id:` fields. The DB is your durable working memory — tells you what's done, what to skip, which SOP gates you owe.
4 
5Access via `terminal_exec` running `sqlite3 "<db_path>" "..."`. Tables: `tasks` (queue), `steps` (per-task decomposition), `sop_checklist` (hard gates).
6 
7### Claim: assigned task (check this FIRST)
8 
9If your spawn message includes a `task_id:` field, the queen pre-assigned a specific row to you. Claim that row by id — **do not** use the generic next-pending pattern below:
10 
11```bash
12sqlite3 "<db_path>" <<'SQL'
13UPDATE tasks SET status='claimed', worker_id='<worker-id>',
14  claim_token=lower(hex(randomblob(8))),
15  claimed_at=datetime('now'), updated_at=datetime('now')
16WHERE id='<task_id>' AND status='pending'
17RETURNING id, goal, payload;
18SQL
19```
20 
21Empty output → another worker raced you or the row is already done. Stop and report.  Non-empty → that row is yours, proceed to "Load the plan".
22 
23### Claim: next pending (fallback when no task_id is assigned)
24 
25If your spawn message did NOT include `task_id:` — you are a generic fan-out worker racing on a shared queue. Use the generic next-pending claim:
26 
27```bash
28sqlite3 "<db_path>" <<'SQL'
29UPDATE tasks SET status='claimed', worker_id='<worker-id>',
30  claim_token=lower(hex(randomblob(8))),
31  claimed_at=datetime('now'), updated_at=datetime('now')
32WHERE id=(SELECT id FROM tasks WHERE status='pending'
33…