where do you want to go
a quick map · plain english
The interactive centerpiece. Click any word in the orbit to filter the view; type what you want to do next, hit EMIT, and the page writes the brief for the next iteration.
The project tracker. Shows what's in flight, what just shipped, what's queued, what has drifted. Open this when you want to ask "where am I?"
A circular progress chart. Gray fills clockwise green as work completes; rings widen when a branch is in motion.
A 16-row grid mapping Greek mythology to Egyptian mythology. Shows where multiple Greek figures collapse into one Egyptian deity, and the reverse.
Same data, rendered as constellations. Each Egyptian deity is a bright central star; the Greek figures cluster around it.
The first Hermetic Business case study. A walk-through of the first client consult (Sola Story), written client-facing.
The first client consult parsed into three views (tree, timeline, tags). Every quote is line-grounded back to the original transcript — click an item, the transcript opens at the right line.
The home base. Every tool, principle, and idea organized by tier with filter chips at the top. If you want to see everything in one place — open this.
The single root idea everything else hangs off. The act of saying yourself into being from within a field you haven't named yet — and the way that act stays passable down a chain without losing its edge.
The project's self-description. Names the four deliverables (what the system knows · what it uses · what it makes · how it shows) and the rule that you drop ideas in and the system sorts them.
The frozen operating architecture as of today. Everything ratified, in one file. The agent reads this first, every time. Never edited — future iterations write v1.1.3.
The iteration rule. Every cycle has twelve steps; step twelve is "look back and correct." Twelve is also the structural cap — no tier holds more than twelve items.
The rendering rule. Each view is a "hologram" (a selection, a map, a timeline, a tree, a filter, a detail panel, a composer, a cycle). Holograms can overlay each other on a page but never get welded together.
The audit mechanism. At the end of every cycle, check whether the parts still resonate with the whole. Drift is caught and named here.
The project's tier system. Five layers: cosmos → iteration → branch → variant → converging-branches. Tells you which scale of work you're at.
The roster of every link in order. The chain is active, not archival — you can replay any link from the root forward.
The first link. The navel-stone. Where the saying happens. The starting point the rest of the chain extends from.
The second link. The mechanism by which the chain extends without forgetting — each new link carries the prior link's substrate.
The dictionary of terms you minted yourself. Words you struck like dies into the language.
The dictionary of terms you borrowed from established traditions. The canonical register — words like Omphalos, Pars-pro-toto, As-above-so-below.
how this got built · 23 iterations
The captain had been building tools, viewers, principles, and case studies across hundreds of chats. The artifacts existed — what was missing was the organizing layer that would let any of them be navigated as one thing.
earlier surfaces: Meta-Map.html· The-Constellation.html· Principia-Operandi.html· Site-Constellation.html
Two foundational principles got written down. Executing-as-architecting: the way you build the system IS the way you think about the system. Delegation-and-handoff: how the captain, the AI agents, and the deterministic code trade work cleanly.
_principia/executing-as-architecting.md· _principia/delegation-and-handoff.md
The operating kernel document was written: the bedrock that says "naming a thing installs the operation." It became the single source-of-truth hub the rest of the project would route back to.
Earlier that day, a different chat had skipped reading the principles and shipped something off-spec ("Drift-001"). The response wasn't to write more rules — it was to make the rules structural: a five-item gate every agent has to walk past before producing anything.
The project tracker shipped. A Python scanner walks the whole tree, a "Thoth" pass merges proposals, and a renderer emits a single HTML dashboard. "Where am I?" became a clickable surface instead of a question.
A circular progress visualization shipped. Gray fills clockwise green as branches complete; rings widen when a branch is in motion, narrow again when resolved. Mantra runs along the inside curve.
wheel.html · drift caught: the word "cyclic-progress" was used as a term without being added to the dictionary first.
The iteration cycle got named: every cycle has twelve breaths, and the twelfth is "self-monitor and correct." Twelve also became the structural cap — no tier of the system ever holds more than twelve items. Over twelve, condense into a sub-tier (which gets its own cap of twelve).
The first client consult (Sola Story) was parsed into three views — tree, timeline, tags — with every quote line-grounded back to the original transcript. Click any item, the transcript opens at the right line.
The first Hermetic Business Services case study shipped, in a client-facing register. The structural insight: the legal act of registering a DBA (a "doing business as" name) IS the ritual that calls a business into being — naming installs operation, at the business scale.
The Greek-to-Egyptian mythology mapping shipped — first as a 16-row table, then as a star map. Showed how multiple Greek figures can collapse into one Egyptian deity (Osiris absorbs Dionysus + Hades + Pluto + the dying-king pattern) and the reverse.
The navigable cosmos library shipped. Five views overlayed on one page: filter chips, tool browser, course-state map, the chain of named links, and a status strip at the top. The closest thing to a single "home base" surface.
The first entity rendered through the full schema: name, position, relationship, timeline, mythos, telos. Zeus's record carried 107 navigable references — every parent, child, partner, and conflict clickable into its own six-dimensional view. Recursive.
library entry: _titus/library_entries/
The captain's earlier hermetic-business schema converged with the cosmos. Five principles were already-in-lexicon; six are expansion-pending. Also: the named-link chain (osisus) was recognized as the same pattern the captain had already named TULKU_STREAM in prior work — the system had been running it textually all along.
The common visual skin used across eleven different cast pages was extracted into one shared substrate file (CSS + JS). All the pages now point at one source of truth for theme, typography, and the shared widgets.
Ra-Function was named the parent axiom. Underneath it, twelve operating principles got carved out, each with sub-tier methods. For every principle, the "shadow" (the disowned reading of the principle — what it looks like when it breaks) was also named.
Captain caught a methodology failure: editing files in place was destroying their prior state. Six canonical files had been overwritten without archiving the older version first. Correction: the rule "iterate, don't decimate" now binds at the file scale — every change writes a new version into an archive folder, the canonical filename always points at the newest version, the prior is preserved.
_archive/_README.md · the corrective protocol
The parent axiom was passed through five lenses (science, metaphysics, myth, nature, plus a synthesizer that holds all four). Convergence: self-distinction-as-substrate-of-its-own-successors. Shadow named: solipsistic-origination — the utterance forgetting it's within a field, claiming to BE the field.
Five adversarial edge cases (paywall, recursion, counterpoint, certainty, qwurfblat — none of them real entities, all designed to break the schema) were run through the methodology. The schema held against all five. The framework proved robust enough to lock.
The frozen operating snapshot was ratified. The agent now operates FROM this file; future iterations write v1.1.3 and beyond rather than editing this one. "Path D" is in effect — schema additions surfaced by the stress test are flagged as provisional but not yet canonicalized, pending evidence from the ten remaining lens-passes.
The second five-lens pass: the centering principle through all five lenses. Two of twelve principles now enriched; ten remaining queued.
The four-deliverable project spec was rewritten with the "egregore" framing made explicit — the project is itself a thoughtform that organizes ideas by being a microcosm of the system it builds. Same day, the second osisus link (Tulku-Stream) was named and added to the lineage roster.
A long-form, plain-English orientation document was written assuming the reader has no memory of the project at all. It was used as the source material for the visual index you're navigating right now.
The page you are reading right now. Mobile-first card grid on one tab, this chronological story arc on the other. One HTML file, no external dependencies, opens straight from the disk.
_titus/start.v2.html· prior: v1 archived
Where this leaves us
A navigable cosmos of the captain's work, with twelve operating principles, two named links in the kernel chain (Omphalos, Tulku-Stream), five-lens enrichment passes ongoing (two of twelve done), and a locked operating snapshot (CORE v1.1.2). Next: scale the lens passes through the remaining ten principles, then ratify the path-D provisional schema fields into v1.1.3.
captain · shalaco
iteration · 2026-05-22 · core v1.1.2
the cosmos names itself by running