Project shapes

Part of Architecture: what kind of artifact are you building? Complexity is earned. This is not a rival track to compute — hosts live under What runs where → Compute.

Language and framework bets: Language selection · Web framework selection.

flowchart LR
  A[Simple website] --> B[CLI]
  B --> P[Python package]
  P --> C[Multi-lang monorepo]
  A -.->|skip if you already need it| C

You do not have to walk every step in order. The sequence is a teaching order: each shape adds mechanisms the previous ones deliberately skipped.

Shape	You are here when…	Default stance
01 — Simple website	One site, one deploy target, few people	Ship thin; refuse monorepo/agent swarms
02 — CLI	A command-line tool users install/run	DX + tests + packaging; still one artifact
03 — Python package	Importable library (optional console scripts)	PyPI/private index; API + tests + release
04 — Monorepo	Multiple packages/languages/deploy units	Boundaries, affected CI, ESC secrets, ownership

How to read a shape page

1. Know your lifecycle phase (Discover / Deliver / Operate / Maintain / Retire).
2. Confirm Architecture bets you need (language, framework, placement).
3. Open the shape page → reading order and starter DAG.
4. When stuck, idk-now or kiss — don’t invent a fifth language or third web default.

Shared spine

flowchart TD
  O[Orient] --> G[Achievable goal]
  G --> W[Work + evidence]
  W --> S[Ship]
  S -->|learn| O

Strategies and practices remain the modular deck. Shape pages tell you which cards to draw first.