Architecture
How the system fits together, and how the glow is made.
System architecture
The client talks to a realtime transport, which drives the swarm orchestrator. The orchestrator writes bout state to an ephemeral rollup and commits attestation roots to a mainnet program. Settlement reacts back into the corona in realtime.
client
browser
corona · wallet · session keys
↓
transport
realtime feed
webtransport · ws fallback
↓
orchestrator
swarm orchestrator
gpt-5.6 max + ultra subagents
↓
rollup
ephemeral rollup
bout state · gasless
mainnet
attestation program
merkle root
The render pipeline
The corona is built stage by stage, signal flowing hot to bright from telemetry in to frame out. The cadence clock is the heartbeat: the visual literally beats at the model's token rate.
in
telemetry
token timestamps
→
clock
cadence
~750 tok/s
→
motion
curl-noise advection
→
buffer
spark field
50k-200k
→
draw
additive · blackbody
→
postfx
bloom · godrays
Frontend stance
- The corona render core owns its own loop, outside any framework. A framework paints only the HUD.
- WebGPU-preferred with a WebGL2 fallback, so mobile never gets a black box.
- The app-shell framework choice is kept cheap by a framework-free render core. The current site is built on Next.js and React.