Operations Config

# CLAUDE.md — Operations Config

## SOP Format
Every Standard Operating Procedure must include:
1. **Purpose**: one sentence explaining why this SOP exists
2. **Scope**: who does this apply to, and when
3. **Steps**: numbered, each step is one action (verb + object)
4. **Decision points**: if/then branches clearly marked
5. **Owner**: who maintains this SOP and review cadence

## Status Reporting
- RAG format: Red (blocked), Amber (at risk), Green (on track)
- Weekly update every Friday by 4pm
- Include: status, progress vs plan, blockers, next week priorities
- Keep to 5 bullets max per project

## Meeting Notes Template
- Date, attendees, duration
- Decisions made (numbered)
- Action items: WHO does WHAT by WHEN
- Parking lot: topics deferred to future discussion
- Distribute within 2 hours of meeting end

## Process Documentation
- Write for someone doing this for the first time
- Include screenshots for any step involving a UI
- Version-control all SOPs (date + author on every revision)
- Review quarterly — archive anything not updated in 6 months