Lumbridge Compute

Governed compute for unified-memory AI hardware — machines where CPU and GPU
share one pool and there is no separate VRAM allocation to bounce off.
Over-commit that pool and the box thrashes and wedges, SSH and ping included,
before the OOM killer gets a turn.

Compute does not run inference. It supervises the servers that do: admission
control against both a declared budget and what the machine actually has free,
a 1 Hz watchdog that stops the newest model before thrash, Scenes activated as
one transactional unit with rollback, process ownership bound to
(boot_id, pid, start_time_ticks, pgid) so a reused PID can never be
group-killed, a protocol-transparent gateway, an MCP server, and a read-only
HTTP API for dashboards.

Registry footprints in this release are measured on a live node rather than
estimated.

One binary, six direct dependencies. Apache-2.0.

Generated by scripts/publish-compute.sh, which refuses to publish a tree it
cannot prove clean.

scenes/music.scene.yaml

@@ -0,0 +1,20 @@
+apiVersion: lumbridge/v1
+kind: Scene
+metadata:
+  name: music
+  version: 1
+  description: "Music studio — ACE-Step XL 4B sft, with ears and voice, no brain."
+  author: karti
+  tags: [music, creative]
+
+# ears 5 + voice 4 + music 24 = 33 GB. Brain-free, so tons of headroom — the clean
+# scene for a music-generation demo when the MoE is not needed.
+models:
+  - ears
+  - voice
+  - music
+
+budget_gb: 100
+activation:
+  order: footprint-asc
+  wait_healthy: true