{ "version": 1, "note": "Caps are never raised. A red p95FrameIntervalMs on this box is noise before it is a finding \u2014 the GPU here never leaves 500 MHz of a possible 2,725, so a desktop cell on the vsync deadline flips between 16.8 and 33.3 ms with geometry identical to the digit; judge on maxTriangles and maxDrawCalls. The five scene names are bound to board identity in performance-budget.mjs: every scene asserts the data-board of the pressed tab, because ?city= falls back to the first board rather than failing and a bay-area cell that silently measured California would pass its cap by a factor of six. `california-one` is the merged board and its caps are RECORDED, not copied: measured 352,927 triangles / 420 draws desktop and 352,527 / 416 mobile on its first full run, set here with headroom in the same spirit as bay-area and socal. They were briefly copied from `california`, which is wrong for the reason that cell's own numbers are wrong for this board \u2014 `california` describes a state with no cities on it, and this one carries 56,327 buildings, two ports and both metros' bridges and airports. No existing cap was raised to accommodate it. Since the frustum-cull work, geometry submitted is a function of the camera: the terrain is a grid of 17 chunk meshes plus one un-chunked caster and the city is packed by district against the view frustum, so `maxDrawCalls` and `maxTriangles` are maxima over the sample window and the terrain half of the draw count is bounded at +17 by the object count rather than by a measurement. The change is directional \u2014 it can only remove geometry that was drawn before \u2014 so performance-budget.mjs's assumption that geometry is not a function of the camera path still holds in the only form it was ever relied on. No cap moved for it either. `california-one-basin` is the merged board over the Los Angeles basin from eleven kilometres, and it exists because that pose is the board's worst and nothing stood on it: six poses over that basin were measured over the 400,000 cap, one at 761,648, all reachable from the board's own chapters. Its caps are NOT recorded from a first run in the way bay-area and socal were \u2014 they are `california-one`'s own 400,000/460/455, deliberately, because the question this cell asks is not 'has this pose regressed' but 'is this board still inside the budget it claims'. Measured at 390,598 triangles on the run that added it, a 2.3% margin held by one constant (`LOT_BUDGET`), which is the tightest thing in this file and the reason it is now watched.", "scenes": { "california": { "desktop": { "p95FrameIntervalMs": 16.7, "maxDrawCalls": 480, "maxTriangles": 440000 }, "mobile": { "p95FrameIntervalMs": 33.3, "maxDrawCalls": 415, "maxTriangles": 430000 } }, "california-drive": { "desktop": { "p95FrameIntervalMs": 16.7, "maxDrawCalls": 480, "maxTriangles": 430000 }, "mobile": { "p95FrameIntervalMs": 33.3, "maxDrawCalls": 280, "maxTriangles": 420000 } }, "office": { "desktop": { "p95FrameIntervalMs": 16.7, "maxDrawCalls": 550, "maxTriangles": 550000 }, "mobile": { "p95FrameIntervalMs": 33.3, "maxDrawCalls": 520, "maxTriangles": 200000 } }, "bay-area": { "desktop": { "p95FrameIntervalMs": 16.7, "maxDrawCalls": 320, "maxTriangles": 2600000 }, "mobile": { "p95FrameIntervalMs": 33.3, "maxDrawCalls": 240, "maxTriangles": 1450000 } }, "socal": { "desktop": { "p95FrameIntervalMs": 16.7, "maxDrawCalls": 320, "maxTriangles": 1700000 }, "mobile": { "p95FrameIntervalMs": 33.3, "maxDrawCalls": 170, "maxTriangles": 900000 } }, "california-one": { "desktop": { "p95FrameIntervalMs": 16.7, "maxDrawCalls": 460, "maxTriangles": 400000 }, "mobile": { "p95FrameIntervalMs": 33.3, "maxDrawCalls": 455, "maxTriangles": 400000 } }, "california-one-basin": { "desktop": { "p95FrameIntervalMs": 16.7, "maxDrawCalls": 460, "maxTriangles": 400000 }, "mobile": { "p95FrameIntervalMs": 33.3, "maxDrawCalls": 455, "maxTriangles": 400000 } } } }