GENERAL NOTES

Method — one ruler, two deploys, two altitudes. Every block on this plate is massed by SIDE() and HT() imported from sheet9.mjs — footprint side 10 · √files, floored at 18; height one pixel per 4,300 gzipped bytes, floored at 8, the constants read back off the functions themselves — and every file is weighed the way sheet 9 weighs it: raw bytes and gzip level 9, the honest wire measure, since the CDN serves compressed. The two halves stand on different grounds and say so. The docs deploy is data/census-shipped.json, origin/main @ 3f55e419, the cabinet sheet 9 reads. The atlas is not on main, so it cannot be in that cabinet: it is data/survey-shipped.json, written by generator/survey-shipped.mjs from a git archive of its own branch — www/atlas @ 08a98096, committed 2026-10-30 — in which the app is built by its own npm ci and npm run build, the vite build and the prerender, and app/dist is measured file by file: 290 files, 23.1 MB on disk, 8.5 MB on the wire. That is what Cloudflare Pages serves at atlas.lit-ui-router.dev. A reachability walk from every page sorts the files into districts, and a path the app computes at runtime — a fragment by the manifest's file, the manifest by the router's base, the visualizer's icons by its stylesheet — is seeded rather than reported as a false orphan.

Two altitudes, one ruler. The sheet draws both deploys twice, at one scale: sheet 9's ruler drawn at 0.85×, the largest hundredth at which both rows fit 1,520 px with 8 px gaps and 140 px lettering slots.Along the top, by role: sheet 9's three roles of the docs deploy, read from its exported ROLES, each summed into one block, and three roles of the atlas deploy in the same order, each beside its counterpart — the pictures beside demo payload, the plates beside the documentation site, the app and its lanes beside the routed apps. Below, by district: every district of each deploy on its own lot, the docs deploy's fifteen west of the atlas's eleven. A role's block and a district's block are massed by the same two functions, so a block in either row reads against any other at the same altitude, and a role against its own districts. Summing is honest on this ruler for plan area — area ∝ files, so one block of a role's sum covers the same ground its districts do — and approximate for height, which reads a role's total bytes as one tower. The by-role totals reconcile each plate's own totals, every atlas district is claimed by exactly one role, and sheet 9 throws when a district on its plate is claimed by no role or two, so the two plates cannot disagree.

What the drawing says. The atlas deploy is 1.1× the docs deploy it draws, on the wire: 8.5 MB gzipped against 8.0 MB, in 290 files against 1,771; by role, the pictures 4499 KB against demo payload 1726 KB (2.6×) · the plates 3026 KB against the documentation site 6084 KB (0.5×) · the app and its lanes 1172 KB against the routed apps 400 KB (2.9×). The tallest district is card pictures, 3663 KB in 68 files — 1.0× the docs deploy's tallest, html pages at 3668 KB. The pictures are the whole story of the weight: a card picture is a webp, already compressed, so card pictures keep 99% of their raw bytes through gzip; the routed pages keep 21% — the lettering and markup of a deploy shrink on the wire and its pictures do not. The plates themselves ship in triplicate: every plate ships three times — inside its routed page, as a bare plate and as a fragment: 1420 KB + 830 KB + 776 KB — the routed page carries its plate server-rendered, the bare plate stands for a reader who opts out of the router, and the fragment feeds the client's own navigation. Below those, the 3D lane's viewer and its decoders, 854 KB, outweigh the routed app itself, 154 KB, 5.5 to 1, and no ghost district stands here: every file in the deploy is reached from a page, by reference or by a seeded path. Every claim in this paragraph is computed from the two plates and changes its wording when the plates change it.

What the pictures are for. The 68 card pictures are the cover's cards: one per plate in each theme, 300×400 CSS pixels drawn at 2×, so a card holds up on a retina display and the cyanotype theme has a picture of its own rather than an inverted one. They are 42% of the wire and arrive lazily, as the gallery scrolls; the first page a reader lands on is 276 KB at most, the heaviest routed page, and a plate's own page carries nothing of the pictures at all. The weight is real and the drawing shows it; whether it is the right weight is a question for the cover, not for this ruler.