GENERAL NOTES

Method — one basis, shared with sheet 4. Every massed structure was counted from this repo's authored source, counted at origin/main @ 3f55e419 (2026-10-31) and read from www/atlas.lit-ui-router.dev/data/census-yard.json: .ts/.tsx/.js/.mjs under each member's source directory, excluding *.d.ts, *.test-d.ts, *.spec.* and *.test.*, specs/, __tests__/ and fixtures. sloc is scc's Code count — string-aware, so the interior of a template literal counts as code rather than as one line. @tools/release hosts several instruments at once, so it is attributed by module prefix — check-published-diff* to structure 11, check-exports* to 10, the pack modules to 3, the release steps to 5 — with every file landing in exactly one structure and none counted twice. 20 structures, 18 of them massed: 396 authored files, 32,205 lines. One member is massed nowhere: @tools/wintercg-globals is a single globals.d.ts, and declaration files are outside this basis. The tarball, the registry and the boundary are diagrammatic.

Mass is volume; volume does not predict authority. Footprint side is 1.6 · √sloc, so plan area tracks lines; height is 1.5 px per authored file, so a block's volume is its sloc × files. The three heaviest masses on the sheet gate nothing: packages/*/src (109 files, 10,708 lines), sample apps (84 files, 4,502 lines), lint & probe fleet (47 files, 5,313 lines). The 5 structures that can stop a pull request total 37 files between them, and one of them — dts-backtest — is a single 619-line run.ts. Encoding severity as height would imply the opposite; the census says a gate's authority has nothing to do with how much code it is.

Severity in colour. Red hatch across cap and flank marks a check that stops the PR line: the vitest harness (7), compat-guards (8), dts-backtest (9), check:exports (10) and Cypress e2e (17). One block is solid red — published-diff (11) — because it is the only structure that halts publishing itself, and it closes the loop by pulling the live npm tarball back for comparison, which makes the registry part of the circuit rather than a destination. Accent hatch marks the gates that fire later rather than on a PR: peer-floor tier-2 (12) gates version bumps, the workers-builds watch (19) gates the docs deploy. Faint, unhatched blocks never gate at all — peer-floor tier-1 reports check runs, the lint & probe fleet is advisory, @tools/shared, the typedoc plugin and the vendored anti-slop rules (20) are libraries. The tiers survive both themes because they differ in hatch as well as hue: solid red, red hatch, accent hatch, no hatch.

One packer, many readers (#449). The dashed trunk leaving the green crate is literal: check:exports (publint + attw), dts-backtest and published-diff all read the same cached packPublishTarball output. No check re-packs, so a drift verdict is always about the artifact that would actually ship. Known failure mode, drawn nowhere but real: a poisoned remote cache entry can replay a stale verdict — --force is the remediation.

Two task managers, one re-entrant loop. The inset at top right is drawn flat, not isometric, because a task manager is not a place — and because the relationship is not the clean layering it sounds like. GitHub Actions enters mise at 56 call sites across 9 workflows (36 distinct tasks); mise itself is almost graphless — 65 tasks with exactly 12 of them declaring depends (16 edges), among them lint_workflows → its four linters and setup → turbo_pin_worktree — because it delegates fan-out rather than modelling it. Seven mise tasks shell turbo, whose ci graph alone expands to 1251 task nodes. Then the loop closes back on itself: seven root package.json scripts shell mise run again, so turbo's //#lint:markdown node literally runs mise run lint_markdown. That return is the whole point — mise/aqua owns the versions of the non-node tools (rumdl, taplo, shellcheck, actionlint, zizmor), and turbo climbs back out to it to get a cache key over tools node never installs. Neither gantry is above the other.