2 Commits

Author	SHA1	Message	Date
karti	85be0b13f8	feat: boards load before you ask for them ... The owner asked for one map, with detail arriving in the background rather than behind a wait. The interface already said one place (4bd8481: one ladder, no tab strip, no boot card). This is the world catching up: on a desktop both metros are now resident within seconds of landing, and the switch that used to be a build becomes a fog dip over a cache hit. **Measured, three runs each, California -> The Bay after an 8 s dwell:** the longest blocking task falls from **521 ms to 58 ms** (before 700/501/521, after 58/58/61) and long tasks from 2 to 1. **And the cost, stated rather than omitted.** Over ten seconds sitting on the state board: 601 frames -> ~571, p95 frame interval 18.0 -> 18.7 ms, and **one long task of ~500 ms that did not exist before**. The build is not chunked yet, so this moves a freeze from the moment of interaction to a moment nobody asked for. That is a real trade and the follow-on that removes it is chunking the build. `PREFETCH_ENABLED` in main.ts turns the whole lane off in one line. A parked board draws nothing: 371 draws per frame before the lane lands a board and 371 after, patched at the GL entry points. The performance budget reproduces every cell to the digit. **Three defects found on the way, two of them latent for a while.** 1. `environmentRig` had no idea what off-stage meant. `createScene` calls `apply()` unconditionally, two hundred lines above the `present` check, and the rig holds one probe per kind: on a key miss it convolves a new one, disposes the one the visible board is using, and repoints every applied scene at the replacement. A board built ahead of the camera is observed at its own centre — about forty minutes of apparent solar time across the state — so its key differs by construction. The board on screen would have changed colour because something invisible finished loading. Harmless until today only because every build was followed within ~800 ms by the swap that presented it. Fixed with `ApplyOptions.offstage`; the regression test was written first and failed first. 2. `mounting` was assigned and never cleared. Harmless while the only reader was the next `mountCity` wanting something to abort. It stopped being harmless the moment a second lane asked "is a foreground build in flight?", because the honest answer after the first mount of the session was permanently yes — the background lane armed exactly never, and the only symptom was a feature that silently did nothing. Found by measuring, not by reading. 3. `buildBoard`'s `onProgress` ends in `bootProgress`, which raises the switch pill. A prefetch would have put "Building The Bay Area... terrain 42%" over a visitor who did nothing — the exact chrome that removing the tab strip was for. `quiet` closes it. **The policy is pure and lives with the eviction policy it has to agree with.** `prefetchTarget` and `canAdmit` in boards.ts take scalars, never a camera, so boards.ts keeps CONTRACT section 1's no-DOM/no-WebGL/no-three promise and prefetchPolicy.test.ts can assert against the real pack bounds. Two regimes, because collapsing them was the first version's mistake: with free room the gate is simply "is there a slot", since the common path is to land on the state at 1,551 km and click a metro, and on that path a proximity trigger fires never; with the cache full — the handheld case, capacity two with California pinned — proximity is the only thing that justifies an eviction. The discs are asserted non-overlapping against the shipped bounds (92 + 146 km of reach across a 314 km gap), which is the covering-set argument residentCapacity already rests on. **Also fixed, and separately load-bearing: reconcile's flag parser lied.** It prefix-matched, so `?reconcile=palette` selected nothing and produced an empty set — indistinguishable from the flag being absent. Every photograph taken to judge a rule could have been a photograph of the unreconciled board with no way to tell. Exact names now, with a warning that says "the flag is NOT off". And two consumers were reading the raw packs beside a reconciled World: `buildLadder` derives every rung's stand-off from `focus`, and `createMinimap` was handed `entry.city` next to `handle.world`. Both now read `world.city`. Latent with the flag off — `reconciledCity` returns by identity — which is what kept it alive: it corrupts the measurement rather than announcing itself. **What I did NOT ship, having tried it.** `roads` on by default. The rule exists to stop California drawing 1,919 m freeways, and `city.roads` is not what draws them: California is the one board with `roadTraffic`, so `scene.ts:816` takes the `createFreewayWorld` branch and `createRoads` — the only reader of `Road.width` — is never called for it. The visible corridor is a deliberate atlas glyph sized so DRIVE mode can drive down it. Photographed at three chapters the rule moved Downtown LA not at all (empty diff bbox), FiDi by RMSE 0.0006, California by 0.001% of pixels; the only measurable effect anywhere was -112 triangles on Southern California. See DEFAULT_RULES for the whole argument. 1,688 + 295 tests, every gate, chapter-identity OK against the unmodified fixture, ui-smoke PASS, budget PASS with private-request checks clean on all ten cells. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-23 13:15:37 -07:00
karti	4bd8481be1	feat: the boards stop being three products ... The owner asked twice why there are still three separate boards. The honest answer, and what this round executes: **it feels like three boards, but not because the scale jumps 20x — because the three packs draw three different Californias, and the loudest difference is that the mountains are four times taller on one of them.** **THE 20x HORIZONTAL SCALE JUMP IS INVISIBLE**, and measuring that collapsed the cost of this whole round. `World.project` is a uniform scale in x/z with no vertical term, and a uniform scale leaves a perspective image identical — so a camera carried across the seam on matched true-metre offsets draws a pixel-identical horizontal frame. 1,919 -> 94 m/unit costs nothing to look at. Rescaling was never the problem. A boot card, a tab strip and a 4.17x vertical deflation were. **THE PAUSE WAS MOSTLY FAKE.** A switch covered the screen for 1,715 ms but only 608 ms blocked the main thread; the page drew 46 of 69 frames with nothing to show, because the outgoing board had already been disposed. `mountCity` now retains it: the incoming board builds BEHIND a live, interactive picture, and `stage.setScene` fires only on completion. Measured across all six directions, three runs each — boot card yes -> **no**, opaque cover 726-1,415 ms -> **0**, blank frames 21-46 -> **exactly 1**, wall clock down 12-29%, blocked main thread down 15-47%. A return to a board already seen links **zero** shader programs and blocks **zero** milliseconds: 298-312 ms of camera flight where it was ~1,600 ms behind a card. Disposal had been throwing away the shader cache too — linkProgram ran 38, 59, 78, 109, 127 across five mounts and never reused one. **The transition is a fog dip, not a crossfade**, through the `setAerialFog` seam built last round. Every both-boards-live crossfade breaks a budget — ca+sf is 2,640,307 triangles against bay-area's 2,600,000 cap — and a fade never lands inside the harness's sample window, which is the "a cap you do not measure is a cap you do not have" failure this repo already argues against. The dip costs zero triangles and zero draw calls, and it hides the 4.17x deflation, the 4,025 m projection disagreement and the vanishing 2 km freeway symbols at once, because all three happen at maximum obscuration. It is also diegetic: a descent through haze. The first dip was wrong and the photograph caught it: collapsing to 6% of board SPAN turned the whole night frame into one flat field — the exact "turns the map off" failure the risk list named. Re-anchored to 70% of camera STAND-OFF, so the coastline survives and only the relief melts. **One ladder, one places list.** 26 authored chapters become 24 rungs sorted descending by STAND-OFF, not altitude — by altitude they interleave badly and altitude cannot tell a low oblique from a high plan. The three-board tab strip is off by default; the left column is now one scrolling list of all 24 rungs under three region headings that does not change when the board does. Only which row is lit changes. Label collisions are resolved in the ladder and never in a pack, so the 29 index-aimed capture guards are untouched. The minimap stops turning through 90 degrees between boards: every board is pinned to a rectangle with California's proportions. **SF and SoCal are not regressed**, and that was the acceptance that mattered: 95.9-98.8% of board pixels are delta-0 against a baseline hash-verified identical to what the live site serves, and every one of the 34-70 surviving pixels per frame is an aircraft or a hull. **A real defect found only by photograph:** `minimap.setMarkers()` had zero call sites. Every marker on every board was gone — the LA studio's door dot, the Bay Area's eight company markers — dropped when the minimap went per-board. Typecheck, tests, budgets and the console were all green with that bug in. Also fixed: two capture presets that lied. `look.mjs`'s `glyph-la` and `glyph-sf` claimed California chapter closeups and returned SoCal and Bay Area frames, because they aimed by chapter index and the indices had moved. Aiming is now by identity, with a guard test. NOT SHIPPED, DELIBERATELY: the pack merge. At Bay density it is 34.04M triangles, 13x the highest budget — dead, not a trade. At SoCal density it is 1.99M and fits today, and the price is San Francisco rendering at 164 m lots instead of 40 m, i.e. SF looking the way SoCal looks now. SF and SoCal carry every marketing still on the site. That is the owner's decision and it is worthless as an argument and decisive as a photograph, so it ships as a measurement artifact with a side-by-side still and is wired into nothing. The four data reconciliations that would make one world honest — one exaggeration rule, roads in metres, one projection centre, one coastline convention — are behind TERA_RECONCILE, default OFF. Tests 1,570 -> 1,651, server 295. All ten budget cells pass, no cap raised. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-23 06:20:18 -07:00