LIM-RPS as Constraint

LIM-RPS as Constraint

LIM-RPS: Lipschitz-constrained Implicit Map for Recursive Polymodal Synthesis.

The name is technical but the principle is artistic: LUME's visual and musical
responses must be bounded, memoryful, multimodal, and synthesizing. This is
the difference between a sensor spike and a choreographic response.

The Four Properties

Lipschitz (bounded rate of change)

Outputs cannot change arbitrarily fast. Every primitive, template, and effect has
an attack and release rate. If the wave target jumps from 0.0 to 1.0, the actual
value moves toward it at a controlled rate. If burst falls, it decays rather
than disappearing in one frame.

This prevents sensor jitter from becoming visual violence. It gives the visuals
the musical quality of attack, sustain, and release. A hand moving fast produces
an increase in wave that builds and then settles. A sensor dropout does not
immediately blank the visual. The body is heard as a continuous voice, not a
series of disconnected shouts.

Implicit map (continuous field, not a switch table)

The system does not use one rigid table that maps a single gesture to a single
effect. Instead, it evaluates a continuous field. BodyTruth, primitives,
templates, memory, and confidence become effect weights. Color shift, pressure
glow, wall bend, ribbon impulse, calm field, contour focus, fluid impulse, and
spark damping emerge from that map.

The result is more like a mixer than a switchboard. Multiple body qualities
contribute simultaneously. A moment that is 0.6 wave and 0.4 lean produces a
different visual than 0.9 wave and 0.0 lean. The aesthetic richness comes from
this continuous composition, not from a discrete command system.

Recursive (present depends on the past)

A hold is defined by duration. A wave is partly defined by side alternation over
time. Recovery is defined by a drop from previous activity. False reactivity is
often recognized by inconsistency across time and sources.

Without recursive memory, the system sees poses but not phrases. This is the
difference between "this frame has high arm velocity" and "the arm has been
rising for 200ms and is now near the shoulder — this is a wave onset."

Polymodal (multiple sources, no single authority)

Femto/Mega body, mocopi skeleton, pCloud motion, iPhones, Watch, audio, and
labels can all contribute. No one source is treated as eternal authority.
The authority changes with freshness and confidence. Mocopi absence is a valid
operating mode; it does not collapse the stack.

Synthesis is the output: the fused belief about the body drives all output
domains simultaneously. The same gesture that informs color shift also informs
audio param routing and (if promoted) AirDeck command eligibility.

LIM-RPS Is Historical Vocabulary Plus Aesthetic Constraint

The repo contains real LIM-RPS vocabulary, especially in the Echelon
`motion-bridge/src/lim_rps.rs` lane and older manuscripts. The current runtime,
however, should be documented by concrete source names: `EchelonCore`,
`LatentUpdater`, `SimpleLatentUpdater`, `LearnedLatentUpdater`,
`DellLatentUpdater`, `SANPipeline`, `DiffusionService`, and `ClaimBridge`.

`DellLatentUpdater` exists as one Rust backend. That does not prove that the
entire LUME stack is a single deployed LIM-RPS model, nor that every path uses
DELL at runtime.

In the visual/performance layer (Set C), LIM-RPS is the operating philosophy:
every visual decision should be bounded, remember the past, accept multiple
sources of evidence, and synthesize rather than switch.

Use LIM-RPS as a constraint vocabulary, not as a catch-all implementation claim.
When the docs describe code, name the exact producer and consumer.

What Violates LIM-RPS

• Visual elements that jump discontinuously when a sensor value crosses a threshold
• Effects that disappear immediately when a sensor drops out
• Visuals that depend on a single sensor being present (violates polymodal)
• Any response that doesn't decay when movement stops (violates bounded)
• Any response that treats the current frame as isolated from history (violates recursive)
• Spark explosions when sensor noise crosses a threshold (violates bounded + implicit)