the ALTERNATE BUILDS
ALTITUDE 2 — SIBLING PLATE, THE ECOSYSTEM: one box of eleven family bricks at sheet 2’s mould and nine runtimes as stacks of baseplates sized from one shipped build at the same scale, and the seven alternate models the repository’s own consumers build from it, and an eighth the atlas’s own app builds on its own branch — each model the parts one consumer pins, on the plates they peer · rows read census-builds.json, both readings, and census-peers.json @ eb1162da
GENERAL NOTES
One box, several models. Sheet 2 draws every family brick in one assembly on @uirouter/. The repository's own consumers — 19 consumers: the sample apps, the docs site and the examples at the cabinet's sha — pin seven distinct sets of family parts, each manifest closed over its family peers, and this plate draws each set as the model it makes: its parts at sheet 2's mould, standing on the runtime plates those parts peer. The eighth model, build VIII, is the atlas's own app: its manifest at www/, read from git archive www/ @ 2011c945, off the cabinet's tree, and drawn accent-edged on its own branch the way sheet A4 draws the atlas deploy. Every count on this sheet reads both ways, the cabinet's tree first and “with the atlas app” after. Build I is the most built, lit-ui-router alone on @uirouter/ and lit, by 6 consumers. One consumer pins no family part at all (sample-app-lit-e2e), and is a consumer rather than a build.
No model mixes two reactivity runtimes. effect, mobx and signal-polyfill are each reached by a family binding — lit-ui-router-mobx, lit-ui-router-effect, lit-ui-router-signals, ui-router-effect, ui-router-signals and ui-router-mobx — and no consumer in either reading mixes two of them; the build stops if one does. The bindings are alternates in the box, the way one set's instructions show a car or a plane, not both.
Ground and stacking follow the dependency. A family brick peers lit or effect, not the reverse, and no runtime on this plate peers another — both read from each row's own peerDependencies — so each runtime is a plate, the parts stand on them, and the plates lie on plain ground. @uirouter/ is a plate like the others: ten of the eleven family bricks peer it, and it is the baseplate of every model, laid first at the left, the way sheet 2 seats the family on it. A part stands on the part it peers when that part is in the same build, as it does on sheet 2, and the rest seat on core at sheet 2's places measured from core's right edge, packed from the back where sheet 2 seats them off its client plate; a part that peers no core seats on its one runtime (eslint-plugin-lit-ui-router). Every other runtime a brick peers abuts core and the brick reaches it, unless the brick it stands on already carries it: a brick on core straddles the seam onto a flat runtime plate one stud deep, the way lit-ui-router stands on both core and lit, and a brick that cannot straddle, one on another brick or one beside a stack, reaches it by a cord: a string with end studs, two 1×1 round plates joined by a cord, one seated on a ringed stud of the brick's top and the other on a ringed stud of the plate, the cord leaving each plate's own stud, from the nearest pair of free studs whose cord clears every brick and stack. A brick standing on another brick hangs its cord instead from a free stud of its underside, the round plate's stud seated in the brick as on a stud, wherever that cord drops clear of every other brick and stack — brick 5 in build III and brick 6 in build VIII. Nothing abuts core from behind: a stack taller than core stands at its left or right side, and a flat plate along its front, at the right beside the seam or at the left, wherever every cord to it runs clear of every brick and stack; each plate rings one stud per brick coupled to it. The atlas app's model spans the columns its width needs. A build stands on the runtimes its consumers declare and on every required peer its parts carry, which the installer adds whether or not a manifest names it; an optional peer no consumer declares stays off the model.
One scale. The family keeps sheet 2's mould exactly — 1 stud per 150 sloc rounded up the brick shapes, a course per 3 authored files. A runtime is baseplates at sheet 2's baseplate footprint, 8×6 = 48 studs, one stud per 150 sloc of one shipped build — the files reachable from its exports entries, the development condition where one is shipped (@lit-labs/) — laid a plate at a time and stacked when it overflows, the remainder on top at its own size, three plates to a brick course: effect is 8 plates · 7 of 8×6 + a 3×4, eslint is 9 plates · 8 of 8×6 + a 6×6 and hono is 2 plates · 1 of 8×6 + a 4×4. Under 48 studs a runtime is one plate at its own size, the nearest rectangle: @lit-labs/ 3×3, @lit-labs/ 1×2, @uirouter/ 6×6, lit 1×1, mobx 6×6 and signal-polyfill 2×2. A package's dependencies are a number in the schedule rather than area on the plate: @lit-labs/ builds 1,083 lines over a closure of 28,345, @lit-labs/ builds 282 lines over a closure of 4,564 and lit builds 39 lines over a closure of 4,282. Every model on lit stands on a 1×1: six of the seven builds, seven of eight with the atlas app, and the runtime they run on is in its closure.
What stays in the box. lit-ui-router-ssr is carried by no consumer at the cabinet's tree, so no model of that reading draws it; with the atlas app, lit-ui-router-ssr stands in build VIII. @lit-labs/, @lit-labs/ and hono are plates no model stands on at the cabinet's tree — @lit-labs/ssr-client and hono optional and pinned by no consumer there, @lit-labs/ssr peered only by a part no consumer there carries; with the atlas app, build VIII stands on @lit-labs/ssr and @lit-labs/ssr-client, and hono stays spare. They stand in the dashed register under the box, each line reading the cabinet's tree first and the atlas app after, and the spare plates are drawn there rather than on the ground. Build II's manifests differ in what they pin and what they take as a peer, build III's manifests differ in what they pin and what they take as a peer and build IV's manifests differ in what they pin and what they take as a peer; the schedule says which. Every number on this sheet is read from www/, census-peers.json, census-bricks.json and census-couplings.json — counted at origin/main @ eb1162da (2026-10-18); the second reading adds www/ at www/atlas @ 2011c945.
KEY
| a family brick — sheet 2’s mould: 1 stud per 150 sloc, a course per 3 files | |
| a runtime — baseplates of 8×6, 1 stud per 150 sloc of one shipped build, stacked when they overflow, the remainder on top at its own size; three plates are one brick course, 144 studs; under 48 studs, one plate at its own size | |
| a build — the family parts one consumer installs together, counted from the sample apps, the docs site and the examples at the cabinet’s sha, and from the atlas app’s own manifest on its branch | |
| an accent-edged panel — the atlas app’s build, on its own branch, its ground edged in accent | |
| a ringed stud — one per brick coupled to a plate, under a seated or straddling brick or under a cord's round plate, on the plate and on the brick's top; the plate lettered A–I beside it | |
| drop line — the brick seats on that stud; a brick straddling a seam drops onto both plates | |
| a string with end studs — two 1×1 round plates joined by a cord, a coupling a footprint cannot make, drawn to fit and not massed: one plate seated on a ringed stud of the brick’s top, the other on a ringed stud of the runtime’s plate, the cord leaving each one’s own stud; a cap seats on a stud or hangs from a brick’s underside | |
| a dashed plate — an optional peer | |
| not in any build — a part no consumer carries, or a plate no model stands on | |
| ground — the registry, not massed |