Back to corpus
research noteexperiment writeup candidatescore 18
LUME Derived Lanes After Capture Spec
This spec defines what the system is allowed to derive after a strict-real capture bundle exists. It prevents a common failure mode: treating generated outputs, semantic candidates, or learned summaries as if they were the original evidence.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
This spec defines what the system is allowed to derive after a strict-real capture bundle exists. It prevents a common failure mode: treating generated outputs, semantic candidates, or learned summaries as if they were the original evidence.
Derived lanes may explain, summarize, transform, annotate, map, or propose. They cannot replace required physical lanes, source identity, camera topology, operator review, or K11 command promotion.
Template candidates become stable templates only after repeated sessions and review.
DEMON must not receive raw camera frames as truth, must not send Rekordbox commands, and must not replace SAN or reconstruction evidence.
Room reconstruction cannot satisfy required body evidence lanes and cannot claim the first real body reconstruction by itself.
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.