Back to corpus
technical noteexperiment writeup candidatescore 44
HANDOFF: Depth-Reactive Visuals + LUME Hardware Product + Creative Agency
**Date**: 2026-04-04 **Author**: Mohamed Diomande (via Claude Opus) **Recipient**: Codex (continuation agent) **Session**: b8e3a146 — Full-day session covering three interconnected initiatives
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Date**: 2026-04-04 **Author**: Mohamed Diomande (via Claude Opus) **Recipient**: Codex (continuation agent) **Session**: b8e3a146 — Full-day session covering three interconnected initiatives
1. [Overview — Three Initiatives](#1-overview) 2. [Initiative 1: Depth-Reactive Interactive Visual System](#2-depth-reactive) 3. [Initiative 2: LUME Hardware Product](#3-lume) 4. [Initiative 3: Diomande Creative Agency](#4-agency) 5. [Infrastructure State](#5-infrastructure) 6. [File Inventory](#6-files) 7. [What's Working](#7-working) 8. [What's Blocked / Incomplete](#8-blocked) 9. [Next Steps (Priority Order)](#9-next-steps) 10. [Reference Material](#10-references)
This session started from an Instagram reel by Duncan Fewkes showing depth-reactive interactive installations, and evolved into three interconnected projects:
1. **Depth-Reactive Visual System** — A Unity 6 + TouchDesigner pipeline that uses depth cameras to create real-time interactive particle/fluid visuals driven by body movement and audio 2. **LUME** — A $1,299 standalone hardware product (Jetson Orin Nano + Orbbec Femto Bolt) that packages the visual system into a wall-mounted device for dance studios, venues, and content creators 3. **Diomande Creative** — A new media art agency inspired by Hybrid Xperience, Projection Mapping World, and the immersive art sector (teamLab, Mercer Labs, ARTECHOUSE)
All three share the same codebase and technical pipeline. The depth-reactive system IS the software that runs on LUME, and the agency uses it as portfolio work.
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.