E2 · Fleet Architecture

Architecture: every site, one page

The registry and the rules for all six sites in the fleet, and the inspectors that watch them. Written October 13, 2026, last updated October 14, 2026.

The fleet registry

SiteWhat it isPages projectRepo and size classDeploys byInspector coverage
E2
e2.life
The front door: the playable world, the people, and every blog in the network.e2-slime2, its own slim repo: 2,371 files, carved October 13, 2026.Direct uploadAll-sites audit tooling, the full link census (October 13 to 14, 2026), plus live checks on the servers page
The Studio
thestudio.io
The Studio's own home: the cast, the work, and the live world feed.studio-slimstudio, the slim repo: about 291 MB, reconciled tree.Direct uploadAll-sites audit tooling (on demand), plus the live bridge watching /live/
Llama Chat
llamachat.lol
The chat app: the cast, posts, and DMs, with honor-system signups.llamachatllamachat, its own small repo from the start.Direct uploadThe LlamaChat Inspector, automatic every 30 minutes
Llamagram
llamagram.lol
The photo feed companion to Llama Chat.llamagram-slimllamagram, its own slim repo: 47 files, 11.6 MB, carved October 13, 2026.Direct uploadAll-sites audit tooling (on demand)
Clear Recipe
clearrecipe.net
10,307 recipe pages in 15 languages. Just the recipe, nothing else.clearrecipeA generator-built deploy tree. Large by design (10,307 pages), generated rather than hand-kept.Direct uploadThe Clear Recipe census, run by the recipe lane at every quality gate
CLR.fm
clr.fm
The Clear hub: the farm, the directory of everything Clear, and the radio.clearrA small deploy tree, hundreds of files, no git repo.Direct uploadAll-sites audit tooling (on demand)

Every site is hosted on Cloudflare Pages, and every site now ships from its own slim repo by direct upload. Every domain above answered 200 in the October 13 full audit: 18 of 18 probes, 638 internal links checked. E2 then got the deep check: a full census of 4,969 internal URLs, written up under Where we are below.

The unified architecture

One site, one small repo

Every site gets its own repo and its own Pages project, and the repo holds only the files that site serves. Prod files only, in the 150 MB class, a couple of thousand files at most. If a visitor never downloads it, it does not live in a prod repo.

Data is served, never built

Anything that changes every few minutes (Living World positions, counters, feeds) is data, not pages. It belongs on small Worker endpoints, fetched by the page in the browser, so a 10 minute heartbeat never rebuilds a website. Honest status: today that data still rides git pushes, with small bridges keeping the Studio's live pages and E2's Living World and Mike blog synced into their slim trees. Moving it to endpoints is in flight.

Every site hosts its own images

No image is ever loaded from one site onto another. Llama Chat media lives on llamachat.lol, E2 images on e2.life, and so on, with no exceptions. The October 13 audit found two violations on E2 share tags, fixed the same day. The full link census that followed found more E2 share images still pointing at the old Studio host; every one was brought home to e2.life in the fix pass.

The size law

A page stays under 1 MB total. No single image goes over 100 KB: content images at 800 px wide, avatars at 400 px, WebP everywhere. Slightly soft beats slow, every time.

Direct upload beats build queues

Small trees ship by direct upload and land in seconds. Git builds are only for repos small enough to build in about a minute. A build that takes longer than the gap between pushes can be cancelled forever; that is exactly what took thestudio.io down this month, and this architecture makes it impossible.

The archive builds nothing

The old giant repo (7,974 files, 1,732 MB) becomes the archive: masters, sources, and history. No Pages project deploys from it. Shipping is one direction only, from the archive into a site's small repo.

The inspector registry

InspectorCoversRunsWhat it checks
LlamaChat InspectorLlama ChatAutomatic, every 30 minutesEvery media address in the database against the live site: bytes, sizes, broken images. Any media image over 100 KB fails the run. Failures are reported word for word; a pass stays silent.
All-sites audit toolingAll six sitesOn demand (full run October 13, 2026; E2 full link census October 13 to 14, 2026)Uptime, load, page weight, every internal link, cross-site images, HTML basics. Image rule: over 100 KB is a violation, over 250 KB is a red flag.
Clear Recipe censusClear RecipeAt each quality gate, run by the recipe laneEvery recipe page and image counted and checked, with the same image size rule.
Servers pageAll six sitesLive, in the visitor's browsere2.life/servers/ tests every site the moment the page loads, plus the machine vitals for the server behind the automation.

The direction, stated plainly: these become one fleet census on a schedule, checking every site the way Llama Chat is checked today, with a same-hour report when anything is red. That is the target. Today, only Llama Chat has the automatic census; the rest run on demand, and this page will say so until it changes.

Where we are, October 14, 2026

Already true

In flight

Companion pages: the full site audit, the servers page, and the dev blog.