GENERAL NOTES

Method — what is drawn, and from where. Everything on this page comes out of www/atlas.lit-ui-router.dev/data/census-loop.json, the checked-in plate generator/census-loop.mjs reads off a materialized archive of the ref — surveyed at origin/main @ eb1162da (commit 2026-10-18). It is a T1 tree probe: nothing runs, seven files under packages/lit-ui-router/src/ are read line by line. The plate carries the 10 stations of sheet 1 (each anchored to the line where lit-ui-router implements it), the 12 legs between them (each with the call or event that carries it), and the walk — 12 steps, 30 evidence lines in all. Every evidence entry is filed as file:line plus the verbatim source at that line, and the probe throws if the line it was told to cite no longer reads what it expected: a refactor that moves a hook breaks this plate rather than letting it narrate stale code. The lane cross-checks the plate at build time and throws again if the walk names a leg that is not on it, a leg joins a station that is not on it, or the tallies disagree with the lists.

The walk, defined. One navigation: a click on <a uiSref> from /people to /people/32. The steps are ordered by the source, not by memory — the click handler's own guards and its $state.go, then core's sequence stated only through the hooks lit-ui-router registers in it: <ui-view>'s onBefore (uiCanExit) and onSuccess (uiOnParamsChanged), uiSrefActive's onStart tap and its trans.promise, TransitionController's default ['onSuccess']. No line of @uirouter/core is cited, so where the machine itself moves — matching, resolving, writing the url — the step says so and cites the wire lit-ui-router owns at that point. Step 2 is the click; step 1 is the circuit at rest, because before any click the stations have already found each other by composed DOM events, and that wiring is the only reason the click has anywhere to go.

Layout — sheet 1's ring, computed at build time. The stations stand in sheet 1's own order around a ring: location, core, the transition hall, the view with its child below it, Lit render, the document with the link on it. The two stations sheet 1 draws elevated — uiSrefActive and TransitionController — stand inside the ring here, because they are not on the route: sheet 1's key says "elevated = overlay", and inside is the flat drawing's word for the same thing. Positions are computed here and drawn with cytoscape preset: no physics, so a station is always in the same place when you come back to it. Loop legs run straight; the legs that would otherwise be read as passing through a building bow clear of it.

Sprites. Ten skins, one per station, authored to the house recipe — the girding frame drawn first and a semi-opaque wall washed over it, so the frame reads through and the themed node body tints the building. The document keeps sheet 1's one metaphor break: it is the only station that is not a building but a window with its DOM rising in plates, and the link is that topmost plate alone. Both palettes are baked at build time and swapped with the page's theme, the register's pattern exactly.

What this shows that sheet 1 cannot. Sheet 1 proves the loop is a circuit; here it has an order. The hall is tapped two times by the overlays and those taps fire at different bays — the perch hears onStart before any view has changed, the view hears onSuccess after every view has — which is why .active can flip before the page does. The two overlays never light a loop leg at all, in 12 steps. And the last step is honest about the one leg this package does not own: core writes the url; lit-ui-router's part of that wire is the listen() that carries the next back-button press in.

What is editorial. The ring and where the overlays stand; the sprite drawings and the colours; the Lucide glyphs (ISC, restroked) that mark the lane's controls and panel heads; the narration sentences and this prose. The stations, the legs, the order of the steps, every line number, every excerpt and every count are the plate's.