THE CODEC
BECAME THE
CANVAS.
Pixels became codec math. Ordered primitives changed the reconstruction. The adapter recomposed the result into video again.
FOLLOW THE TRANSFORMATION ↓Change the
reconstruction.
The experiment treated RGBA and YUV as two views of the same data. The adapter crossed that boundary; the codec primitives changed selected reconstruction decisions; the decoder and output adapter turned the result back into pixels.
This was not a conventional beauty filter painted over a finished frame. The research entered AV1’s segmentation, reference, and in-loop reconstruction surfaces so the codec itself became the transformation medium.
The compatibility goal was an ordinary, stock-decodable AV1 result. That final cross-decoder guarantee must be revalidated when the source is reconstructed; the public page does not turn historical intent into a current certification.
Same idea.
Wrong seam.
No result.
Several early placements were technically active but visually ineffective because later codec stages corrected the change away. Moving the chroma constraint to the post-CDEF reconstruction seam changed the outcome.
Stacking order is not polish. It is part of the contract. The orchestrator must know which representation exists at each stage and which later primitive can weaken or erase an earlier one.
Do not crack
the sealed engine.
When an engine cannot or should not be opened, adapters can wrap its public inputs, outputs, commands, and events. An atom kit can add missing features, replace behavior at the seam, or require cryptographic proof before an action is allowed.
The method is powerful because the original engine stays intact. Its limit is equally important: the outside composition can only control boundaries the engine actually exposes.
READ THE PUBLIC TECHNIQUE ↗Working research.
Recovering source.
The prototype processed frames, but its surviving repository preserved compiled artifacts instead of a reproducible source checkout. The Lucerna Labs repository records the architecture and recovery gates without pretending those artifacts are developer-ready source.
Executable and compiled evidence
`av1-avatar`, adapter-test, `cam-avatar`, and focused avatar primitive artifacts remain as evidence of the historical build.
A trustworthy source tree
No current manifest-and-source checkout can reproduce the application. That is why the repository is marked source recovery.
Clean, testable reconstruction
Pinned libaom, reviewable patches, neutral fixtures, drift tests, stock-decoder checks, and a humane development surface.