LUME Post-Mac4 Master Goal

LUME Post-Mac4 Master Goal

Generated: 2026-06-10T14:37:53Z

Objective

Build the full post-Mac4 LUME system as a multi-device capture, control, reconstruction, learning, and performance loop without breaking the command boundary. K11 remains the only Rekordbox/AirDeck command gate. Mac4 remains read-only for BodyTruth, ENTHEA, Unity visuals, MRT2-style audio mapping, DEMON control curves, and template output. Mac5 reconstructs and learns offline only after real synchronized evidence passes strict preflight, operator review, and explicit heavy-reconstruction allow.

Cloud VM is out of scope for this phase. The active mesh is local devices plus Tailscale.

Current State

Code and contract surfaces are ready. The Mac4-first unlock is green, the post-Mac4 contract coverage audit passes, Mac5 tooling is verified, and the current refresh surface now carries Mac5 sync, strict real-bundle preflight, full-goal audit, and the operator action packet together.

The system is not complete. Current status is `waiting_for_physical_lanes`. Strict real-bundle preflight is `blocked_real_bundle_preflight`, with `heavy_reconstruction_preflight_ready=false`, because the existing bundle still contains fixture/smoke-origin evidence. No heavy reconstruction has started.

Device Roles

Required First Real Evidence

The first real capture cannot proceed to heavy reconstruction until these four physical lanes are replaced with strict real evidence:

• `iphone_16_plus_motionmix`
• `iphone_14_pro_max_motionmix`
• `mac2_insta360_room_wide`
• `mac4_bodytruth_depth_or_wide`

K11 is the required command/safety lane and is currently treated as proven by the latest refresh, but it still gets rechecked at home return before capture.

Stage Gates

Stage 1 is already complete: Mac4-first green unlock and K11-only command boundary are frozen.

Stage 2 is already complete: the shared session-bundle contract covers K11, phones, iPads, Insta360, Mac4 BodyTruth, SAN rows, timestamps, calibration, source manifests, reconstruction requests, and safety flags.

Stage 3 is ready: refresh and action-packet tooling can tell the operator exactly which physical lanes are missing without starting capture or reconstruction.

Stage 4 is next: when devices are available at home, run the home-return refresh with live checks, verify K11, prove the two required iPhone MotionMix pose streams, prove Mac2/Insta360 nonzero video, and prove Mac4 BodyTruth pose/video.

Stage 5 follows immediately after Stage 4: assemble a real capture bundle from copied physical evidence, not fixture paths, and run the strict real-bundle preflight.

Stage 6 is gated: only after strict preflight reports `heavy_reconstruction_preflight_ready=true` may the operator arm Mac5. Placeholder proof can still run for plumbing. Heavy `auto` reconstruction additionally requires explicit `--allow-heavy-reconstruction`.

Stage 7 is learning: Mac5 output is audited by the reconstruction-learning audit. The system can only claim it learned if the audit sees non-placeholder successful reconstruction frames from a strict real bundle.

Stage 8 is promotion: only after learning audit passes do reconstructed templates, DEMON curves, ENTHEA/Unity visuals, MRT2 mappings, SAN policy rows, and N'Ko/MnKO semantic annotations become candidates for controlled live rehearsal.

Normal Command Surface

Preferred current-state refresh:

cd [home]/Desktop/lume-commerce/viz/lume-pcloud
python3 tools/lume-mac5-reconstruction/refresh_lume_post_mac4_home_return_state.py \
  --report-json [home]/Desktop/MotionMix/lume-wiring/lume_post_mac4_home_return_state_refresh_current.json \
  --live-checks \
  --probe-mac2

Current state reports:

• `[home]/Desktop/MotionMix/lume-wiring/lume_post_mac4_home_return_state_refresh_current.json`
• `[home]/Desktop/MotionMix/lume-wiring/lume_post_mac4_home_return_action_packet_current.json`
• `[home]/Desktop/MotionMix/lume-wiring/lume_post_mac4_real_bundle_preflight_current.json`
• `[home]/Desktop/MotionMix/lume-wiring/lume_post_mac4_full_system_goal_audit_current.json`

Definition Of Done

The goal is complete only when all of these are true:

• Current refresh is no longer waiting for physical lanes.
• Required first-run lanes have strict real evidence, not fixture evidence.
• Real assembled bundle exists and passes the strict real-bundle preflight.
• Mac5 reconstruction is run only after operator review and explicit allow.
• Reconstruction-learning audit reports real non-placeholder learning.
• K11 remains the only command gate throughout.
• Mac4 remains read-only throughout.
• Output lanes for ENTHEA/Unity, MRT2, DEMON, templates, SAN, and N'Ko/MnKO are derived from audited evidence rather than replacing evidence.

Immediate Next Work While Away From Devices

No more physical reachability work is useful until the devices are actually awake and reachable. The best work while away is documentation and code hardening: keep the master goal current, verify the current refresh/action/preflight reports, keep Mac5/Mac2 sync tooling green, and prepare the home-return operator path so the first real session is one command plus device placement.

Operator Command Surface Update

Updated: 2026-06-10T14:47Z

The current action packet and refresh reports now emit copy-paste-safe commands that include the project `cd`, explicit `--wiring-dir`, and current report paths. The preferred live refresh command is available as `refresh_home_return_state_live` in `[home]/Desktop/MotionMix/lume-wiring/lume_post_mac4_home_return_action_packet_current.json`.

This update does not change the stage gate. Current status remains `waiting_for_physical_lanes`; strict preflight remains `blocked_real_bundle_preflight`; Mac5 is tool-verified; Mac2 has the updated helper scripts and current reports.

Operator Surface Audit

Updated: 2026-06-10T15:01Z

Added a dedicated operator-surface audit at `[home]/Desktop/lume-commerce/viz/lume-pcloud/tools/lume-mac5-reconstruction/audit_lume_post_mac4_operator_surface.py`. It verifies that the action packet and state refresh are fresh, command strings are portable, safety flags preserve the K11-only command boundary, Mac5 sync is green, strict preflight remains blocked until real evidence exists, and missing physical lanes are represented honestly.

Current audit report: `[home]/Desktop/MotionMix/lume-wiring/lume_post_mac4_operator_surface_audit_current.json`.

Current audit status is `operator_surface_ready_waiting_for_physical_lanes`. This proves the operator surface is ready for home return, but it does not prove physical capture readiness. The missing physical lanes remain iPhone 16 Plus MotionMix, iPhone 14 Pro Max MotionMix, Mac2/Insta360, and Mac4 BodyTruth.

First-Real-Capture Topology Gate

Updated: 2026-06-10T15:16Z

The session-bundle verifier now deeply audits `raw/calibration/camera_topology.json` before any bundle can become capture/reconstruction ready. Required physical lanes must have explicit topology rows with `camera_role`, unique `view_angle_label`, `sync_method`, `room_anchor_notes`, positive `calibration_confidence`, and non-synthetic calibration status.

This does not block dry-run plumbing. It does block the exact failure mode we want to avoid: treating a fixture-like or under-calibrated source plan as a real Mac5 reconstruction input.

Verification after this update: local affected smokes passed; Mac5 copied 41 tools and 18 reports, remote compile passed, and all 7 remote smokes passed; Mac2 report readback matches the refreshed current reports.

Current state remains `operator_surface_ready_waiting_for_physical_lanes`. The missing physical lanes are still iPhone 16 Plus MotionMix, iPhone 14 Pro Max MotionMix, Mac2/Insta360, and Mac4 BodyTruth. Heavy reconstruction remains disallowed.

Home-Return Validation And Remote Parity

Updated: 2026-06-10T15:34Z

The current validation path now gates first-real-capture readiness on both source-plan evidence and camera topology. Required sources must not remain placeholders, and required topology must include roles, unique view labels, sync methods, room-anchor notes, positive calibration confidence, and non-synthetic calibration before capture/reconstruction readiness can pass.

The validation path also reads the strict real-bundle preflight before allowing heavy reconstruction. This prevents an old structurally valid bundle from becoming a Mac5 heavy-reconstruction unlock while strict preflight still reports fixture/stub evidence.

Current final reports:

• Mac5 sync: `mac5_post_mac4_tools_verified` at `2026-06-10T15:33:35Z`.
• Home-return state refresh: `waiting_for_physical_lanes`.
• Action packet: `waiting_for_physical_lanes`.
• Home-return validation: `waiting_for_home_devices`, `first_real_capture_ready=false`, `heavy_reconstruction_allowed_now=false`.
• Strict real-bundle preflight: `blocked_real_bundle_preflight`, `heavy_reconstruction_preflight_ready=false`.
• Full-system goal audit: `waiting_for_required_real_capture_lanes`, `goal_complete=false`.
• Operator audit: `operator_surface_ready_waiting_for_physical_lanes` at `2026-06-10T15:33:59Z`.

Mac5 copied 43 tools and 20 reports, remote compile passed, and all remote smokes passed. Mac2 and Mac5 both read back the same final current report states. Mac2 final sync used temp-file copy plus atomic `mv` because direct scp overwrite can fail on `dataless` remote report files.

The missing required physical lanes remain iPhone 16 Plus MotionMix, iPhone 14 Pro Max MotionMix, Mac2/Insta360 room-wide nonzero video, and Mac4 BodyTruth pose/video. No capture, reconstruction, BodyTruth write, MIDI/AirDeck, or Rekordbox command path was executed.

Remote Report Parity

Updated: 2026-06-10T15:52Z

Added a dedicated remote report parity verifier:

cd [home]/Desktop/lume-commerce/viz/lume-pcloud
python3 tools/lume-mac5-reconstruction/verify_lume_post_mac4_remote_report_parity.py \
  --wiring-dir [home]/Desktop/MotionMix/lume-wiring \
  --report-json [home]/Desktop/MotionMix/lume-wiring/lume_post_mac4_remote_report_parity_current.json

The verifier copies current reports to Mac2 and Mac5 using temp-file copy plus atomic remote `mv`, then reads back the core status JSON files and compares them against local truth. This is now the formal path for the Mac2 `dataless` overwrite issue.

Current remote parity report:

• `[home]/Desktop/MotionMix/lume-wiring/lume_post_mac4_remote_report_parity_current.json`
• Status: `remote_report_parity_verified`
• Created: `2026-06-10T15:52:26Z`
• Hosts OK: `true`

The action packet now exposes `verify_remote_report_parity`, and the operator-surface audit requires it to be green. The verifier intentionally compares core state reports, not the operator audit itself, so the operator audit can depend on parity without creating a circular freshness loop.

Final current state after this update:

• Mac5 sync: `mac5_post_mac4_tools_verified` at `2026-06-10T15:51:22Z`.
• Home-return state refresh: `waiting_for_physical_lanes` at `2026-06-10T15:51:43Z`.
• Remote report parity: `remote_report_parity_verified` at `2026-06-10T15:52:26Z`.
• Operator surface audit: `operator_surface_ready_waiting_for_physical_lanes` at `2026-06-10T15:52:33Z`.

Mac5 copied 45 tools and 22 reports, remote compile passed, and all remote smokes passed including the remote report parity smoke. Mac2 and Mac5 both read back the final current core report statuses. The missing required physical lanes remain iPhone 16 Plus MotionMix, iPhone 14 Pro Max MotionMix, Mac2/Insta360, and Mac4 BodyTruth. Heavy reconstruction remains disallowed.

Home-Return Execution Map

Updated: 2026-06-10T15:58Z

The current home-return execution map lives at:

- `[home]/Desktop/MotionMix/lume-wiring/lume-post-mac4-home-return-execution-map-current.md`

It is the operator-facing bridge between the architecture and the next physical session. It defines device placement, lane ownership, required evidence, the live refresh command, the one-pass home-return sequence command, strict real-bundle criteria, and the success state. The architecture remains unchanged: K11 commands, Mac4 observes read-only, Mac5 reconstructs only after real evidence and explicit allow.

Handoff Docs In Sync Manifests

Updated: 2026-06-10T16:20Z

The execution map and master goal are now first-class sync artifacts, not manual one-off copies.

Mac5 return sync includes:

• `[home]/Desktop/MotionMix/lume-wiring/lume-post-mac4-home-return-execution-map-current.md`
• `[home]/Desktop/MotionMix/lume-wiring/lume-post-mac4-master-goal-20260610T143753Z.md`

Remote report parity includes the same two documents in its temp-file plus atomic remote `mv` copy set for Mac2 and Mac5. The parity readback still compares only core status-bearing JSON files, avoiding circular audit dependencies, but the docs now travel with every standard parity refresh.

Verification after this update:

• Mac5 sync report `2026-06-10T16:17:14Z`: `mac5_post_mac4_tools_verified`, 45 tools copied, 24 reports/docs copied, remote compile passed, 9 remote smokes passed.
• Remote parity report `2026-06-10T16:18:49Z`: `remote_report_parity_verified`, hosts OK, Mac2 copied 20 files, Mac5 copied 20 files, zero mismatches.
• Operator audit report `2026-06-10T16:19:21Z`: `operator_surface_ready_waiting_for_physical_lanes`, failure count 0.

This does not change the physical stage gate. The system is still waiting for iPhone 16 Plus MotionMix, iPhone 14 Pro Max MotionMix, Mac2/Insta360, and Mac4 BodyTruth real evidence. Heavy reconstruction remains disallowed.