Some checks failed
CI / fmt (push) Has been cancelled
CI / clippy (push) Has been cancelled
CI / test (1.85) (push) Has been cancelled
CI / test (stable) (push) Has been cancelled
CI / deny (push) Has been cancelled
CI / sim-bench (stable) (push) Has been cancelled
CI / twilio-live (manual only) (push) Has been cancelled
Co-authored-by: Aaron D. Lee <himself@adlee.work> Co-committed-by: Aaron D. Lee <himself@adlee.work>
50 lines
1.2 KiB
TOML
50 lines
1.2 KiB
TOML
# Scenario: sustained-call (slice-4½ spec §5.3 entry #3)
|
||
#
|
||
# Drives the multi-barge / fatigue / sustained-load check. Three loud
|
||
# bursts + two quiet interludes + end:
|
||
# - loud cycle 1 → barge fires → local VAD re-arms on quiet
|
||
# - quiet cycle 1 → no barge, VAD re-armed for next loud
|
||
# - loud cycle 2 → second barge fires
|
||
# - quiet cycle 2 → re-arm
|
||
# - loud cycle 3 → third barge fires
|
||
#
|
||
# Threshold assertion (S7): the per-barge kill_times should drift
|
||
# ≤ 1.5× across the three bar cycles (anti-fatigue). The second + third
|
||
# bar's kill time should not be significantly longer than the first's
|
||
# (no resource exhaustion, no GC pressure, no growing lock contention
|
||
# across the slice's lifetime).
|
||
#
|
||
# See slice-4 §6.1 for the barge_epoch disambiguation mechanism that
|
||
# makes "fresh re-barge" vs "late confirmation of the bar already in
|
||
# flight" distinguishable — the Reflex::barge_epoch increments on each
|
||
# SpeechStarted.
|
||
|
||
name = "sustained-call"
|
||
|
||
[[steps]]
|
||
kind = "speak_loud"
|
||
frames = 10
|
||
|
||
[[steps]]
|
||
kind = "speak_quiet"
|
||
frames = 10
|
||
|
||
[[steps]]
|
||
kind = "speak_loud"
|
||
frames = 10
|
||
|
||
[[steps]]
|
||
kind = "speak_quiet"
|
||
frames = 10
|
||
|
||
[[steps]]
|
||
kind = "speak_loud"
|
||
frames = 10
|
||
|
||
[[steps]]
|
||
kind = "await_reply"
|
||
frames = 0
|
||
|
||
[[steps]]
|
||
kind = "end"
|