Atlas node

studio-notes

Distilled cross-project layer for patterns, decisions, trusted reference, and teaching cards harvested from the studio repos.

Repository →

What is public now

  • Pattern cards
  • Decision records with revisit triggers
  • Trusted reference tables
  • Teaching cards with source links
  • MOARkNOBS-42 Bench findings and interface lessons can be distilled into reusable build and teaching patterns.
  • Memory Engine Consent, retention, and steward logic can be promoted into decisions and reusable operating references.
  • Syllabus Turns project methods into teaching material that can travel across courses and workshops.
  • Class Hub Keeps cross-project access, delivery, and maintenance knowledge durable without burying it inside one app.

Source trail

The Atlas is the relationship layer. Use the repository for current project-specific truth, and use studio-notes when methods, decisions, or teaching material need to travel across the fleet.

Notes

Project repos are canonical for project-specific truth. studio-notes is canonical for cross-project truth.

Use it when the thing you learned needs to survive beyond one repo: a repeatable method, a decision with consequences, a known-good baseline, or a teaching translation. When you need the live build, current setup, or implementation details, go back to the source repo.

It exists in part because constrained years of rebuilding made legibility and durable memory non-negotiable. When a setup cannot stay continuously available, notes have to carry more of the practice forward.