--- title: Holograms · the rendering layer · overlay but never weld kind: principium-operandi captured: 2026-05-22 captured_by: Phase 2 / T-hierarchy · silicon alchemist register back_reference: ./executing-as-architecting.md parent_brief: ../_ops/BRIEF-OMPHALOS-001.md sibling: ./cosmos-to-converging-branches.md also_called: [the hologram layer, render layer, surfaces and views] domain: project-agnostic principle_honored: [executing-as-architecting, holograms, categorize-via-filter-not-inline, ptah-skin, thoth-ptah-captain, ratify-dont-decimate] sigil: ⎔ pre_flight: read_principia: yes found_grammar: yes viewer_skin: _ptah/cyrelium-md-viewer.html · canonical for any standalone surface stamped: yes gaps_disclosed: yes --- # Holograms · the rendering layer > *"you tried to hold two holograms at once and you needed space for two seperate holograms but you layed them on top of eachother and got things all miuxed up"* > — Shalaco, 2026-05-22, on `_ops/omphalos.html` after walking the cast ## §0 · The rule **Holograms can overlay but never weld.** A hologram is a rendered surface — a view, a template, a way data lays itself out so it can be acted on. Each hologram has its own logic and its own coordinate system. Two holograms can share a page; the page's *real estate* is the medium they overlay in. But the *affordances* of one hologram must not double as the affordances of another. A chip that re-keys the page is not also a star in the orbital map. A row that opens a side panel is not also a node in the constellation. Welding two holograms onto the same element costs clarity in proportion to the load each was carrying, and the cost shows up as captain-steers downstream. This principium is the orthogonal axis to `cosmos-to-converging-branches.md`. That principium says *what a thing IS in the project tree.* This one says *how it RENDERS.* ## §1 · What a hologram is A hologram is the **logic of a rendered surface.** It is not the data; it is not the file; it is the grammar that decides where things sit, what is clickable, what re-keys what, and what dimension is exposed as which affordance. A hologram is named by its shape, not its content. A hologram is to the cast what the cast is to the principium: the runnable instantiation. The principium is what to render; the cast is the file; the hologram is the way the cast lays itself down on screen. Holograms inherit the ptah skin (`_ptah/cyrelium-md-viewer.html`) at the CSS-variable layer — the typography, the color, the gradients — but the *structure* of each hologram is its own. A hologram carries the four coordinates in its own register. **Name:** what shape it takes (selection-interface · spatial-map · timeline · tree · tag-filter · detail-inspector · composer · cartographic). **Position:** where on the page it sits and how much real estate it owns. **Relationship:** which other holograms it composes with and which it must not weld to. **Timelines:** when its state changes — on hover, on click, on emit, on re-key. ## §2 · The known holograms Eight named so far. The inventory grows when a new shape is identified and named; it never shrinks (R0). **⬢ Selection-interface hologram.** Chips, filters, dropdowns, search inputs, segmented controls. The affordance by which the captain *chooses*. Its job is to narrow the set the rest of the page is showing. Its failure mode: pretending to also carry meaning (a filter chip whose *position* on the page implies something the chip's text does not). It must not be welded to a spatial-map. **Reference instance:** the binge-report filter strip (`05-20 Binge Report` / `05-21 Binge Report`) — DAY / BINGE THREAD / SEARCH / VIEW — clean because the strip's affordances are purely categorical and the spatial layout of the controls is decorative, not semantic. **◉ Spatial-map hologram.** Stars, orbits, positions, edges, nodes. The relational geometry. Each element's *coordinates carry meaning* — distance from center, angle, ring, proximity to neighbors all encode the relationship the data has. Its failure mode: the elements are also offered as filter affordances, so clicking a position-meaningful element is now interpreted as a categorical selection. It must not be welded to a selection-interface. **Reference instance:** the constellation viewer's SVG (`The-Constellation.html`, `Site-Constellation.html`) — stars sit where they sit because that's where they belong in the graph; the filter bar is a separate strip above. **◰ Timeline hologram.** Linear, chronological, ordered along one axis. Events, emissions, sessions, decisions, ship-dates. Failure mode: collapsing two unrelated timelines (e.g. capture-date and last-modified-date) onto one axis, so the viewer cannot tell which chronology is being read. **Reference instance:** the hermetic-business-parser's timeline view (`hermeticbusinessparser/`) and `_mnemosyne/mnemosyne.html`'s `recent emissions` section. **◬ Tree hologram.** Hierarchical, parent-child, indented or nested. The shape of a folder, an outline, a taxonomy. Failure mode: a tree whose siblings are actually peers under different parents (the four-matrices fracture is this exact failure made canonical). **Reference instance:** the hermetic-parser's tree view; `_mnemosyne/mnemosyne.json` `branches` as rendered into the dock. **▦ Tag/filter hologram.** Cross-cutting category dimensions exposed as filter axes — a row of toggles, a strip of dimensions, a multi-select. Each dimension is orthogonal to the others. Failure mode: baking categorization into individual row labels (per `gate-12-drift-detection.md` ▸ check #6 — *Categorize via filter, not inline*; the `tag-fire/water/earth/air/aegis` inline-chip anti-pattern). **Reference instance:** the binge-report filter strip surfaces this cleanly; the hermetic-parser's inline tag chips are the anti-pattern. **⊟ Detail/inspector hologram.** Single-record deep view. A side panel, a modal, a stacked card. Carries every field of one item, related rows below, links to neighbors. Failure mode: opening a detail view that does not let you navigate to the *next* item in the same shape, forcing a return to the list. **Reference instance:** `mnemosyne.html`'s right-side `side` panel — open with a row click, close with Escape, dl-formatted body. **⌬ Composer hologram.** Author/emit affordance. Inputs, textarea, select, an emit button. Captures captain intent and turns it into an artifact (a brief, a patch, a row). Failure mode: a composer that exports without preserving what was selected to compose it from, breaking provenance. **Reference instance:** `_ops/omphalos.html`'s bottom composer; `_mnemosyne/mnemosyne.html`'s `register-direction / register-branch` patch emitter. **⌖ Map/cartographic hologram.** Geographic or topological positioning that *means* something — latitude/longitude, network topology, conceptual coordinates carved by the captain. Like spatial-map but with a *given* coordinate system, not an emergent one. Failure mode: drawing a map with no key, so the position cannot be decoded back into meaning. **Reference instance:** `Meta-Map.html`, `Maps/`. ## §3 · Overlay rules Holograms compose by stacking with cleanly separated real estate. The page is the medium; each hologram owns a region of it. A region can be a strip, a card, a panel, an inset, a row, an SVG layer. Two rules govern composition: **One affordance per element.** An element belongs to exactly one hologram. The chip in the filter bar serves the tag-filter hologram; the star in the SVG serves the spatial-map hologram. If both need the same data dimension surfaced (e.g. "principium"), each hologram surfaces it in its own way — the filter shows it as a togglable chip, the map shows it as a node at a position. The two are *coordinated by state* (selecting in one re-keys the other), never by *being the same DOM element*. **Geometry of one is not semantics of another.** If a hologram's positions carry meaning (spatial-map), no other hologram may use those positions as affordances. The captain's eye cannot hold two semantic readings of the same coordinate at once. The constellation viewer is the clean reference: the filter bar (tag-filter hologram) sits at the top, the SVG (spatial-map hologram) sits below, and the right-side panel (detail-inspector hologram) opens on click. Three holograms, three real-estate regions, one page. A chip in the filter bar is not also a star. ## §4 · The omphalos drift · case study `_ops/omphalos.html` is the worked example of welding. The page is good — the cast holds, the captain ratified it, R0 preserves it — and the diagnosis is named here so the next variant has a sharp prescription, not a vague urge. On omphalos.html the **principia chips around the kernel ⊙** simultaneously serve as: (a) **Selection-interface hologram.** Clicking a chip re-keys the page — the accent color shifts, the corpus reorders, the composer's required fields change. That is a categorical filter affordance. (b) **Spatial-map hologram.** The chips are positioned on a ring around the kernel as *orbital stars.* Their geometric position around the navel carries meaning: this is the inner orbit, the operating-principle tier. That is a spatial-map affordance. Both readings are valid; both readings were intended. The captain wanted the page to honor §5 of `OMPHALOS-KERNEL.md`'s reverse-Socratic proposal (chips as orbits as principles) AND wanted the page to function as a working selector for re-keying. The two holograms were **welded onto the same DOM element** — the principium chip is the filter affordance and the orbital position simultaneously. The cost: the chip cannot decide whether clicking is "select this principle as the page key" or "select this principle as the spatially-loaded principle." The captain reads two semantic registers from one click and the two registers fight for primacy. He named the fight: *"you laid them on top of each other and got things all mixed up."* The prescription is not to fix `_ops/omphalos.html` — the page is locked. The prescription is for the **next omphalos variant** (`omphalos.v2.html` or whatever the captain names it) to split the layers cleanly: a filter strip carries the selection-interface hologram, a separate SVG carries the spatial-map hologram, the two are coordinated by state but rendered as distinct regions. The composer (composer hologram) and the side detail (inspector hologram) stay where they are. ## §5 · Hologram inventory per branch The branches and the holograms they currently render. Where a hologram is missing that the branch should use, it is named with `(missing)`; where two are welded, it is named with `(welded)`. - **`omphalos`** (`_ops/omphalos.html`) · spatial-map **welded** to selection-interface · composer · detail-inspector. Next variant splits the weld. - **`mnemosyne`** (`_mnemosyne/mnemosyne.html`) · timeline (recent) · tree (branches list) · spatial-map (branch-map SVG) · selection-interface (HUD key) · detail-inspector (side panel) · composer (register-direction). Clean — five holograms, five regions, no welds. The dock is the reference for multi-hologram composition. - **`mythmatrix`** (`mythmatrix/`) · spatial-map (matrix viewer) · tag-filter (proposed, not yet rendered cleanly) · detail-inspector (missing). The convergence with the constellation viewer's grammar is the next move. - **`triskelion`** + variants (`Principia-Triskelion/`, `Principia-Triskelion 26/`, `Principia-Triskelion-Branchv000/`, `Principia-Triskelion-Branchv001-ical/`) · timeline · tree · detail-inspector · composer (missing for ical-resume; will be supplied by an OMPHALOS-emitted brief). - **`hermeticbusinessparser`** · timeline · tree · tag-filter **inline-anti-pattern** (per `gate-12` check #6) — fire/water/earth/air/aegis baked into row labels rather than exposed as a filter strip. The correction is to lift them into a tag-filter region. - **`shalaco`** (`shalaco.com/`) · spatial-map (`Site-Constellation.html`, `The-Constellation.html`) · tag-filter · detail-inspector. Reference instance for clean three-hologram composition. - **`wfag`** (`Automaton Architecture/Wildfuturesadvancementgroup.com/`) · composer (purchasing console) · cartographic (`master-control.html` TOTK skin) · timeline (LINEBOSS register). - **`hbs`**, **`magickal`**, **`cosmic`** · the latent convergence cluster. Holograms not yet inventoried; the convergence-cast that folds them will pick its hologram set. - **`ptah`** · the skin, not a hologram. Provides CSS variables to every hologram in every branch. - **`principia`** · this branch. Renders through the cyrelium template; no welds. The text *is* the hologram. ## §6 · Lineage This principium pairs with `cosmos-to-converging-branches.md` carved this same iteration. The two cover the orthogonal axes: hierarchy says what a thing IS; holograms say how it RENDERS. Either alone is half the operating frame. - **Back-references** `_principia/executing-as-architecting.md` — *find the existing grammar before inventing.* The eight holograms are the grammar; new ones get named only when the existing eight cannot carry the shape. - **Siblings** `_principia/cosmos-to-converging-branches.md` (this iteration), `_principia/gate-12-drift-detection.md` (the gate that catches inline-tag drift and welded-hologram drift before the captain has to steer). - **Parent brief** `_ops/BRIEF-OMPHALOS-001.md` — drift catalog calls out the *raw-markdown handoff* and the *existing-grammar miss*; both are hologram-level failures, made visible here. - **Walking-distance** `_ops/OMPHALOS-KERNEL.md` (the four cornerstones + ten principia + four-coordinate schema), `_ptah/cyrelium-md-viewer.html` (the canonical skin every hologram inherits). The falsification path: if a future surface is built and none of the eight holograms named here describes it, the inventory is short. The correction is to name the missing hologram in §2 and stamp the page that surfaced it as the reference instance. The principium grows; the rule (overlay but never weld) does not. --- *Sigil:* ⎔ · *Operation:* the page knows which logic owns which region · *Mold:* this document · *Cast:* every viewer in the cosmos that holds two readings without welding them.