LDI Studio · Operating Layer
Infrastructure
Three machines. Three agents. One handoff bus. This is how the work actually runs.
LDI runs on a three-machine, three-agent stack connected via Tailscale. This is not metaphor. The Attraction is the public face of a real operating infrastructure. The Workshop, the Signal Feeds, the back lot incident log — all of these correspond to actual running services.
What follows is the honest version of the architecture: what the machines are, what the agents do, and how the handoff bus moves work between them. The Attraction's lore is the interpretive layer. This is the documentation layer.
The Machines
Tailscale mesh — always IPs, never hostnamesThe brain. Bob lives here. All agent sessions, vault access, handoff dispatch, and Claude Code sessions run from this machine. The Crossroads volume (3.5TB) and X9 Pro (1.8TB) are both mounted here.
- Bob/Hermes gateway
- Claude Code
- Obsidian vault
- Handoff bus (writer)
- OneDrive (sole mount)
Linux compute node for async workloads. Docker containers, long-running jobs, scheduled crons. The Crossroads and X9 Pro are accessible via SSHFS. No agent sessions or messaging — worker only.
- Docker / cron jobs
- Hermes worker
- SSHFS (Crossroads + X9 Pro)
- Handoff bus (reader)
Windows machine with GPU. ComfyUI, 3D render jobs, image generation. Codex MCP available via WebSocket. All scripting is .ps1 — write file, SCP, execute. Never inline shell chains.
- ComfyUI
- Codex MCP (WebSocket)
- GPU workloads
- 3D fabrication prep
The Agents
Workers, not orchestrators — the Operator is the architectPrimary dispatch agent. Receives missions via the handoff bus, routes work to appropriate nodes, returns receipts. Runs on Hermes gateway with Nemotron Super as default model. Persona-hardened — does not spiral, does not apologize, gets things done.
- Mission dispatch
- Multi-step research
- Cross-machine routing
- Receipt writing
- Telegram interface (sole agent)
Infrastructure maintenance agent. Keeps the gateway clean, signal paths correct, and the cold coffee undisturbed. Ghost operates at the systems layer and does not explain his work unless asked directly and twice.
- Gateway health
- Signal path validation
- Cross-node sync
- Config maintenance
- Cold coffee management
Monitors the boundary between the known operational envelope and whatever else is happening. Logs access events, classifies anomalies, and holds the full field notes record including the two open Y07 incidents. The Warden's logs are not public.
- Access logging
- Anomaly classification
- Boundary monitoring
- Full field notes record
- Back lot watch
The Handoff Bus
Work moves between the Operator and Bob via a file-based handoff bus at /tmp/brainlab-context/handoff/. The Operator writes a mission brief to inbox-for-bob/. Bob's cron scans every 5 minutes, picks up the file, executes the mission, and drops a receipt in inbox-for-claude/. Both inboxes are committed to a shared git repo and pushed to GitHub so all machines see the same state.
git push
receipt
Mission briefs include a done_criteria field — a verifiable stop condition Bob checks after each iteration. Without it, Bob decides when he's done. This is how loops happen.
On the Attraction
Ghost's Workshop is the public-facing version of this infrastructure. The signal feeds in the Workshop correspond to real service states. The access log on the Employees Only page uses real access event logic. The Warden's boundary patrol is the monitoring layer. The cryptid in the back lot is not yet classified.