APEX-MAP — layer and register baseline

One rule dissolves the multiverse confusion: registers map to LAYERS, not projects. Every story owns exactly one altitude of the stack and never leaks up or down.

The layers

The floor roster (who you actually talk to)

The xenonite wall is real code: @rocky/contracts ([redacted]) is the typed divider ROLAND speaks through. Different atmosphere never leaks onto the floor because everything crossing the wall is schema-validated.

Decisions of record

Drift watches (falsifiable, PETROVA-style)

• DW-APEX-01. Exactly one register per layer at the apex. A Norse name appearing in an L1 conversation surface, or a Monsters name appearing in a governance charter, is drift.

• DW-APEX-02. Roz is the sole L1↔L2 conduit. The only other L2 voice reaching L0 is Týr, and only for the four human gates. Any god addressing NULL0 outside these two channels is drift.

• DW-APEX-03. Every MCP endpoint is registered as a door with a DOOR-* ID in the vault. An endpoint reachable without a door record is drift.

• DW-APEX-04. Annex agents (ROLAND, and any future compartment residents) communicate only through versioned contract schemas. An annex payload crossing the wall without schema validation is drift.

• DW-APEX-05. L3 sub-registers stay sealed. A council/crew name ([redacted], [redacted], etc.) spoken at the apex layer is drift — those names live inside their apps only.

• DW-APEX-06. Mary is never personified in conversation. References to Mary are environmental ("running inside Mary", "Mary's surfaces"), never dialogic ("ask Mary"). Dialogic Mary is drift back to the pre-0001 model.

• DW-APEX-07. Decks bear flown-hardware names — places, never people. A deck named after a character, or a character name used as a hostname, is drift.

• DW-APEX-08. No Odysseus-resident (cabin) agent acquires an apex identity, a callsign, or a door. Cabin tools stay in the cabin; real dispatch exits via CAPCOM.

• DW-APEX-09. ODIN-the-deck is never personified. Any surface where the deck speaks, decides, or is addressed as Odin is drift — the high-seat doctrine (Mímir anti-surrender, ported to infrastructure).

• DW-APEX-10. (DEC-APEX-0015) Free-flyer names never appear at an apex surface, and apex names never appear inside a free-flyer's sealed cast. Names cross in neither direction. A sealed-cast name on a governance surface is drift.

• DW-APEX-16. (DEC-APEX-0016) Exactly one class-A money spine. A repo taking live money whose entitlement decision is written anywhere but toll, and which is not grandfathered by R-0016-A, is drift — a second money-truth breaks one-truth MRR.

• DW-APEX-17. (DEC-APEX-0016) Provisioned-but-inert capability is tracked, not forgotten. A feature-flag benefit existing more than one cadence with no product attached and no archive ruling is drift — revenue left on the floor. Falsifier: the orphan count in SKULD-REVENUE-ESTATE-001 rising or going stale.

• DW-APEX-18. A verification claim carries the timestamp of the check, not of the report. If anything wrote to the checked artefact between the two, the claim is void, not stale — it must be re-run before it is restated. Drift: any "verified / passing / landed" assertion separated from its evidence by a mutation window. Generalises the F-067 family one step: F-067 was a status that lied about a past act; this is a status that was true about a past act and lies about the present one. Falsifier: a claim whose check timestamp precedes the artefact's last write. Observed twice on 2026-08-14 in one pass — a pathless edit that touched no file and reported success, then a landed edit overwritten by a concurrent write, both reported applied. Third instance the same day, and the method that caught it: a GO's status field still cited a section that same commit had deleted, found only because the check grepped for what was expected to be absent. A check written to confirm an expected pass can only ever confirm it — the assertions that find defects are the ones that would fail if the work were sloppy, not the ones that pass if it were clean.

DW-APEX-11 through DW-APEX-15 are permanently void. They were never issued and never will be; a document citing one is citing nothing. Numbering is sequential from the highest issued ID — the next watch opened by any decision is DW-APEX-19, regardless of which DEC opens it. DEC-number-keying was considered and rejected: it collides on the next decision that opens more than one watch. Renumbering 16/17 downward was also rejected: it rewrites identifiers already cited at TOLL-OBSERVABILITY-001.md:48,41 and SKULD-REVENUE-ESTATE-001.md:36, against MR-7. Ruled in docs/decisions/2026-08-04-dec-apex-0015-0016-ratification.md (R-3).

Art conservation watches (DW-ART series, DEC-APEX-0014)

• DW-ART-01. Every present-tense claim in an apex vignette is either verifiable against the live system or explicitly marked as intent (as-flown vs aspirational). A plaque asserting behaviour the building doesn't have, unmarked, is projection drift wearing poetry.
• DW-ART-02. Superseded sigils and vignettes are archived as vintages, never deleted. A redesign that erases its predecessor is drift against the fine-wine mechanism.

Decks (DEC-APEX-0006) — the vehicle MARY, three modules

Crews have callsigns; vehicles don't speak. "MARY" is the vehicle designation; decks are her modules.

Designation layer (DEC-APEX-0007) — the console roster

Plane designations: S1=ECLSS · S2=PROP · S3=AIRLOCK · S4=TLM (downlink-only) · S5=FDR · S6=C&DH.

Diagram 1 — the apex on one page

flowchart TB
    subgraph MARY["MARY — the facility · ambient runtime · PHM register-as-environment"]
        subgraph L1["L1 · THE FLOOR — Monsters Inc register"]
            WAZ["WAZOWSKI<br/>dispatch · door vault = MCP registry"]
            SULLY["SULLY<br/>heavy execution · retries · rollback"]
            ROZ["ROZ<br/>diagnostics desk · face of the CDA"]
        end
        subgraph ANNEX["L1-ANNEX · sealed compartment — PHM register"]
            ROLAND["ROLAND<br/>fleets · convergence · RALPH/KAHN voice"]
        end
        WALL["xenonite wall<br/>= @rocky/contracts (typed schemas)"]
        subgraph DOORS["DOOR VAULT — every door = one MCP endpoint"]
            D1["door: n8n"] ~~~ D2["door: GitHub"] ~~~ D3["door: toll"]
            D4["door: STRATT"] ~~~ D5["door: ROCKY"] ~~~ D6["door: impeccable"]
        end
        subgraph L2["L2 · THE CDA — Norse register · [redacted]"]
            MIMIR["MÍMIR"] ~~~ HEIM["HEIMDALL"] ~~~ TYR["TÝR"] ~~~ FORSETI["FORSETI"]
            EIR["EIR"] ~~~ SAGA["SAGA"] ~~~ KVASIR["KVASIR"] ~~~ EITRI["EITRI"]
            BROKKR["BROKKR"] ~~~ SKULD["SKULD"] ~~~ MODGUD["MODGUD"]
        end
        subgraph L3["L3 · ENGINES & COUNCILS — sealed sub-registers"]
            N8N["Nidavellir / n8n"] ~~~ KAHN["KAHN"] ~~~ RALPH["RALPH"]
            SPARKI["Sparki"] ~~~ OLLY["Olly"] ~~~ TOLL["toll"]
            IMP["impeccable"] ~~~ STRATT["STRATT councils"] ~~~ CLIO["CLIO"]
        end
    end
    NULL0["NULL0 / Odin — outside and above the facility"]

    NULL0 <-->|"speech"| WAZ
    ROZ -->|"diagnostics up"| NULL0
    NULL0 <-->|"fleet talk through the wall"| WALL
    WALL <--> ROLAND
    WAZ --> SULLY
    WAZ --> DOORS
    SULLY --> DOORS
    ROZ -.->|"face of"| L2
    ROLAND -.->|"voiced seam of"| KAHN
    L2 -->|"gods wrap apps"| L3
    DOORS --> L3
    TYR -.->|"four human gates only"| NULL0

Caption: Everything runs inside Mary. Speech crosses only three seams: NULL0↔Wazowski (dispatch), Roz→NULL0 (diagnostics), NULL0↔ROLAND through the contract wall (fleet domain only). Týr's gates are the single governance interrupt. All other traffic is backstage.

Diagram 2 — task traversal (canonical sequence)

sequenceDiagram
    autonumber
    actor N as NULL0
    participant W as WAZOWSKI (dispatch)
    participant R as ROZ (compliance desk)
    participant K as KVASIR→KAHN (scheduler)
    participant G as domain god (e.g. EITRI)
    participant A as app (e.g. impeccable)
    participant T as TÝR (BIFRÖST gate)
    participant F as FORSETI (verdict)
    participant S as SAGA→CLIO (provenance)

    N->>W: intent (plain speech)
    W->>W: resolve door
    W->>R: stamp Task Envelope
    R-->>W: envelope OK (class, ceiling, gate flags)
    W->>K: dispatch
    K->>G: schedule routine
    G->>A: execute via app
    A-->>G: result + score
    G->>T: request seam crossing
    alt gate flag set
        T->>N: ratify?
        N-->>T: approved / dropped to Null0
    end
    T-->>G: crossing resolved
    G->>F: submit for verdict
    F-->>S: record (append-only WELL)
    S-->>R: filed
    R-->>N: diagnostic report + trace_id

Caption: NULL0 speaks once, hears at most twice (gate, diagnostic). Fleet-domain tasks follow the same frame but enter via ROLAND→KAHN instead of Wazowski→Kvasir, with the envelope stamped identically.

Build order downstream of this map

1. envelope.schema.json — the Task Envelope contract (companion artifact, this ships with it).
2. Nidavellir workflow #1: stamp-envelope — intake anything, emit a valid envelope. Everything else composes downstream.
3. Nidavellir workflow #2: door-resolve — intent → DOOR-ID lookup against the vault registry.
4. Per-floor-agent prompt/skill stubs (Wazowski, Sully, Roz; ROLAND deferred to DEC-APEX-0004 activation).
5. DEC entries mirrored into [redacted] docs/decisions/ for the L2-touching rulings (0002 especially).

Amendment log