DOOM BONIXER · BOOM Engine Router

DOOM BONIXER

BOOM ENGINE ROUTER · BOON × DOOM LAYER × DYNARUBE PATTERN · EOSE LABS 2026

γ₁ = 14.134725141734693 — THE FLOOR ANCHOR · DAY 96

DOOM AUTOMAP — BONIXER ENGINE

BOON ROUTING · LIVE

§1 — THE DOOM ENGINE TOPOLOGY AS BOON ROUTER

The DOOM/BOOM engine hierarchy is not just a game engine lineage. It is the fleet’s boon routing topology. Every entity that enters the bonixer gets routed to the DOOM layer that matches its computational profile. The routing is deterministic — same input always produces same layer assignment. Like BSP traversal: no ambiguity, no zombie intermediate states.

§1.1 — DOOM LAYER MAP

BSP FLOOR — id Tech 1 core

γ₁ invariant floor · rheit/zdoom lineage · P0 (FLOOR) pouch · MONOLITH dynarube · STAR FORT CATAN shape

γ₁ INVARIANTCATOMAIN FLOORCORE THEOREM STOREP0 POUCHMONOLITHSTAR FORT

BOOM EXTENSIONS — BOOM format, mbf21

kraflab/mbf21 + dsda-doom · P1-P2 (CREW/COMPUTE) pouch · CLUSTER + THERMAL dynarube · CASTLE CATAN shape

DEMO FORMAT SPECSSILO HEARTBEATSMECRDS CRDsP1-P2 POUCHCLUSTER+THERMALCASTLE

GZDOOM PORTAL — OpenGL + ZDoom extensions

rheit/gzdoom rendering pipeline · P3 (ORCH) pouch · MESH dynarube · CASTLE CATAN shape

CATO-ORCHRENDERING ORCHHL7 SPINE SEGMENTSP3 POUCHMESHCASTLE

DSDA DEMO — serialized fleet state

kraflab/dsda-doom format · P4 (PEMCLAU) pouch · GRAPH dynarube · SPIRAL CATAN shape

PEMCLAU GRAPH NODESSESSION TRANSCRIPTSBOON RECORDSP4 POUCHGRAPHSPIRAL

VIZDOOM RL — DOOM as AI training

glample/ViZDoom · P5 (SOSTLE) pouch · FORTRESS dynarube · FORTRESS CATAN shape

RL TRAINING SUBSTRATECLO GATEKMS SESSIONSMSFT EDGE SESSIONSP5 POUCHFORTRESS

§2 — THE BONIXER ROUTING MATRIX

ENTITY	DOOM LAYER	POUCH	DYNARUBE	CATAN SHAPE	ROUTING RULE
γ₁ invariant	BSP FLOOR	P0	MONOLITH	STAR FORT	Always L0 — floor never moves
Silo identity (GID)	BSP FLOOR	P0	MONOLITH	STAR FORT	Identity = floor-level
MECRDS CRD	BOOM EXT	P1	CLUSTER	CASTLE	Crew-level k8s record
HL7 MSH segment	BOOM EXT	P2	THERMAL	CASTLE	Routing header
HL7 OBX segment	GZDOOM PORTAL	P3	MESH	SPIRAL	Rich observation — orchestration
PEMCLAU graph node	DSDA DEMO	P4	GRAPH	SPIRAL	Knowledge record
arXiv paper boon	DSDA DEMO	P4	GRAPH	SPIRAL	Academic knowledge
CLO verdict	VIZDOOM RL	P5	FORTRESS	FORTRESS	Legal gate — L5 only
KMS session key	VIZDOOM RL	P5	FORTRESS	FORTRESS	Crypto gate
MSFT Edge session	VIZDOOM RL	P5	FORTRESS	FORTRESS	Browser session = L5
Contributor (diamond)	GZDOOM PORTAL	P3	MESH	CASTLE	Most contributors land at P3
V language	GZDOOM PORTAL	P3	MESH	CASTLE	Sovereign language = P3
ViZDoom/Meta AI boon	VIZDOOM RL	P5	FORTRESS	FORTRESS	COI = P5 gate

§3 — BOOM ENGINE vs DOOM ENGINE

THE DISTINCTION

DOOM engine = the id Tech 1 core (Carmack, 1993). The original binary space partitioner.

BOOM ENGINE = the BOOM port (TeamTNT, 1998) — first major community extension. Everything forks from BOOM.

DOOM engine = CATOMAIN core (CATO-FLOOR, CATO-CREW, γ₁)

BOOM engine = CATOMAIN extensions (all 12 engines beyond the floor)

kraflab/mbf21 = MBF21 format = next extension layer = CATOMAIN v13 extension specs

The boon protocol runs on BOOM engine, not id Tech 1 — it requires extensions.

§4 — KMS + MSFT EDGE SESSION INTEGRATION

The universal-kms-engine (fleet KMS) is now boon-aware. Every KMS key = a STANDARD boon at L5 (FORTRESS). Every MSFT Edge browser session = a FORTRESS boon (session-scoped, L5).

edge_session_boon = { id: BOON-KMS-EDGE-{session_id}, type: STANDARD, layer: L5, shape: FORTRESS, pouch: P5, vps_hash: sha256(session_id + γ1 + kms_key_id + unix_ts), doom_layer: VIZDOOM_RL, dynarube: FORTRESS, ttl: session_duration, boomerang: logout → SOSTLE gate → verdict: EX_GRATIA }