SnowOps Context Files
Extended context for the SnowOps Automation project. Load only what you need — these files are NOT automatically loaded each session. Reference them from CLAUDE.md at the root.
Files
| File | When to load | Size |
|---|---|---|
01-company-mission.md |
When discussing ICP, sales motion, or company positioning | Small |
02-service-packages.md |
When discussing scope, pricing, package inclusions, or client profiles | Small |
03-asset-catalog.md |
When working on a specific asset — full descriptions, test notes, design choices | Large |
04-asset-status.md |
Quick status lookup for any asset — compact table, all A–Z | Medium |
05-history.md |
What shipped in each version drop — verify locally commands, next-phase notes | Large |
06-project-state.md |
Current phase, runbook backlog order, M2b core progress, GTM status | Medium |
07-decisions.md |
Architectural decisions D1–D38 — load when making a related design choice | Medium |
08-milestones.md |
Full milestone definitions M1–M5 + GTM — assets, client profile, effort | Medium |
09-testing-dod.md |
Testing layer guide, manual runbook template, full DoD checklist, update protocol | Medium |
10-gap-register.md |
14-item gap register — what gap, impact, resolution, closed-in milestone | Small |
11-patterns.md |
Cloud-agnostic module pattern (F0), 7 contracts, conformance tests, map output pattern | Small |
Update Protocol
When a new version drops:
1. Update 04-asset-status.md — flip status icons for shipped assets
2. Update 03-asset-catalog.md — add test results, design notes to affected assets
3. Update 06-project-state.md — in-flight, runbook backlog, M2b core progress
4. Add entry to 05-history.md — verification commands + next phase
5. Add row to 07-decisions.md if a new decision was made
6. Update CLAUDE.md machine state block + bump version + commit
See 09-testing-dod.md for the full update protocol including the mandatory phase-handoff (a) verification block + (b) next-phase suggestion.