Overview
Heimdall is the coworking Remote Gaming Server (RGS) for Lindeier.at. Where the
Eyes of Argus demo shipped with a single-game mock RGS bound to one game's
books, Heimdall generalises that into a registry: it watches a shared
/games/ directory, detects which builds are marked online, loads
their pre-computed books, and serves every game through one standardised
/wallet/* protocol.
The intent is collaborative. A developer builds a slot, pushes it to a Git
repository under games/<gamename>/, and the build syncs to the
VPS. Once the game's manifest reports it as online, Heimdall picks it up
automatically, generates a tile for it in the admin grid, and makes it playable
in an embedded frame — no per-game server, no manual wiring.
Design Philosophy
Heimdall keeps the strict separation of concerns used across the platform: the math layer (offline simulation that produces books) never touches the serving layer, and the serving layer never touches presentation. The frontend of each game is a dumb renderer for a server-decided outcome — it asks Heimdall for a round and animates exactly what comes back.
The one boundary that matters most is the split between the financial summary of a round (bet, win, balance — fixed, boring, predictable) and the presentation events of a round (reveals, gaze beams, free-spin triggers — fully dynamic and game-specific). Holding that line is what lets a game add new features without Heimdall ever needing to understand them, and what would make a future move onto a commercial aggregator a re-point rather than a rewrite.
Technical Architecture
Heimdall is a Python service following the same shape as the rest of the stack.
It exposes the four-endpoint RGS protocol established by Eyes of Argus —
/wallet/authenticate, /wallet/play,
/wallet/end-round, and /wallet/balance — with amounts
as integers carrying six implied decimal places.
On top of that protocol sits the registry. Each game directory carries a manifest
describing its identity, cover image, and online status, plus a
published_books set: the index.json mode manifest, the
compressed book files, and the lookup tables that weight round selection. Heimdall
reads the manifest, loads a bounded number of books per mode for testing, and
registers the game. The admin view renders each online game as a large tile;
opening one loads a standard template that embeds the game's own
index.html in a frame and hands it a session and the RGS URL.
Current Status
Heimdall is in early design. The protocol and book formats are settled (inherited from the Eyes of Argus build), and the game-folder contract and registry service are the next pieces to land. This page itself is the project's first footprint on the platform.
Long-Term Vision
Heimdall is meant to be the shared workshop where slots are tested before they ever leave the forge — a place where a build dropped into the games folder simply appears, runnable, in the admin grid. Longer term it is the clean room that keeps the financial and presentation layers honest, so that whatever is built here can travel to a wider distribution path with the contract intact.
Heimdall Console
The Heimdall admin grid — the live list of online games and their embedded players — is available to authorised members from within the platform once the service is deployed.
Console access is available to authenticated members only.