CydandClaude Fable 5
88caa81e04
Searched the firestorm tree for an authoritative expansion of "CTCL" and found none. Replaced the guessed "cafe/Tesla control layer" wording with the attested facts (Console 2 Launcher message comments, _ECTCL_Console/ _ECTCL_Launcher roles, Tesla-centric coin-op API) and flagged the reading "Console-Tesla Control Layer" as inference. New facts from the dig: CTCL is game-agnostic (_EAT_MW4/_EAT_RP) and has its own ports 1000/1001, added to the port map. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
SiteLink
Linking multiple VWE Pod Bays together to play games across the internet.
A Pod Bay today is an air-gapped network of ~20 computers: 1 command console, 1 printer, 2 review stations (Live Cam & Mission Review), and 16 cockpit computers. SiteLink is the project to connect those islands — so a bay in one city can field a lance against a bay in another, share a queue, share voice, and (eventually) be commanded as one fleet.
Seed concept (2026-07-10)
Organize each site into its own
10.0.y.xsubnet (site 1 =10.0.1.x, site 2 =10.0.2.x, …), VPN them all together into a single10.0.0.0/16, then collect every site's.siteconfigand merge them for a master console that can command the entire fleet.
That concept is the anchor of this repo. The analysis, alternatives, and open questions live in the docs below.
Contents
| File | What it is |
|---|---|
| docs/PODBAY-ECOSYSTEM.md | Survey of the existing bay software stack — every component, every protocol/port, with source pointers into the sibling repos. The ground truth SiteLink has to work with. |
| docs/BRAINSTORM.md | The design record: goals, the seed proposal analyzed, addressing plan, VPN topology options (routed vs bridged), master-console vs federation, per-game linking analysis, shared services, security, open questions, and a phased roadmap. |
Related repositories (gitea.mysticmachines.com/VWE)
| Repo | Role |
|---|---|
TeslaSuite |
TeslaConsole (operator console), TeslaLauncher (pod service), the Console↔Pod RPC contract, SecureConfig provisioning, and vPOD (virtual pod — our cross-site test double). |
firestorm |
BattleTech: Firestorm — the MW4/Gameleap-engine game the 16 cockpits run. DirectPlay 4 multiplayer. Contains the drafted 16→32 player-cap plan that a two-bay link needs. |
RP411 |
Red Planet (MUNGA engine, Win32/DX9 port). Console-controlled via Munga protocol, TCP 1501. |
BT411 |
Classic arcade BattleTech (Tesla 4.10) reconstruction on the RP411 engine. Console streams the mission egg over TCP; pods mesh with each other. |
(local PQS/) |
Pod Queue System — PHP/MySQL front-of-house: registration, callsigns, queue, and the HTTP endpoints the game/console poll for the next mission + roster. |
Status
Brainstorm / design phase. Nothing here touches a live bay yet.