# Mission: Docker for local dev and reliable shipping

## Why
You build with TypeScript (often via AI-assisted coding) and need containers so local environments match what you ship. The goal is not “know Docker trivia” — it is develop locally and ship reliably, scalably, and securely, then maintain what you shipped.

## Success looks like
- Run and debug services with the **Docker CLI** (production-relevant skills first)
- Spin up local stacks (app + deps) without polluting the Mac host install
- Package a TypeScript app into an image you can run the same way locally and in deploy targets
- Inspect, fix, and reason about containers when something breaks in production
- Prefer secure, maintainable defaults as you grow (not root-by-default, not “works on my machine”)

## Constraints
- macOS with Docker already installed (Docker Desktop available)
- Primary stack: TypeScript; other languages OK when useful
- AI writes most of the code — you need enough mental models to review, prompt, and debug
- **CLI first**; Docker Desktop is a bonus for visual inspection, not the main path
- Complete beginner: no assumed prior container knowledge

## Out of scope
- Kubernetes / full orchestration (until shipping multi-host scale is real)
- Deep Linux kernel internals (namespaces/cgroups beyond the “why isolation works” level)
- Swarm as a primary target
- Becoming a Desktop power-user before CLI fluency
