← System records

Spatial computing · Native iOS · Performance

FocalaneSpatialLab

The spatial research twin of FocalaneCapture: an isolated lab testing whether an iPhone can remember a filming space well enough to restore a setup and explain what moved.

Part of the Focalane family.

State
Native spatial research
Form
Case study
Updated
2026-09-24
  1. Sense
  2. Reconstruct
  3. Compare
  4. Propose to FocalaneCapture

Screens

All screens in the gallery →
FocalaneSpatialLab research page headed “A camera that remembers the room.” beside an illustrative diagram of a filming space with labeled anchors.
FocalaneSpatialLab, the spatial research twin of FocalaneCapture. Local build, captured 24 September 2026. The diagram is illustrative; no private room capture is shown.
FocalaneSpatialLab section “Turn a room into a filming decision.”: four steps, Measure where, Understand what, Remember which one, and Decide what helps the shot, above a note that physical prediction is not creative simulation.
The four research layers. Local build, captured 24 September 2026.
FocalaneSpatialLab section “The lab may propose. FocalaneCapture decides.”: private spatial assets flow to a bounded worker, whose proposal passes a separate gate before FocalaneCapture accepts it.
The authority line: the lab proposes, and FocalaneCapture decides. Local build, captured 24 September 2026.
01

Problem

A creator's filming setup drifts between sessions, and spatial capture can look functional while hiding cadence, energy, thermal, and data-integrity costs on the device.

02

Actual state

Contracts, the local worker, and setup comparison pass on synthetic fixtures, and iPhone 16 Pro depth, mesh, and relocalization gates passed within their recorded scope. Performance and thermal causality remain open pending controlled device measurements.

03

System architecture

A separate research app and a bounded Mac worker turn capture-owned spatial evidence into setup proposals. FocalaneCapture accepts, rejects, or ignores each proposal; the lab owns no production camera, accepted setup, or product state.

04

Christian's role

Audited the native pipeline and defined controlled measurement and thermal-policy gates.

05

Verified evidence

source-reviewNative capture and cadence path audited
06

Safety, privacy, and authority boundary

  • No thermal cause is claimed from uncontrolled runs
  • Illustrative diagrams are not measured geometry
  • Proposals only: FocalaneCapture keeps camera and setup authority
07

Current limitation

  • Controlled cooled, unplugged target-device baselines are incomplete.
  • The latest performance build is installed; its attended run is pending.
08

Next milestone

Complete controlled target-device performance baselines.