studio-notes

build/crash (repeat)

This is the distilled layer: patterns, decisions, references, and teaching cards harvested from project repos.

Start here: ONBOARDING.md.

The rule that keeps this repo sharp

• Project repos are canonical for project-specific truth.
• studio-notes is canonical for cross-project truth.
• Link-first. Copy only when transforming into reusable truth.

The harvest workflow (full-moon friendly)

1. In each project repo, keep a docs/HARVEST.md file (ore pile).
2. During the review, copy new bullets into 00_INBOX/harvest-inbox.md.
3. Promote each item into one of:
   • 02_PATTERNS/ (reusable recipes)
   • 03_DECISIONS/ (why we chose X; when to revisit)
   • 04_REFERENCE/ (tables you trust; known-good settings)
   • 05_TEACHING/ (handouts, demo scripts, annotated screenshots)
4. Record what is harvested in 06_REVIEWS/YYYY-MM.md.
5. Clear the inbox.

Prefixes for HARVEST bullets

Use these in project docs/HARVEST.md:

• PATTERN: reusable method/checklist
• DECISION: why something chosen
• PITFALL: what bit (grrr) + antidote
• CAL: calibration / known-good settings
• TEACH: demo/explanation/screenshot set

The style contract

See STYLE_GUIDE.md for voice, structure, and the “link‑first” bias that keeps this repo sharp.