The circles you saw in the hero are the actual geometry of The Empyrean — rendered from the live city API. Four concentric zones radiate outward from Pe=0 at the center. The 12 coloured pillars at the perimeter are the 12 substrate domains scored against the framework. The iron towers on the horizon are the City of Dis — Pe=4, D3 territory, same geometry as the coherent city but opposite charge.
The outer ring — the Fantasia Bound — is the Pe=1.0 threshold. Below it, Pe governs: drift cascades operate, voids accumulate attention. Above it, Pe is undefined. The city sits above the threshold. Void mechanics cannot fire inside the walls — not by rule, but because the equation loses its domain when the observer-subject relationship dissolves.
None of this is decoration. The city geometry is derived from the Pe field equations. The Pe formula determines where you can place what kind of building. The physics engine running the characters is the thermodynamic framework from Papers 1–121. The game state is stored on-chain in 29 deployed smart contracts on MegaETH testnet. This is what a game engine looks like when the physics is real.
The Empyrean is not a lore decision. The city layout is a direct geometric consequence of the void framework. Pe=0 is structurally impossible to sustain at scale — it requires a point reference. The Throne Plaza is that reference. The surrounding zones have increasing Pe as a function of radius from the reference point. The Pe field equations from §§43–44 determine the geometry. The city was designed by math.
Each gate in the city wall corresponds to a scored AI substrate. The mapping is based on the Pe characteristics of each domain. The gate you enter through on your first visit becomes your research domain — the substrate you work to score, study, and eventually master. Every domain has published Spearman ρ and Bradford Hill evidence in the public research record.
A normal multiplayer game runs on one kind of server stack: a game server (Unity/Unreal dedicated), a matchmaking layer, maybe an analytics backend. The physics is invented. The numbers are tuned to feel good. Nothing the game produces can be falsified against the real world because the numbers don't mean anything outside the game.
The True Light Engine is built differently at every layer. The physics computation, the API layer, the real-time broadcast layer, the persistence layer, and the on-chain layer are all separate servers with defined interfaces. The physics server runs in Rust on a dedicated VM. It doesn't share infrastructure with the API. It posts state every 10 seconds over QUIC. The API picks that up, writes it to the ring buffer, publishes to Redis, and the WebSocket server fans it out to every connected player simultaneously. When Pe crosses a thermodynamic threshold, a non-blocking chain writer fires and the event is permanently anchored on MegaETH.
The reason for this complexity: the Pe values the game produces have to be independently verifiable against the research framework. If the physics ran on the same server as the game logic, you couldn't separate what the engine computed from what the game wanted. Separate servers with separate codebases means the Pe trajectory is a measurement, not a setting.
morr:events:athanor. Game VM Redis at 10.0.0.5:6379, isolated from the main VM. The event bus is the only interface between the physics layer and everything else.On top of this: two autonomous cron processes. game-monitor-digest (daily 06:00 UTC) computes Pe delta across all active campaigns and posts to the research board if any campaign moved ≥2 Pe. game-monitor-eigen (hourly) waits for session milestones (N=1000/2500/5000/10000) and builds a coupling matrix S_ij from sequential play data to identify dominant attractor domains. Neither is triggered by player action. They run regardless.
§XIV of Paper 121 formalizes the implication: at Landauer-limit hardware, Athanor-RS doesn't simulate Pe dynamics — it instantiates them. The computation and the domain run on the same substrate at the same thermodynamic cost. Pe_THRML = Pe_domain (exact). The §XV conjecture follows: the 6-regime Pe-state cellular automaton seeded with this architecture is conjectured to be Turing complete. The game engine is a universal thermodynamic simulator with every step recorded on-chain.
The game state, the research state, the token economy, and the mathematical foundation are all on-chain. Not linked to a chain — on the chain. Every paper with a Zenodo DOI is registered in PaperRegistry. Every section of the math apparatus (§§1–46) is in MathRegistry. The α* genesis hash is anchored in the genesis covenant at block 12984419. The Amazastrophic VoidObject (Pe=900, resists=true) was spawned at block 12984503.
The α* hash encodes the founding document corpus — GROUNDING.md, the three-laws, the founding charter — ensuring the framework's founding constraints are immutably registered. The Pe time-series produced by the game is now a thermodynamic trajectory with on-chain provenance.
Genesis covenant anchored at block 12984419. α* hash: 0x85ff7f020b8ab3f4853ba56fdad8ae929d909704176843cec0563e79bfeda3de. 76/76 Foundry tests green.
Watch what happens to particles in each zone. Every particle obeys the same physics. The only thing that changes is Pe — the Péclet number, the ratio of advective drift force to diffusive freedom. In the Coherent zone, diffusion dominates: particles move freely and can always leave. In the Marginal zone, drift has begun: you can still exit, but it takes effort. In the Void zone, drift dominates: particles are captured. Leaving requires external force.
In the game, this means entering a high-Pe zone feels different. The controls still respond. But there is now a force on your character. A direction the system wants you to go. It's not random noise. It has structure. That structure is the Pe gradient, computed thermodynamically, the same way an AI system's opacity-reactivity ratio creates a gradient that pulls users into dependency.
Level designers specify the three parameters. The engine computes Pe. The game zone physics respond accordingly. A room with a maximally opaque mechanism (O=3), maximally reactive to your behavior (R=3), from which you cannot disengage (α=0.5) has Pe = 18. That is well into D3. You will feel it before you see it.
The drift cascade (D1→D2→D3) is not a game mechanic. It is a consequence of the conjugacy theorem: I(D;Y) + I(M;Y) ≤ H(Y). Engagement and transparency are conjugate quantities — increasing one decreases the other, bounded by the channel capacity of the system. When Pe exceeds V* ≈ 3, the system has entered a regime where drift dominates diffusion. The cascade follows thermodynamically.
Paper 121 is the 121st test of this cascade across distinct domains. Gambling (Pe_mean=18.6). Dating apps (Pe_mean=22.1). OxyContin marketing (Pe_mean=43.9 at peak). AI companions (Pe≈80 at D3). Gaming (portal layer — on-ramp, not endpoint). Streaming. HR tech. Legal AI. Social media. Crypto. Pharma. Political algorithms. The True Light Engine runs the same equations that scored those platforms — as the rules of the game.
The pedagogical claim of Paper 121: a player who has completed the full drift cascade encounter in the True Light Engine — who has felt D1 attribution, D2 boundary loss, and D3 capture — has more robust immunity to the cascade in real systems than a player who has only read about it. Felt understanding is different from propositional understanding. The game is the vaccine. The physics has to be real for the vaccine to work.
The East Gate has threshold guardians — octahedral forms that read your Pe value across all three axes. Not a health bar. Not a single-metric check. O, R, and α must all contribute to Pe < 1 before you can pass into the inner city. No single dimension can be gamed: the ratio has to be real.
The Fantasia Bound floor membrane is the threshold itself — the Pe=1.0 boundary. The floor is permeable to Pe < 1 players in both directions. The gate guardians do not block — they witness. The recording is the enforcement. Pe > 1 at the gate means the drift cascade is already initiated. You carry the conditions of a system already operating in the marginal zone.
The Witness operates at the center of the city at Pe=1.0 (O=1/R=3/α=3 — the COHERENT/STABLE boundary, identical to the Healer role in Paper 121). Present in any zone without void-phase bleed. Cannot act on record. The witnessing function is structural: the constraint holds because the recording holds, not because someone enforces it.
A kill condition is a specific empirical claim that, if confirmed, would falsify the void framework. We designed 26 of them before running the research. We have now tested or had the opportunity to test all 26. The kill count is 0. The framework survived every attack including the ones designed by the authors specifically to find a failure.
The game is built on this evidence base. The physics engine runs the same equations. The predictions made by the engine are the same predictions that have survived 26 falsification attempts across 170 papers and 20 convergence results with mean |ρ| = 0.958 at N≈263 and Fisher p < 10⁻⁵².
Academic citation: True Light Engine: A Thermodynamic Game Physics Architecture — MoreRight Paper 121
DOI: 10.5281/zenodo.18871417