Evidence Before Polish
Status language, proof objects, and humble captures come before finished presentation. The first honest thing is often a trace.
Open noteAtlas layer
Methods
These notes name the patterns that travel across the fleet. They are not abstract theory pages. Each one points back to projects, proof objects, and operating habits that keep public claims legible.
Use Atlas for relationships, repositories for implementation truth, and these method notes for the reusable patterns in between.
The method layer is where the site is allowed to breathe. Project pages should stay useful. The homepage should stay threshold-like. Methods can carry the slower weather: the reasons a proof object matters, the ethics hidden inside a diagram, the way a repair note can become a kind of care, the way a missing image can still tell the truth if the boundary is named.
Read these pages as the hinge between studio language and system language. They do not separate poetry from procedure. They ask procedure to remember why it exists.
Start with the working methods
Documentation as Interface
Documentation teaches operation, consent, maintenance, and transfer. It is part of the work, not the caption after it.
Open noteAssumption Ledger
Uncertain claims get named before they disappear into hidden dependencies, private confidence, or myth.
Open noteConsent-Forward Systems
Consent, transparency, and user autonomy are treated as defaults, not as decorative policy added after capture.
Open note