A human and Claude Code turned one LucidLink filespace into a render farm that needs a token and a folder, nothing else.
No farm manager. No queue server. No message bus. The dispatcher is a hub lock, the progress bar is a file browser, and the artifact store is the same encrypted drive the footage already lives on. Everything below is a number that a run actually printed.
A box that knows two things: a token and a folder.
Humans get mounts. Agents get the SDK. A worker joins with pip install lucidlink and a token, fetches its own code and tools from the drive, and starts claiming work. No kernel client, no FUSE, no desktop app on the whole fleet.
"The instance knows two things: a token and a folder. The folder taught it everything else."// beat B5, mountless bootstrap
One survival run held four workers on real load for about 33 minutes with zero stalls, all four SSM Online throughout, every box holding 30 to 65 MB per 5 minutes of network out. The blackout signature that killed the FUSE stack never appeared on the SDK path.
"Nothing on these machines came from anywhere but the drive: their code, their tools, and the model itself."// beat B6, model from the drive
The drive is also the model registry. A fresh box fetched SmolVLM from /tools/models and reached inference in about 53 s with the model hub switched off entirely: fetch 25.5 s at 177 MB/s, untar 21 s, load to CUDA 6.6 s. Version-pinned by snapshots, no model-hub account on any box, weights sitting in the same zero-knowledge vault as the footage.
Post starts while the camera is still rolling.
A live feed lands as 2-second segments on the filespace. Workers discover them by listing a directory, cut proxies and posters, and a single GPU box captions one frame per segment. The captions land as sidecars beside the proxies, seconds behind the lens.
"The camera has not stopped, and post has already started."// beat B1, live proxies
"A GPU in Oregon is logging your footage seconds behind the lens."// beat B2, live captions
Elasticity is the whole point. In the presentation take the cameras produced roughly 90 clips per minute; four workers consumed 24 per minute. That gap is not latency, it is a dial you turn with instances.
"The backlog is a dial: four machines fall 12 minutes behind, sixteen never fall behind, each is 53 cents an hour."// beat B3, elasticity
The receipt refuses to lie.
When the queue drains, the run signs a receipt. It counts the clips in the movie before it signs, and it would rather fail loudly than certify a hole. Two clean dress runs, 420 of 420 posters each, ffprobe-verified.
"The receipt refuses to lie: it counts before it signs."// beat B4, the receipt
One receipt was signed by two operating systems. A MacBook and a Windows gaming laptop transcoded the same dailies queue, coordinated only by hub locks on the filespace, neither machine mounting anything. The gaming rig joined the same way every worker does: pip install lucidlink and a token.
"One receipt, two operating systems, nothing shared but a drive."// beat B7, the two-hostname receipt
"You are watching one hub lock physically block another machine."// beat B8, lock theater
Locks are range-scoped, they follow a file across a rename, and contention returns a clean refusal every time, 0 exceptions in 53 tries. In the close, the audit trail answers the offboarding question directly: every fileId is stamped creatorNodeId:seq, so the drive can say which session made each write and whether an offboarded machine actually stopped.
"Did the offboarded machine's writes actually stop? The drive can answer that."// beat B9, audit close
The GPU never downloaded the model.
SmolVLM is one 4,492,630,912-byte safetensors file: an 8-byte header length, a JSON tensor index, then a packed blob of 657 BF16 tensors. Because the SDK does ranged reads, a two-process loader can parse the header, plan coalesced byte ranges, and pump exactly the tensors it wants off the drive and into video memory. No local copy. No untar step. Every byte md5-verified on both sides.
"The GPU never downloaded the model: it read the tensors it wanted straight into video memory."// beat B10, streaming weights
The last line is the proof of life: the streamed model captioned a frame that also came from the drive. Full-stream time held steady across four runs at 28.4, 33.6, 34.5, and 32.3 seconds (130 to 158 MB/s). Bootstrap to work-ready on the spike box was 138 s. The box lived about an hour, on-demand, and the session's entire GPU spend was about 53 cents.
The backbone, one line each.
Nothing goes on this list that a run on screen is not currently proving. Numbers beat adjectives.
The only thing that persists is the drive.
The machines were rented and returned. The code, the tools, the model, the queue, the telemetry, and the receipts all lived in one folder. Turn the instances off and the filespace still holds the whole story.