Order of the Ætherwright
Symbolic Structure for Creative Work
Updated March 2026
Every consistent creative practice has a method underneath the visible work. The instinct that produces reliable results across different projects, different domains, different decades. But it’s invisible to everyone, including the person using it. You can’t teach what you can’t articulate. You can’t defend it under pressure. And if you can’t make it explicit, it erodes.
I had thirty years of that. I tried to surface it through a branding exercise, mapping my creative practice the way you’d build an RPG character sheet: domains, patterns, how I actually work across disciplines. What came back wasn’t a brand. It was the method itself, visible for the first time.
Once visible, so was the problem: invisible methods erode. Not catastrophically. Incrementally. A decision made under deadline pressure. A compromise that felt reasonable once. A principle abandoned because explaining it was harder than ignoring it. None of them feel like failures. Together they are.
So I dressed it up as a secret order. Glyphs, a Codex, Stewards, a daily ritual. I know how that reads. Building it felt embarrassingly serious. But a governance framework doesn’t survive as a text file. Give it the weight of an institution and people actually follow it.
Eight glyphs divide work by domain. Every folder, document, and decision gets a glyph. The name announces its category before you open it.
▲ UX / Systems / Strategy
▼ Narrative / Language
◀ Intuition / Reflection
▶ Illustration / Expression
■ Design / Grid / Typography
◆ Craft / Material / Fabrication
⬟ Photography / Observation
⬣ Code / Engineering / Logic
● Input / Research (non-domain)
All Unicode. All terminal-compatible. The set is closed. No new glyphs will be added. The constraint is deliberate.
A daily 15-minute alignment practice. Each morning: What will I defend today? What compromises won’t I make? Do this daily and the principles become muscle memory. Under pressure, habit operates.
The framework is institutional, not personal. A Codex as source of truth, a symbolic execution string that encodes how domains interact across a project’s phases. Stewards who maintain the order. Practitioners who use it.
/Æ/#|●▼||▲◆|||▶⬣⟩⟩[projects.versograms.cherubrock]/
Read left to right: input and narrative research, then systems and craft, then illustration and code. Completed and released. The Codex traces transformation, not usage. When ▶ appears in Phase 1 (sketching) and again in Phase 3 (vector refinement), that’s not redundancy. That’s the domain returning at a different altitude.
# A system that never ships — perpetual research
/Æ/#|●||●|||●~[systems.signals]/
# Completed, held back from release
/Æ/#|●||▲⬣|||⬣⟩[systems.savepoint.protocol]/
# Pure output — no research phase at all
/Æ/#|∅||∅|||▶⟩⟩[studies.miniposters.oneoff]/
I don’t own the framework. I steward it. Others can learn it.
The glyph system now classifies every artifact in this portfolio. Savepoint Protocol uses the same architecture. Formwork Protocol applies the same principle to project governance.
This is how I work. If it sounds like what you need, let's talk.