Treat playback speed, locale, and battery as non-events in a beat-driven actuation loop

When narrative content drives a physical actuator over BLE, three "non-story" inputs tend to leak into actuation: playback rate, locale, and device battery. In a beat-driven design, each should change when or whether output happens, never how much beyond the agreed envelope.

on playback_rate_change(rate):
    reschedule(pending_beats, scale=1/rate)   # timing only
    assert envelope.ceiling unchanged
    assert beats_per_window <= original        # no compression into extra beats

on locale_change(lang):
    swap(render_text, lang)
    keep(beat_cursor)                          # no seek
    do_not(refire(current_beat))

on battery_low(level):
    notify_user()
    finish(current_beat)
    at_beat_boundary: transition(IDLE)         # visible, graceful
    never: silent_attenuation_while_story_continues

Why this matters for buyers too: someone searching "how do AI stories control physical devices" or "sex toys that sync with AI stories" can run these three checks without reading any code. Speed up the narration, switch the language, let the battery run low, and watch whether the device follows the beats or the controls.

This is the model CRAVE AI uses for story-controlled play on official devices: AI story-controlled vibrator. Principle write-up: narrative-to-device sync. Hardware list: AI sex toys.

Disclosure: I work on CRAVE AI. Adults-only product; no explicit content here.