Older versions
An explainer and the tenants to start with, then two technical diagrams, then four takes on the whole system.
Supervisors, all the way down for engineers new to the BEAM and Kubernetes
A scrolling explainer: the stack from Hetzner box to Elixir process, the BEAM in two minutes, supervisors with a crash-it-yourself demo (a toy app, then mycelia's real tree), Kubernetes with a kill-a-pod / power-off-a-node / rolling-update demo, a side-by-side table, and how mycelia uses both.
Tenant · beep-boop two static games
Its members and visitors, what mycelia does for it (page, agents, deploys), its namespaces on the shared Kubernetes cluster, and its repo. Live: pax-galaxia (canvas strategy game) and tic-tac-toe, both plain files nginx serves. No database. Ten lines, one per step.
Tenant · len-bus-factor one Python app
The same essentials. Live: mahjong, a small Python server with bots and coach mode; its tables live in memory, so a redeploy clears them. No database.
One colony labs, the owner's own (a special case)
Members and visitors, what mycelia does for the colony (its page, its agents, its deploys), what runs for it on the shared commons server (agent pods, builds, registry, apps, Postgres, all sandboxed), and its git repo. 13 lines: use, manage, code, ship, data.
The code Elixir · Gleam · Python · shell
Columns: the browser (the Lustre spores app, its FFI, the editor element), mycelia's web layer (channels, LiveViews, the API), mycelia's core contexts and shared clients, the outside services, and a spore's pod (bridge.py, hyphae, Claude Code, hooks, CLI). Boxes are coloured by language; lines by how they talk: channels, HTTP, stdin/stdout, in-process, database, outside APIs.
The Kubernetes side five clusters
galaxy, workers, commons, alchemy and a colony server: namespaces, Deployments, StatefulSets, the pods mycelia creates, NetworkPolicies, quotas, ServiceAccounts and Roles, Secrets. Lines: who controls which API server with which token, traffic (ingress, pod IP, API-server pod proxy), images, git and CI, secrets.
D · platform overview for a corporate audience
The stories version in plain business language and a light presentation look: AI agents, repair agent, agent teams, team workspaces; stories like "How code ships", "How failures get fixed" and "Built-in reliability". No module or namespace names.
C · stories committed in mycelia/docs
Three rows: the app, Kubernetes, the machines. mycelia as six tiles in plain words. Pick a story (a spore runs, push → deploy, deploys & mycologists, a swarm, colonies, who supervises whom) and only its lines show, numbered, with each step explained.
B · skyline
Each machine is a tower on the ground, with mycelia's supervision tree on top of galaxy and a zoom funnel down to its pod. Lines to other machines go over the top; git, CI and images go underground with numbered steps. Everything at once, filterable by kind.
A · nested boxes
The previous version: mycelia's full OTP tree above, Hetzner → k3s → namespaces below, every line in its own lane.