Back to corpus
technical notebacklog referencescore 30
HANDOFF: Mac4 Unity Takeover for Codex
Date: 2026-04-04 Authoring machine: `[home]` on Mac1 Target machine: Mac4 Primary target project: `[home-path]` on Mac4 Companion reference project: `Desktop/DepthReactiveVisuals/` on Mac1
Full HTML reader
Read the full artifact
Extracted abstract or opening context
Date: 2026-04-04 Authoring machine: `[home]` on Mac1 Target machine: Mac4 Primary target project: `[home-path]` on Mac4 Companion reference project: `Desktop/DepthReactiveVisuals/` on Mac1
1. Open the actual Unity project on Mac4. 2. identify every compile/runtime/configuration problem that Claude Code left behind. 3. fix the errors. 4. clean up the questionable or placeholder work. 5. produce a minimal but real Unity scene that runs.
This handoff is intentionally more skeptical than the earlier general `HANDOFF.md`.
- The local machine has a partial source bundle at: - `[home]/Desktop/DepthReactiveVisuals/` - That local bundle contains: - `24` C# files - `3` compute shaders - `2` docs - `2` TouchDesigner source files plus the earlier general handoff - The local bundle is **not** a full Unity project: - no `Packages/manifest.json` - local `ProjectSettings/` exists but is empty - no `.unity` scenes - no `.vfx` assets - no `.prefab` assets - no `.asset` assets - no `.asmdef` files - no `.meta` files - Mac4 was **not reachable by SSH** during this handoff pass. - `ssh mac4` timed out. - Therefore this document separates: - `confirmed now` - `claimed previously` - `must verify on Mac4 before trusting`
Treat any statement about the live Mac4 Unity project as untrusted until Codex re-verifies it on Mac4.
Promotion decision
What has to happen next
Keep in the searchable backlog until it intersects a live paper or system.
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.