Back to corpus
technical noteexperiment writeup candidatescore 40

Mac5 Reconstruction Worker

Latest execution: 2026-06-06 Mac4-first prerequisites passed, local AirDeck artifact verification passed after repairing the mirrored recording-status link, and Mac5 completed a fresh non-placeholder one-frame SAM3DBody reconstruction from an already staged K11 bundle. Live K11 upload/return could not run because SSH to `[ip]:22` timed out during this pass.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

Status: verified K11 return lane, review index, and dry-run AirDeck mapping on 2026-06-01. Latest execution: 2026-06-06 Mac4-first prerequisites passed, local AirDeck artifact verification passed after repairing the mirrored recording-status link, and Mac5 completed a fresh non-placeholder one-frame SAM3DBody reconstruction from an already staged K11 bundle. Live K11 upload/return could not run because SSH to `[ip]:22` timed out during this pass. Current wiring update: on 2026-06-10 the Mac4-first live gate turned green after the Chrome/Web MIDI wrapper was fixed. The wrapper now proves the MRT2 page by clicking the page's own `Connect MIDI` control through CDP DOM/Input, then validating a fresh `LUME MRT2 Proof Sink` browser proof. The saved unlock artifact is: It reports `completion_ready=true`, `mac5_heavy_reconstruction_allowed=true`, `wrapper_status=pass`, `audit_status=pass`, and no failed requirements. Mac5 is now allowed by the Mac4-first gate, but real heavy reconstruction still needs a verified real external/multi-angle capture session. K11 remains the only Rekordbox/AirDeck command gate. Mac4 remains read-only. Mac2 is still staged as the external-only Insta360 room-wide angle host, but it must enumerate a real eligible external camera before its lane counts as capture evidence. This page documents the current K11 -> Mac5 -> K11 offline reconstruction path. It is an implementation note, not a future architecture sketch.

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.