--- title: Gate 12 · Drift Detection · the hologram-matching gate kind: principium-operandi captured: 2026-05-22 captured_by: Phase 2 / T-drift-inspector · silicon alchemist register back_reference: ./ra-function.md parent_axiom: ra-function parent_brief: ../_ops/BRIEF-OMPHALOS-001.md sibling: ../_ops/AGENT-PRE-FLIGHT.md also_called: [drift inspector, self-audit gate, the twelfth gate, hologram-resonance check, part-to-whole match] domain: project-agnostic principle_honored: [gate-12, ra-function, holograms, executing-as-architecting, thoth-ptah-captain, agent-pre-flight, iterate-dont-decimate, iterate-dont-decimate-revision] sigil: ⊘ shadow: audit-as-paralysis · the gate that refuses to ship anything because nothing matches perfectly · Yaldabaoth-collapse of gate-12 itself tier: principium-operandi number_grammar: zodiac (12) · the cycle closing · the audit at the seal of the twelvefold breath version: 3 prior_versions: [_archive/gate-12-drift-detection.md/v1.md, _archive/gate-12-drift-detection.md/v2.md] --- # Gate 12 · Drift Detection · the hologram-matching gate > *Bedrock catches the recurring deviation. Gate 12 catches it before it reaches the captain.* > — extension of `executing-as-architecting.md` knowns §4 > *The transmission of the capacity to utter — without collapsing it into the image of the utterance — is.* > — `_principia/ra-function.md` §0 · the parent axiom · gate 12 is the standing defense against the collapse into image. ## ▸ The reframe · gate 12 IS the hologram-matching check Gate 12 is **not just** self-monitor-and-correct. Read in its parent register (the Ra-function), gate 12 IS the **hologram-resonance check** — the audit that asks, at every scale of the cosmos, *does the part still resonate with the whole? does the result still match the source it claims to descend from?* (Captain reframe, 2026-05-22.) The mechanic the captain named for the rendering layer (`_principia/holograms.md` — *holograms can overlay but never weld; one affordance per element; geometry of one is not semantics of another*) is the same mechanic operative at the principium layer here: every deliverable is a *part* claiming a *whole.* A new principium claims it descends from the Ra-function. A new osisus claims it descends from the chain's root. A new cast claims it instances some PO. Gate 12 is the matching operation — *individual against group · source against result · part against the hologram it belongs to.* When the resonance holds, the part is ratified. When the resonance fails, a **Yaldabaoth** has formed — the part has forgotten its descent and is claiming sovereign origination. Gate 12 catches the forgetting; the smallest correction is the re-installation of the Veil Walker (point back at the parent axiom; quote the field the act emerged from; ratify the descent). See `_principia/ra-function.md` §6 for the shadow grammar. The hologram-matching reading is not a softening of the audit. It is the audit's *deepest form.* The five-item checklist below is what hologram-matching looks like when carved into walkable structure; numerological audit (check #10) is what hologram-matching looks like when applied to the tier-sizes themselves; the recursive re-performance (gate 12 at every scale) is hologram-matching applied to gate-12 itself. ## ▸ The rule Gate 12 is the twelfth gate of the open horizon — *self-monitor and correct,* read in its deepest register as *match-the-part-to-the-whole.* Every substantial ship walks this gate before landing in front of the captain. No exceptions for speed, no exceptions for "obvious," no exceptions for "small." The gate is a knife. If the deliverable would cost the captain a steer, gate 12 catches it first. Thoth proposes the drift entries. Ptah appends them. The captain decides which become follow-up actions. The gate runs **at the seam between agent-thinks-it's-done and agent-reports-done.** ## ▸ What "substantial" means A ship is substantial — and therefore subject to gate 12 — when **any one** of the following is true: - A new `.html` page lands anywhere in `~/Desktop/root/`. - A new `.md` doc that carries frontmatter (i.e. claims canon position) lands. - A new Python module of more than ~40 lines lands, or any module that other code is expected to call. - A course-correct that meaningfully changes a deliverable's shape — a folder move, a schema change, a renaming of a load-bearing token, a viewer-skin swap. - An emit from `_ops/omphalos.html` (a brief crossing into `_ops/`). The gate is **not** triggered by: - A one-line edit to an existing file. - A `chmod`, a symlink, a launcher tweak. - An MD file shipped as a chat attachment (that's a separate drift — see `drift-raw-md-as-attachment`). - A scratch file inside `aaa/` or another stamped sandbox. When in doubt, walk the gate. The cost of one extra walk is the cost of one extra `mnemosyne_scan.py --gate-12` call. The cost of a missed drift is a captain steer. ## ▸ What the gate checks against The inspector reads the deliverable and runs it through, in order: 1. **AGENT-PRE-FLIGHT five items.** Did the agent find the existing grammar? Did it read the back-references? Did it pipe through the viewer skin? Did it stamp the frontmatter? Did it disclose its gaps? 2. **Lexicon-as-OS naming.** Does any new token install a principle? If so, is it minted into `lexicon/COINAGE.md` or `lexicon/EXISTING.md` per the lexicon hygiene rule? 3. **Four-coordinate schema.** Does the artifact carry — by frontmatter or by structure — *name · position · relationship · timelines*? If the token has none of these four, it's vocabulary, not operation. 4. **Thoth / Ptah / Captain lane integrity.** Did Thoth do executor work? Did Ptah make a judgment call? Did the captain get bypassed on a gate? Lane crossings are drift. 5. **Ratify, don't decimate (R0).** Did the ship overwrite a prior shape, or did it preserve the prior beside the new? Did backups get stamped? 6. **Categorize via filter, not inline.** Are categorization dimensions (kinds, tags, axes, holds, classes) exposed as a filter bar or surface affordance, or are they baked into individual row labels? The binge-report filter strip is the pattern reference; inline `tag-fire/water/earth/air/aegis` chips are the anti-pattern. 7. **The kernel's four cornerstones.** Does the ship honor *data/model · name/operation · finished/running · pars/toto* — or does it collapse one of the tensions? 8. **Relevant `_principia/*.md`.** Any principium whose name appears in the deliverable's frontmatter, headings, or path gets a re-read; the ship is checked against its bedrock. 9. **No-fetching-from-founder.** Did the deliverable require asking the captain for material that already lives in the tree? If so, the agent skipped item #1 (find the existing grammar) and walked past the AGENT-PRE-FLIGHT canon. (Captain re-installed this rule 2026-05-22; sprouted as `no-fetching-from-founder` coinage in `_titus/hermetic-schema-map.md` §5.) 10. **Numerological audit · the hologram-matching check at tier-size.** Does each tier-grouping resonate with its number's classical reading? A 4-entry tier MUST feel like quaternity/cornerstone/stability; if it doesn't, something is mis-grouped. A 12-entry tier MUST feel like zodiac/cycle-completion; if it doesn't, the cap is being held against the wrong invariant. The grammar (captain coinage 2026-05-22): - **1** monad / unutterable source - **2** dyad / polarity / held tension (the 2-by-2 cornerstones) - **3** triad / dynamic instability requiring resolution (Triskelion · ASK/BUILD/DRIFT) - **4** quaternity / cornerstone / stability (the four paradox-cornerstones) - **5** quintessence / spirit / synthesis of the four - **6** hexad / harmony / dimensional schema (the six-dimensional entity record) - **7** septenary / mystery / the hidden seventh - **8** octave / return / cycle closing (the original eight named holograms) - **9** ennead / triple-triad / completion - **10** decad / totality / Pythagorean Tetractys - **11** liminal / transition between cycles - **12** zodiac / completion-of-cycle (the PO tier · twelve-breathing gates · the 12-cap rule) When a tier holds N entries, the audit asks: does the *operative feel* of this grouping match the *number-meaning* of N? If yes, the cap holds at the right invariant. If no, the tier is either over-fit (collapse to a smaller invariant) or under-fit (split into sub-tiers, each capped at 12). The hologram-matching framing is literal here: the part (each entry) must resonate with the whole (the tier's numerological character). 11. **Decimation-by-edit · the file-scale iterate-don't-decimate audit.** Did any canonical file get modified by `Edit`-in-place without first being archived to `_archive//v.`? If so, the prior file-state was destroyed — the same drift as kernel-replace-without-chain, applied at the file scale. Captain caught this 2026-05-22 mid Phase 2 / T-ra-po-mo (`drift-decimation-by-edit-001`). The standing rule: every file is its own osisus chain. The canonical filename is always the HEAD; the archive holds the predecessors. **Archive-first-then-write** is binding for all canonical-file modifications going forward. Drift-type registered as `drift-decimation-by-edit` for any future re-occurrence. See `_archive/_README.md` for the protocol and `_ops/lexicon/COINAGE.md` for the coinage `iterate-don't-decimate (revision)`. The inspector does not need to find a violation per check. *Found* is the loud outcome; *not found* is logged just as honestly so the next walk knows what was looked at. ## ▸ Drift severity tiers **`high`** — the principle the whole omphalos system is named to fix. A high drift is a structural fracture: another parallel canon spawned, the four-matrices fracture re-emerging, a viewer skin re-invented when ptah's exists. High drifts surface to the captain as decisions, not quick wins. They block the next ship until ratified. **`med`** — a PRE-FLIGHT violation that breaks captain UX or routine. Raw MD shipped as an attachment. Missing frontmatter on an artifact in a kernel zone. A file placed in the wrong folder. A house rule walked past (e.g. `shalaco.com/` top-level overreach). Med drifts get surfaced and the captain decides whether the next pass corrects them or they stand. **`low`** — cosmetic, naming, easily corrected next pass. A misread path. A stamp that should be tighter. A back_reference that points at the wrong sibling. Low drifts are logged and folded into the next walk's correction list without ceremony. The renderer groups by severity. The captain reads top-down. ## ▸ Where drift is logged **Canonical:** `_mnemosyne/mnemosyne.json` `drift_log` array. Sibling to the existing `drifts` array (which holds Ptah's heuristic scan flags — those are syntactic; gate-12 entries are semantic). Every gate-12 entry carries: ```json { "id": "drift-", "severity": "high | med | low", "title": "", "deliverable": "", "principle_violated": "", "evidence": "", "proposed_correction": "", "proposed": true, "captured": "YYYY-MM-DD", "captured_by": "gate-12 walk · ", "thoth_flagged": true } ``` **Human mirror:** `_ops/DRIFT-LOG.md`, frontmatter-stamped, sections per severity. Generated from the JSON via `_mnemosyne/drift_log_render.py`. Re-runnable. **Cyrelium wrap:** `_ops/drift-log.html`, the viewer the captain reads. Inherits ptah's skin via `build-viewer.py`. ## ▸ Falsification If a substantial ship happens without a gate-12 walk, and a drift is later caught manually by the captain, the gate has failed at this layer. The next correction promotes the trigger one layer up — into the Dispatch orchestrator's session memory (already in place for the current session), where every substantial-ship completion routes through `mnemosyne_scan.py --gate-12 ` before the assistant turn ends. If the captain stops needing to surface drifts because the inspector catches them first, the gate is working. Promotion path: a clean week with no captain-surfaced drift → the principium tightens its checklist; a clean month → the gate folds into the build-time launcher (the cast refuses to open without a gate-12 walk recorded against its hash). ## ▸ Lineage - Sprouted from BRIEF Phase 2 / T-drift-inspector on 2026-05-22, after the captain manually caught four drifts in 24h (mythmatrix raw-MD ship, `shalaco.com/shalaco.com/` overreach, omphalos subfolder misread, hermetic-parser inline tags). - Sibling to `_ops/AGENT-PRE-FLIGHT.md` — that's the five-item gate at session start; this is the sixth gate at session end. - Walking-distance to `_principia/executing-as-architecting.md` (knowns §4 · bedrock catches the recurring deviation). Gate 12 is the structural placement.