# V10 Motion Rail channel

This package adapts rights-cleared, playable V3/Lilith music catalog rows into
deterministic Motion work programs. The adapter scores real rows by Rail
daypart, listener energy, mood, BPM, continuity, and recent history. It exposes
the resulting program only through a channel-bound V10 audio-lane port.

There is deliberately no bundled catalog or shuffled fallback. An empty,
invalid, stale, unavailable, or rights-ineligible catalog produces no lane
offer. Playback verification must be no older than 15 minutes at the explicit
request timestamp and cannot come from the future.

The package also owns three source-traced guided movement timelines. Stretch and
posture reset each fit one 30-second Rail phase. The exact 90-second dance break
is deliberately composed from three contiguous 30-second Rail phases so the
experience does not weaken the kernel's micro-act budget. A guided act offers
its real break-energy audio program through the same lane-only service, and its
session report records measured elapsed time, completed/skipped/not reached
steps, early exit, evidence that the expected audio source was actually held,
and the explicit absence of sensor assessment.

The presence renderer reads only current lane observations and bounded
guided-act completion reports. It sums registered step durations—not
client-claimed calories or wall-clock idle time—on the user's explicit
IANA-local day. Missing, stale, future, malformed, duplicate, or oversized
evidence remains unavailable rather than being displayed as zero. Its payload
leads with truthful now-playing state, then today's completed movement minutes,
and includes an exact text-only summary.

Motion intentionally publishes no live-moment specs while V3 lacks an audited
runtime class-schedule reader; seed and GA inventory cannot cross that boundary.
Its Mat Mode resolver likewise accepts only an explicit canonical V3 capability
envelope and passes the validated contextual link through unchanged. A missing,
throwing, malformed, generic, product-root, or non-V3 launch target produces no
link, so the package cannot fabricate a manifest-level fallback.