The sequence below runs in this page. Drag the bar or pick a step. The room outlines, names and dimensions come from the same reviewed files the build reads. None of it is placeholder art.
Skip to the house, photographed → four views, every one held to the plan



Each page holds one stage and stands on its own. The running index of every sealed run, payload directory, generator and gate behind them is in docs/INDEX.md.
Paper, photographed at an angle under a window. What came off it, and what turned out to be wrong with what came off it.
The sheets traced again from the numbers written on them, built into a solid that has a back, and photographed as the house it says it is.
No photograph of this house exists, so the first one was generated. Then seven video models, a solve gate, and eight reconstructions you can move the camera in.
A solved frame carried to a camera that never existed. Measured by how much of the original survives the trip.
Fourteen attempts at the three sides of the house nothing had ever seen, in the order they were tried, failures kept.
Nine room plates from before the reconstruction, and the scripted tour.
Fusing the R4 arc with three new clips put 104 of 104 images into a single model on the first try: 33,572 points at 0.889 px, with lateral camera coverage going from 6.5 to about 13.8 units.
That costs 1.34 dB on the R4 arc in exchange for roughly three times the view volume. R4's worst endpoint got 1.19 dB better, because every new clip sees it.
The walk-up view a person actually looks from.
Both edges came back with real detail instead of invented blobs.
Not a floater problem. No capture yet sees the near ground at a grazing angle.
A clip whose camera is low and pitched down while translating, so a driveway approach dolly at −20 to −25°. That is a new control family and a paid decision, so it is not in this build.
Also on the record: one r5 clip completed and billed at $0.50625 with 175.6 s of inference, and then the result store returned HTTP 500 on all 23 retrieval attempts over 24 minutes. It was left out of the fusion rather than worked around. Request 019fd250-e52d-7713-b0f1-63e242925bc2 is still retryable if that store recovers.
Each one is a manifest with a per-file sha256 index, an authority boundary and a spend record.
Across two floors, 33 of them carrying a legible dimension string off the sheet.
Counted from the shipped graph, 117 plus 86. These are room boundaries rather than traced walls; the traced walls are kept in their own manifest as rejected analysis.