GENERAL NOTES

Method: every number on this sheet is read at build time from the checked-in plate www/atlas.lit-ui-router.dev/data/census-shipped.json — measured at origin/main @ 3f55e419 (2026-10-30) · www/atlas.lit-ui-router.dev/generator/census-shipped.mjs. The probe builds www/lit-ui-router.dev/dist inside a materialized, installed archive of the ref, never the working tree, and measures it file by file: height is gzip level 9 of each file, the honest wire measure, since the CDN serves compressed. Footprint is file count, as on sheets 7 and 8. A reachability walk — every HTML shell and hashed chunk, following static asset references — sorts the assets into districts, and a shared chunk counts where it is first claimed (vanilla → mobx → effect → hash → signals), because the CDN ships it once. This sheet extends the survey a step further: sheet 7 measures the source, sheet 8 what npm delivers, this sheet what one deploy actually ships — 1,771 files, 74.4 MB on disk, 8.0 MB on the wire. Sheet 10 goes one level in again and opens the bundle itself.

The tallest building is the prose. The skyline is the site's 389 prerendered HTML pages at 3668 KB, with examples 2,196,461 bytes behind at 1523 KB — the prose outweighs the runner-up 2.4 to 1. Inter's 16 woff2 faces stand third at 849 KB: on the wire, this documentation site is still mostly prose and typography, and the one script district that outranks the lettering is the examples, led by a single galaxy. The prose ships twice: beside the HTML stands its Markdown mirror, 378 files at 526 KB — a plain-text copy of every page plus llms.txt and llms-full.txt, the site's text for language models — and the 14 diagrams the pages inline also stand alone as public .svg files, 20.9 KB. A vacant lot at the plan's edge is the demo corpora's footprint, which the deploy does not carry.

The product is a guest in its own city. The five routed sample apps — the thing the site exists to demonstrate — total 400 KB gzipped, 4.9% of the deploy. First claim seats visualizer.esm and the custom-elements manifest in app: vanilla, which is why that district reads 19 files and 129 KB while the hash app's whole district is 4 files and 16.5 KB. Two rules shape those numbers rather than the CDN: a scoped override holds the @api-viewer/lit-dialog stack to one lit major, so identical lit chunks hash identically across apps and part of mobx's download is chunks vanilla already ships; and the api-viewer docs panel, which renders only behind a feature flag, arrives in a lazy api-docs chunk rather than the eager main one. Same bytes on the CDN, fewer on the critical path.

There is no ghost district. The reachability walk follows the backtick-quoted asset URLs the app chunks build by hand, so the api-viewer custom-elements manifest is reachable after all, and the orphan list on this plate is empty — no hatched block stands here. Read that as a statement about the instrument as much as the deploy: an orphan count is only as good as the walk that produces it, and earlier walks over an accumulated local dist/ reported orphans that were stale build output, not shipped weight. This census builds clean, into a materialized archive of the ref, and counts what a browser can reach.

One example outweighs the router. The examples district — 36 files, 1523 KB — is led by the hellogalaxy-signals example's model-viewer chunk at 276 KB on its own, heavier than the vanilla, mobx and hash apps combined, delivered so one tutorial page can spin a galaxy.