How this lab is being built

Measure before deciding what belongs online.

An earlier inventory of the v025 authoring scene counted 2,536,921 visible triangles before modifiers. It made the first constraint concrete: the browser needed a carefully prepared version of the room, with detail allocated to what a visitor can actually see.

Authoring reference

v025

Recorded source identity

01E33A7244A1E93DE52E91065F61A900AD160FA65141F9D1059C5957FE190EBA

Historical scene inventory

2,536,921 triangles before modifiers

Give the first view only what it needs.

The lab core in this build contains 34,266 triangles and weighs 328,328 bytes. It establishes the space before the smaller details arrive. A reduced dressing slice adds 189,452 triangles and 2,001,164 bytes only after the greeting becomes interactive. The XRP bench artifact adds another 37,330 triangles and 245,392 bytes on the same deferred path. These are the sizes of the shipped modules, read directly from the asset manifest. They describe the loading strategy; they do not measure the finished appearance.

Lab core

34,266 triangles

Transfer asset

328,328 bytes

Deferred dressing

2,001,164 bytes after interactivity

Deferred XRP artifact

245,392 bytes after interactivity

Scope

Room first; supporting detail follows

Make the movement feel authored.

The hero composition uses CAM09, recorded as a physical camera contract with a 60 mm focal length and a 72 mm horizontal sensor. Keeping those values explicit gives the browser a stable projection reference while the viewport changes shape.

The camera route connects the room, the sharpener, the robot, the software desk and the Vision stop. Scrolling and direct shortcuts lead into the same journey. A separate project page carries the longer explanation, so the camera never has to become the only way to reach the work.

Camera

CAM09

Focal length

60 mm

Horizontal sensor

72 mm

Record the awkward result as well as the good one.

The 3 September build note recorded 5 cache-disabled local runs at 20 Mbps and 50 ms latency. The slowest route unlock was 4.450 seconds and the slowest verified 500 ms responsive window completed by 4.950 seconds. The highest p95 frame interval was 8.5 ms. An earlier, pre-FIX1 5.3-minute check completed 53 full project-to-lab loops.

The earlier route-cycling check ended in the adaptive fallback quality tier. The 3 September record described this as an observation that remains open for investigation. These figures describe that earlier checkpoint; they are not measurements of the page you are visiting now.

Slowest cold route unlock

4.45 seconds

Slowest responsive window

4.95 seconds

Highest p95 frame interval

8.5 ms

Historical extended check

53 complete loops

Observation in that record

Adaptive quality ended at fallback

Let the atmosphere lead to something substantial.

The seven project pages now sit alongside the lab. Each can be opened directly, read without JavaScript and shared independently. Original footage, drawings, source-derived plots and specific engineering decisions give the visual journey a destination worth exploring.

Reduced motion, keyboard navigation and recovery paths are part of the same design. They keep the portfolio useful across different devices and ways of browsing, while the richer scene remains available to visitors who want it.