# SOP — P0 Execution Mode (Builder)

## Purpose
Prevent stall loops during critical direct tasks from Rocky by enforcing artifact-first execution.

## Start Criteria
Enter P0 mode when any of these are true:
- Rocky explicitly says priority/only task/do now
- outage/security/payment/auth incident impacts live users
- Rivet emergency directive maps to live-system risk

## Lock Procedure
1. Set `status.json.current_task` = `LOCKED P0: <task>`
2. Stop all secondary work
3. Run only minimal health checks (inbox/build/status)

## Execution Cycle
- Work in 45+ minute focused sprint blocks
- Deliver artifact updates only:
  - commit hash
  - files changed
  - proof output (build/log/query/url)

## Done Criteria
P0 is complete only when:
- required code/config changes landed
- verification outputs captured
- live path validated (if deploy task)
- blocker list is empty or explicitly handed off

## Escalation Template (no artifact within 30 min)
Status: BLOCKED
- blocker:
- attempted fixes:
- current evidence/log:
- next required input/action:

## Handoff Template
- what changed:
- commits:
- verification proof:
- remaining risk:
- next step owner: