hosystem Engagements

Colophon

This site is built as a Ho System project, so its own record renders here—not a description of the practice, but the practice's artifacts doing the site's own work. The governing test the site holds itself to: every dynamic behavior renders something the framework actually does. The trail in the footer is your real walk. The flip is a real state change. This page is the site's own construction, on the record.

How it was designed

The look was decided the way the framework decides design: isolated sessions, one question each, landing as explicit numbers in a Basis of Design. The piece, the palette, the type, the step, the document, the diagram, definition-on-touch, the trail, the flip, and the narrow trail—each a session, each frozen, each changed only by a commit that names its reason (the propagation ledger). A coherence check assembled every frozen element; a spike validated them in Eleventy against the real corpus. This build ports the frozen basis—forward-only, the record intact.

What it renders, and from where

The site authors almost nothing. It ingests the practitioner's corpus at build time and renders it verbatim, pinning each source's commit so the build is reproducible:

methodfetch-step
ho-system79e96b801a13d11166cb5297aec8dbcf9879ed90 · 38 files
sharibakoa97b22af9b618d8fd3b1ed2de4b67a3d1ab76e28 · 23 files
ingested2026-07-08T05:04:06.496Z
fontsself-hosted subsets—no third-party requests

The stack

Eleventy · Cloudflare Pages · vanilla JavaScript · static only. No frameworks, no server code, no tracking. The chain diagrams are one SVG source generated at build time. The trail is localStorage only—nothing leaves your browser.

Colophon v0. As the site's own build hos close, they land here.

ingested: sharibako @ a97b22af9b61 · ho-system @ 79e96b801a13 · the glossary · the colophon