Pick the rail you want to light up.
This is the world-console version of the public surface: pricing, proof, arena, voxel, and discovery all wired together so the product can feel alive on first contact and useful on the second.
World surfaces
Each rail should feel like part of the same authored system, with enough proof to trust and enough motion to stay memorable.
Cash rail
Keep pricing, proof, and support on the same visible lane.
The product feels more real when a buyer can move from proof to pricing without disappearing into a form maze.
- Hosted checkout
- Walkthrough fallback
- Live wins nearby
Launch floor
Operate the whole surface like a rail yard instead of a brochure.
The public site, the 9-bit arena, the voxel rail, and the operator proof should feel like one world with multiple doors.
- Shared control room
- World links
- Static export ready
9-bit arena
Give the site a playable proof instead of empty futurism.
The web game is a fast, linkable proof of deterministic input, palette, and mood. It turns abstract operator energy into something you can feel.
- Browser-first
- Shareable links
- Portal UI
Voxel rail
Keep the Minecraft-style lane one tap away from the operator copy.
The voxel path is the more social, witnessed lane. It belongs beside the public surface because both are really about making a rail feel alive.
- WebSocket path
- Witnessed play
- Same-origin proxy
Runbooks for repeat visits
Return visitors usually want a faster path. These runbooks keep the public rails legible without flattening everything into one generic CTA.
First contact
Lead with public proof before you ask for trust.
Open wins first when the user needs evidence that the rig is active, then hand them pricing only after the surface feels obviously operated.
- Open live wins and show one real signal.
- Move to pricing with the same browser session and the same voice.
- Offer walkthrough or opt-in only after the proof lane lands.
Playable proof
Let the weirdness land in a browser instead of in copy alone.
The 9-bit arena and the voxel rail are not side quests. They are the fastest way to make the public surface feel authored rather than generic.
- Drop people into the arena if you need fast motion and spectacle.
- Use Voxel MP when the point is witnessed presence and shared rails.
- Bring them back to launch floor so the site and the worlds stay connected.
Return path
Keep repeat visits feeling like a resumed mission, not a cold reload.
A useful front door remembers where the operator was headed: proof, pricing, game, voxel, or a quieter discovery lane.
- Keep launch floor reachable from every page.
- Put the active rails in one compact status band.
- Export the same structure to static files so the public mirror stays coherent.
Launch floor console
Proof should be compact, directional, and connected to action.
Operator proof
team_first
Payment rails
crypto
Walkthrough queue
1
Runtime board
origin / api / arena / voxel
What changed
Less brochure. More world.
The launch floor gives the Python public surface a stronger identity spine: one place to move between CodePulse, the 9-bit arena, Voxel MP, discovery pages, and proof without losing narrative continuity.
Deploy shape
Static export is part of the product now.
The same script can render the public pages into static files for the Caddy-served mirror. That means the public mirror no longer has to trail behind the live origin when the Python surface improves.
Why this matters
Identity carries trust.
A site that contains its own proof, worlds, and next actions reads as operated. A site that hides all the interesting rails behind plain pricing copy feels forgettable.