A distributed, asynchronous simulation backend: submit a solve from the
desktop app, the browser, the CLI or an MCP agent, disconnect, and claim
the results later from any device. The hub is an in-memory switchboard
(hub.solidcraft.io or self-hosted) that stores nothing; one worker
coordinates and keeps the job log, results stay on the workers until a
client claims them, and a cluster is a 12-word passphrase from which all
keys derive, so the hub never sees content. Covers the protocol, hub
restarts, studies and caching, Kubernetes pools, the engine changes for
M1 and a five-milestone rollout with the public hub last.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
