Back to corpus
technical noteexperiment writeup candidatescore 52

LUME Full System Goals Execution Prompt

Use this prompt when handing the LUME project to another agent or resuming after a break. The job is not to invent a new architecture. The job is to continue the existing one, preserve the safety boundaries, and drive the system toward the first real multi-device capture, reconstruction, and learning loop.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

Use this prompt when handing the LUME project to another agent or resuming after a break. The job is not to invent a new architecture. The job is to continue the existing one, preserve the safety boundaries, and drive the system toward the first real multi-device capture, reconstruction, and learning loop. Continue building the full LUME computational choreography system as a local, Tailscale-connected, multi-device performance stack. The system must convert real body evidence into safe DJ control, visual response, music adaptation, reconstruction, semantic memory, and future generated control curves without confusing evidence, command authority, and learned interpretation. The current immediate task is to keep writing, hardening, and clarifying this execution surface while Mohamed is away, then be ready to run the home-return validation path when the physical devices are positioned again. Before claiming progress, inspect the relevant report instead of relying on this prose. Reports can drift because some are summaries of other reports, and remote parity copies/readbacks can lag behind local updates. When reports disagree, use this procedure before changing claims in this file.

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.