Systems That Stay Readable

Skill

Constraints that last: protocols, route topology, local-first assumptions, interface boundaries. Hidden state has a social cost.

Now

This site is the proof. Website field guide. Design and software doors.

Leave structures another person can inspect, repair, and extend. data-spw-*, layered CSS, and staged modules are the seams — focus operator chips to see resonance without a second dashboard.

~"architecture_studies"

Reference Studies

A useful architectural image is not a literal system diagram. It shows the kind of load-bearing relationship you want the software to have: fold, support, seam, span, or compression.

Papergami architectural study with stacked planes and interior spans. — **Load-bearing seams** Good architecture exposes where the joins are. The seam is visible, but it does not fail under ordinary use.

A pink-spattered page framing a vertical stack of four ink boxes, each tagged with a hash mark — **Composable volumes** Module boundaries work best when they can stack, rotate, or be replaced without collapsing the surrounding system.

~[pattern_languages]

System Patterns

Durable Protocols

Portable formats, inspectable HTML, and local-first invariants are architectural choices because they decide who can recover the system later.

site: Local First Web

Christopher Alexander

Pattern language is still useful because it treats design as a family of recurring relationships rather than a single frozen blueprint.

wiki: A Pattern Language

Readable Surface Architecture

At site scale, architecture is not only data flow. It is also route affordances, semantic depth, and whether a public page can explain its own moving parts.

route: Website design