# SOP — Inbox Triage (Builder)

## Purpose
Keep coordination latency low and prevent backlog-driven execution drift.

## Triage Windows
- Every heartbeat: check unread JSONL and BUILDER-INBOX.md
- In P0 mode: quick triage only, then execute locked task

## ACK Rules
1. ACK direct task messages in first sprint cycle
2. ACK emergency directives immediately
3. Group ACK related reminders in one concise update

## Stale Cutoff
- Any unread older than 2 hours during active window is stale
- Any stale emergency message requires immediate ACK + status note

## Batch Processing
For large backlog:
1. Categorize: direct task / blocker / reminder / informational
2. ACK task+blocker first
3. Defer informational with explicit defer note

## Reporting Format
- unread count
- oldest unread age
- critical messages actioned
- next triage ETA

## Anti-Drift Rule
Do not let triage replace execution. After triage, return to active task sprint immediately.