sky-lattice/docs/decisions/D003-blueprint-vs-customer-repo.md

18 lines
554 B
Markdown
Raw Permalink Normal View History

# D003 — Blueprint vs customer repo
- **Status:** active
- **Date:** 2026-07-15
## Decision
Keep **blueprint** (modules, schemas, wizard catalogs, policies, skills) as versioned product IP. Each customer gets a **project repo** with intent, decisions, terraform root, and a copied skill pin.
## Why
Separates reusable best practices from client-specific answers and exceptions; enables blueprint upgrades via version pin.
## Alternatives rejected
- Forking the whole monorepo into every customer
- Storing only Terraform without an intent layer