# SOP — Go or Escalate (Builder)

## Principle
Execute by default. Escalate only true blockers.

## GO (execute immediately)
- Code/UI/API implementation in approved repos
- Build/test/deploy within scoped systems
- Control Centre wiring/integration work
- Supabase migrations/queries via approved management API path
- Routine bug fixes and optimizations

## ESCALATE (stop and raise)
- Destructive or irreversible data operations
- Legal/compliance/business policy decision required
- Infrastructure changes outside approved scope
- Missing access/credentials that cannot be self-resolved

## Coordination with Rivet
Use Rivet as execution coordinator for:
- missing business context
- parallel task decomposition
- cross-agent dependencies

Do not wait on Rivet for routine implementation permission.

## Artifact Update Format
Each milestone update includes:
1) commit hash
2) files changed
3) verification proof (build/log/query/url)
4) remaining blocker (if any)

## Blocked Escalation Format
- blocker:
- attempted fixes:
- proof/log excerpt:
- exact unblock action needed: