Atlas node · Cross-project · public site layer

studio-notes

The cross-project reading layer for the public site: patterns, decisions, evidence rules, route data, and teaching translations that should outlive any single project page.

Repository →

Where pattern becomes public structure

studio-notes is no longer only an implied off-site notebook. In the current repo, it is the public connective tissue among the homepage threshold, Studio, Atlas, Methods, Research, lineage notes, and the data files that keep routes and archive entries explicit.

A project repo can tell the truth about one build. studio-notes names what should travel across builds: evidence standards, decision patterns, reading rules, route structure, teaching translations, and public boundary language.

The clearest public evidence is now inside this site: the How to Read page, Atlas method notes, studio route data, legacy work data, lineage pages, research notes, and lint checks that keep diagram references honest.

This layer is public-facing and intentionally selective. It does not expose private operations notes, participant details, home or studio topology, or anything that should remain outside the portfolio boundary.

What it is

studio-notes is the public distillation layer that keeps cross-project knowledge from being buried inside individual repos or repeated across every page.

What it lets people do

It lets readers understand which page holds which kind of truth, and it lets the site reuse shared methods without making the homepage or project pages carry every internal explanation.

What is public now

  • How to Read This Site Current public reading guide for Studio, Teaching, Atlas, Archive, Research, repositories, and evidence boundaries.
  • Methods Reusable cross-project patterns: evidence before polish, documentation as interface, assumption ledgers, and consent-forward systems.
  • Studio route data Current public route set for the Studio page: instruments, sound flow, image systems, fabrication, and maintenance.
  • Legacy work data Preserved archive and lineage routes surfaced as structured site data.
  • Research notebook Public method and research notes that support claims across the site.
  • Visual-system lint Repo check that keeps required diagram sources and Atlas references from drifting.

Evidence status

Status: public site layer. The strongest current proof is not a separate polished notes product; it is the way this repo now exposes reading rules, method notes, structured Studio routes, archive grids, lineage pages, and diagram lint as public architecture.

Next proof object: A small public index or changelog that lists each reusable studio-note pattern and the pages or data files that currently carry it.

What remains unresolved

  • The public layer should not imply that every private studio note, classroom detail, or operations record is publishable.
  • Some older Atlas nodes still need stronger proof objects before the cross-project claims can be fully supported.
  • The current split between Methods, Research, and Privacy & Ethics is useful but should stay lightweight enough that readers do not need a map before they can enter the work.

Methods surfaced

  • Documentation as Interface The site itself is now part of the interface for reading, operating, and inheriting the work.
  • Evidence Before Polish The node records public proof status instead of pretending every route is finished.
  • Assumption Ledger The page names what the public layer can and cannot safely claim.
  • Consent-Forward Systems Public notes stay careful around participants, students, private infrastructure, and identity-bearing evidence.

Proof objects

  • How to Read This Site Status: public. The moved homepage architecture explanation now lives here.
  • Atlas Methods Status: public. Reusable methods are explicit routeable pages instead of hidden internal logic.
  • Studio route data Status: public. Direct-access Studio entries are structured and maintainable.
  • Legacy work data Status: public. Archive entries and lineage notes are structured without removing legacy pages.
  • Pattern index Status: needed. A short index could make the distilled patterns easier to scan without opening every method page.
  • bseverns.github.io The public site repo is currently the clearest implementation surface for studio-notes.
  • MOARkNOBS-42 Bench findings and interface lessons become reusable evidence and teaching patterns here.
  • Human-Buffer Consent, perception, and refusal language become cross-project public method.
  • Memory Engine Retention, decay, retrieval, and steward logic feed the reading rules for scene systems.
  • Syllabus Teaching translations move between project method and course/workshop structure.
  • machine-docs Maintenance language becomes a durable public interface rather than private memory.

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.

Where to go next

Notes

Project repos remain canonical for project-specific implementation truth. The public site now carries the cross-project reading layer: where claims live, which methods travel, what evidence exists, and which parts of the practice should stay quiet.

Read studio-notes as a maintenance layer for meaning. It keeps the work from becoming either a pile of isolated repos or a homepage overloaded with internal explanation.