FA-21233 / Assistive announcements / Member archive

Escalation speaks deadline as message content · case 03

The announcement trace violates the stated escalation-ladder contract.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

Unacknowledged notices have [text,level,next-due]. Open replaces notice at level0 due after2 ticks. Tick uses monotonic clock and emits at most one escalation per notice when due; levels1 and2 schedule another2 ticks, level3 is final and has no future due. Ack removes notice. Snooze adds delay to existing deadline, not now. Edit text preserves escalation level. Reset-level sets level0 and next due now+2. Report [id,text,level] speech and pending state.

Why this case matters

Deterministic controlled model of assistive announcement delivery.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
trace-1	`[[["a", "2", 1], ["a", "4", 2], ["a", "6", 3]], 8, [["a", "alarmalarmalarm", 3, null]]]`	`[[["a", "alarmalarmalarm", 1], ["a", "alarmalarmalarm", 2], ["a", "alarmalarmalarm", 3]], 8, [["a", "alarmalarmalarm", 3, null]]]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.