Architecture
One body of work. Two deliberately separate planes.
Management Plane
~/dev/repo-portfolio — the operational source of truth.
- Tracks all public repositories (98 as of latest snapshot).
- Enforces the Ormus GitHub Standard across the entire fleet (README anatomy, Gold Hat, per-repo mascots, commit discipline).
- Maintains family taxonomy: Libre (the 12 flagship depth-complete systems), Skills, Ormus tools, Hermetic core.
- Produces slim, versioned snapshots for downstream consumption.
Reality lives here. No narrative drift allowed.
Narrative Plane
This site (ormus.solutions) — the public, citable, visual record.
- Hosts the mascot visual system used as the header image in every qualifying repo.
- Distillations journal: the four-stage filter applied to ideas worth keeping.
- /systems: live view of the Libre family with current stars and freshness.
- The knowledge graph, skills self-assessment, and operating history.
Legibility and taste live here. The work must be understandable without being in the room.
The Bridge
Lightweight API routes (/api/portfolio/*) consume slim exports from the management plane. The planes are kept in sync by explicit ritual, not hope.
This separation is the point. The management plane cannot lie to itself. The narrative plane cannot invent a prettier story than the data allows.
This page, and the narrative plane in general, is itself maintained by multiple agents (Grok and Claude Code) working in parallel on the same codebase. Coordination is handled explicitly via ACTIVE-WORK.md in the project root. The architecture described here is not only declared — it is practiced in how the site is built.
Follow the real-time signal on X
Raw observations, architecture decisions, and shipping updates.