FA-30958 / Keyboard interactions / Member archive

Simultaneous chord edge recognizer: An empty configured chord is treated as complete · case 03

The event trace violates the empty chord rule and produces incorrect keyboard state or command output.

Member previewVariant 3 · 3 implementations · 9 checks per implementation

Case contract

Case is [required_keys, events]. Down/up update held keys; cancel clears state. A chord fires on the first transition from incomplete to all required keys held, with no extra keys. It rearms after becoming incomplete. Empty chord never fires. Return fire count, sorted held, armed state, last triggering key and current completeness. Inputs are finite ordered event traces; return the stated deterministic state. Batch entries are independent. N varies the number of independent input transactions.

Why this case matters

Controlled keyboard event processing model for debugging application event logic.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
simultaneous-chord scenario 1	`[[0, [], true, null, true], [0, [], true, null, true], [0, [], true, null, true]]`	`[[0, [], true, null, false], [0, [], true, null, false], [0, [], true, null, false]]`	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.