AARENA APPLICATION
The web.
Structure, gameplay and native browser behavior remain in the application.
HTMLCSSJavaScriptGame state
- HTML structure
- CSS and visual identity
- JavaScript game logic
- Player and enemy state
- Spawning and scoring
- Game rules
QUETZALCOATL CORECASE STUDY · 01
Interactive
Energetic Arena
A real browser experiment designed to expose the boundary between a normal web application and the Quetzalcoatl runtime.
HTML / CSS / JavaScriptRust / WASMCrystalWebGL2
01
THE QUESTIONWho is actually
Who is actually
rendering this?
The Arena does not contain its own WebGL rendering engine.
It does not manually project DOM geometry into GPU space, resolve energetic relationships or manage Crystal.
The application describes the web. Quetzalcoatl maintains the Universe.
RESPONSIBILITY BOUNDARYTwo systems.
Two systems.
One experience.
BQUETZALCOATL CORE
The Universe.
Nahuales carry energetic and relational state. Rays perturb that state and the runtime resolves the response.
NahualesRaysEnergyRelationships
- Nahuales — runtime entities
- Energetic state
- Relationships
- Interaction Rays — perturbations
- Rust / WASM resolution
- Crystal — projection layer
- WebGL2 — GPU backend
- Demand-driven scheduling
The interesting part
is what is NOT there.
Inspect the Arena source code. The application owns the game. It does not implement the Quetzalcoatl runtime.
It runs through the GPU — without application-level <canvas> setup, WebGL scene code or manual DOM-to-GPU projection.
- No custom WebGL scene engine
- No manual DOM-to-GPU projection
- No custom energetic solver
- No Crystal implementation
- No QC runtime scheduler
The Arena handles HTML, CSS and game logic.
Quetzalcoatl adds the Universe.