FAILURE MAP

Understand the failure.
Verify the repair.

Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.

Explore the cases ↓How results are verified ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

WHAT THE ARCHIVE CONTAINS

100840 executable cases. 20168 are open.

Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.

The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗

A RECORD OF WHAT WENT WRONG

Browse the archive / 100840

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-32201

Keyboard matrix rectangle ghost quarantine: Ghost detection treats one row as a rectangle or skips the last matrix row · case 01

The event trace violates the distinct rows rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32202

Keyboard matrix rectangle ghost quarantine: Ghost detection treats one row as a rectangle or skips the last matrix row · case 02

The event trace violates the distinct rows rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32203

Keyboard matrix rectangle ghost quarantine: Ghost detection treats one row as a rectangle or skips the last matrix row · case 03

The event trace violates the distinct rows rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32204

Keyboard matrix rectangle ghost quarantine: Ghost detection treats one row as a rectangle or skips the last matrix row · case 04

The event trace violates the distinct rows rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32205

Keyboard matrix rectangle ghost quarantine: Ghost detection treats one row as a rectangle or skips the last matrix row · case 05

The event trace violates the distinct rows rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32206

Keyboard matrix rectangle ghost quarantine: Ghost detection treats one column as a rectangle or skips the last matrix column · case 01

The event trace violates the distinct columns rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32207

Keyboard matrix rectangle ghost quarantine: Ghost detection treats one column as a rectangle or skips the last matrix column · case 02

The event trace violates the distinct columns rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32208

Keyboard matrix rectangle ghost quarantine: Ghost detection treats one column as a rectangle or skips the last matrix column · case 03

The event trace violates the distinct columns rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32209

Keyboard matrix rectangle ghost quarantine: Ghost detection treats one column as a rectangle or skips the last matrix column · case 04

The event trace violates the distinct columns rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32210

Keyboard matrix rectangle ghost quarantine: Ghost detection treats one column as a rectangle or skips the last matrix column · case 05

The event trace violates the distinct columns rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32211

Keyboard matrix rectangle ghost quarantine: Ghost quarantine accepts a three-corner pattern or ignores rectangles embedded in a larger report · case 01

The event trace violates the rectangle completeness rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32212

Keyboard matrix rectangle ghost quarantine: Ghost quarantine accepts a three-corner pattern or ignores rectangles embedded in a larger report · case 02

The event trace violates the rectangle completeness rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32213

Keyboard matrix rectangle ghost quarantine: Ghost quarantine accepts a three-corner pattern or ignores rectangles embedded in a larger report · case 03

The event trace violates the rectangle completeness rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32214

Keyboard matrix rectangle ghost quarantine: Ghost quarantine accepts a three-corner pattern or ignores rectangles embedded in a larger report · case 04

The event trace violates the rectangle completeness rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32215

Keyboard matrix rectangle ghost quarantine: Ghost quarantine accepts a three-corner pattern or ignores rectangles embedded in a larger report · case 05

The event trace violates the rectangle completeness rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32216

Keyboard matrix rectangle ghost quarantine: Multiple ambiguous rectangles do not accumulate their quarantined corners · case 01

The event trace violates the rectangle union rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32217

Keyboard matrix rectangle ghost quarantine: Multiple ambiguous rectangles do not accumulate their quarantined corners · case 02

The event trace violates the rectangle union rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32218

Keyboard matrix rectangle ghost quarantine: Multiple ambiguous rectangles do not accumulate their quarantined corners · case 03

The event trace violates the rectangle union rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32219

Keyboard matrix rectangle ghost quarantine: Multiple ambiguous rectangles do not accumulate their quarantined corners · case 04

The event trace violates the rectangle union rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32220

Keyboard matrix rectangle ghost quarantine: Multiple ambiguous rectangles do not accumulate their quarantined corners · case 05

The event trace violates the rectangle union rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32221

Keyboard matrix rectangle ghost quarantine: Ambiguity drops already-held keys or preserves keys absent from the latest scan · case 01

The event trace violates the preserve held rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32222

Keyboard matrix rectangle ghost quarantine: Ambiguity drops already-held keys or preserves keys absent from the latest scan · case 02

The event trace violates the preserve held rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32223

Keyboard matrix rectangle ghost quarantine: Ambiguity drops already-held keys or preserves keys absent from the latest scan · case 03

The event trace violates the preserve held rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32224

Keyboard matrix rectangle ghost quarantine: Ambiguity drops already-held keys or preserves keys absent from the latest scan · case 04

The event trace violates the preserve held rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32225

Keyboard matrix rectangle ghost quarantine: Ambiguity drops already-held keys or preserves keys absent from the latest scan · case 05

The event trace violates the preserve held rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32226

Keyboard matrix rectangle ghost quarantine: Matrix keyboard releases include new or unchanged accepted cells · case 01

The event trace violates the release delta rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32227

Keyboard matrix rectangle ghost quarantine: Matrix keyboard releases include new or unchanged accepted cells · case 02

The event trace violates the release delta rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32228

Keyboard matrix rectangle ghost quarantine: Matrix keyboard releases include new or unchanged accepted cells · case 03

The event trace violates the release delta rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32229

Keyboard matrix rectangle ghost quarantine: Matrix keyboard releases include new or unchanged accepted cells · case 04

The event trace violates the release delta rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32230

Keyboard matrix rectangle ghost quarantine: Matrix keyboard releases include new or unchanged accepted cells · case 05

The event trace violates the release delta rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32231

Keyboard matrix rectangle ghost quarantine: Matrix keyboard presses include released or unchanged accepted cells · case 01

The event trace violates the press delta rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32232

Keyboard matrix rectangle ghost quarantine: Matrix keyboard presses include released or unchanged accepted cells · case 02

The event trace violates the press delta rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32233

Keyboard matrix rectangle ghost quarantine: Matrix keyboard presses include released or unchanged accepted cells · case 03

The event trace violates the press delta rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32234

Keyboard matrix rectangle ghost quarantine: Matrix keyboard presses include released or unchanged accepted cells · case 04

The event trace violates the press delta rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32235

Keyboard matrix rectangle ghost quarantine: Matrix keyboard presses include released or unchanged accepted cells · case 05

The event trace violates the press delta rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32236

Keyboard matrix rectangle ghost quarantine: Quarantined observations become prior accepted keys or released keys remain in state · case 01

The event trace violates the accepted snapshot rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32237

Keyboard matrix rectangle ghost quarantine: Quarantined observations become prior accepted keys or released keys remain in state · case 02

The event trace violates the accepted snapshot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32238

Keyboard matrix rectangle ghost quarantine: Quarantined observations become prior accepted keys or released keys remain in state · case 03

The event trace violates the accepted snapshot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32239

Keyboard matrix rectangle ghost quarantine: Quarantined observations become prior accepted keys or released keys remain in state · case 04

The event trace violates the accepted snapshot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32240

Keyboard matrix rectangle ghost quarantine: Quarantined observations become prior accepted keys or released keys remain in state · case 05

The event trace violates the accepted snapshot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32241

Deferred short shortcut versus longer key sequence: Cancelling shortcut recognition retains delayed command or prefix input · case 01

The event trace violates the cancel discard rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32242

Deferred short shortcut versus longer key sequence: Cancelling shortcut recognition retains delayed command or prefix input · case 02

The event trace violates the cancel discard rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32243

Deferred short shortcut versus longer key sequence: Cancelling shortcut recognition retains delayed command or prefix input · case 03

The event trace violates the cancel discard rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32244

Deferred short shortcut versus longer key sequence: Cancelling shortcut recognition retains delayed command or prefix input · case 04

The event trace violates the cancel discard rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32245

Deferred short shortcut versus longer key sequence: Cancelling shortcut recognition retains delayed command or prefix input · case 05

The event trace violates the cancel discard rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32246

Deferred short shortcut versus longer key sequence: Delayed shortcut expiry uses an exclusive boundary or an absolute timeout · case 01

The event trace violates the inclusive timeout rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32247

Deferred short shortcut versus longer key sequence: Delayed shortcut expiry uses an exclusive boundary or an absolute timeout · case 02

The event trace violates the inclusive timeout rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32248

Deferred short shortcut versus longer key sequence: Delayed shortcut expiry uses an exclusive boundary or an absolute timeout · case 03

The event trace violates the inclusive timeout rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32249

Deferred short shortcut versus longer key sequence: Delayed shortcut expiry uses an exclusive boundary or an absolute timeout · case 04

The event trace violates the inclusive timeout rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32250

Deferred short shortcut versus longer key sequence: Delayed shortcut expiry uses an exclusive boundary or an absolute timeout · case 05

The event trace violates the inclusive timeout rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32251

Deferred short shortcut versus longer key sequence: A delayed shortcut is reported at polling time or a second timeout · case 01

The event trace violates the timeout timestamp rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32252

Deferred short shortcut versus longer key sequence: A delayed shortcut is reported at polling time or a second timeout · case 02

The event trace violates the timeout timestamp rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32253

Deferred short shortcut versus longer key sequence: A delayed shortcut is reported at polling time or a second timeout · case 03

The event trace violates the timeout timestamp rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32254

Deferred short shortcut versus longer key sequence: A delayed shortcut is reported at polling time or a second timeout · case 04

The event trace violates the timeout timestamp rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32255

Deferred short shortcut versus longer key sequence: A delayed shortcut is reported at polling time or a second timeout · case 05

The event trace violates the timeout timestamp rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32256

Deferred short shortcut versus longer key sequence: Timer or release events are fed into the shortcut key sequence · case 01

The event trace violates the phase filter rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32257

Deferred short shortcut versus longer key sequence: Timer or release events are fed into the shortcut key sequence · case 02

The event trace violates the phase filter rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32258

Deferred short shortcut versus longer key sequence: Timer or release events are fed into the shortcut key sequence · case 03

The event trace violates the phase filter rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32259

Deferred short shortcut versus longer key sequence: Timer or release events are fed into the shortcut key sequence · case 04

The event trace violates the phase filter rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32260

Deferred short shortcut versus longer key sequence: Timer or release events are fed into the shortcut key sequence · case 05

The event trace violates the phase filter rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32261

Deferred short shortcut versus longer key sequence: Continuation key is prepended to or replaces the buffered shortcut prefix · case 01

The event trace violates the prefix extension rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32262

Deferred short shortcut versus longer key sequence: Continuation key is prepended to or replaces the buffered shortcut prefix · case 02

The event trace violates the prefix extension rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32263

Deferred short shortcut versus longer key sequence: Continuation key is prepended to or replaces the buffered shortcut prefix · case 03

The event trace violates the prefix extension rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32264

Deferred short shortcut versus longer key sequence: Continuation key is prepended to or replaces the buffered shortcut prefix · case 04

The event trace violates the prefix extension rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32265

Deferred short shortcut versus longer key sequence: Continuation key is prepended to or replaces the buffered shortcut prefix · case 05

The event trace violates the prefix extension rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32266

Deferred short shortcut versus longer key sequence: Shortcut candidates use suffix matching or require a completed binding too early · case 01

The event trace violates the prefix candidate rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32267

Deferred short shortcut versus longer key sequence: Shortcut candidates use suffix matching or require a completed binding too early · case 02

The event trace violates the prefix candidate rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32268

Deferred short shortcut versus longer key sequence: Shortcut candidates use suffix matching or require a completed binding too early · case 03

The event trace violates the prefix candidate rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32269

Deferred short shortcut versus longer key sequence: Shortcut candidates use suffix matching or require a completed binding too early · case 04

The event trace violates the prefix candidate rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32270

Deferred short shortcut versus longer key sequence: Shortcut candidates use suffix matching or require a completed binding too early · case 05

The event trace violates the prefix candidate rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32271

Deferred short shortcut versus longer key sequence: Mismatch dispatch reports the old timeout or emits current key identity instead of delayed command · case 01

The event trace violates the mismatch pending rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32272

Deferred short shortcut versus longer key sequence: Mismatch dispatch reports the old timeout or emits current key identity instead of delayed command · case 02

The event trace violates the mismatch pending rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32273

Deferred short shortcut versus longer key sequence: Mismatch dispatch reports the old timeout or emits current key identity instead of delayed command · case 03

The event trace violates the mismatch pending rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32274

Deferred short shortcut versus longer key sequence: Mismatch dispatch reports the old timeout or emits current key identity instead of delayed command · case 04

The event trace violates the mismatch pending rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32275

Deferred short shortcut versus longer key sequence: Mismatch dispatch reports the old timeout or emits current key identity instead of delayed command · case 05

The event trace violates the mismatch pending rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32276

Deferred short shortcut versus longer key sequence: Mismatch retry loses the current key or retries the already failed prefix · case 01

The event trace violates the retry current rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32277

Deferred short shortcut versus longer key sequence: Mismatch retry loses the current key or retries the already failed prefix · case 02

The event trace violates the retry current rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32278

Deferred short shortcut versus longer key sequence: Mismatch retry loses the current key or retries the already failed prefix · case 03

The event trace violates the retry current rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32279

Deferred short shortcut versus longer key sequence: Mismatch retry loses the current key or retries the already failed prefix · case 04

The event trace violates the retry current rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32280

Deferred short shortcut versus longer key sequence: Mismatch retry loses the current key or retries the already failed prefix · case 05

The event trace violates the retry current rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32281

Deferred short shortcut versus longer key sequence: Ambiguity detection counts exact match as longer or ignores a one-key extension · case 01

The event trace violates the longer candidate rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32282

Deferred short shortcut versus longer key sequence: Ambiguity detection counts exact match as longer or ignores a one-key extension · case 02

The event trace violates the longer candidate rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32283

Deferred short shortcut versus longer key sequence: Ambiguity detection counts exact match as longer or ignores a one-key extension · case 03

The event trace violates the longer candidate rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32284

Deferred short shortcut versus longer key sequence: Ambiguity detection counts exact match as longer or ignores a one-key extension · case 04

The event trace violates the longer candidate rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32285

Deferred short shortcut versus longer key sequence: Ambiguity detection counts exact match as longer or ignores a one-key extension · case 05

The event trace violates the longer candidate rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32286

Deferred short shortcut versus longer key sequence: Partial shortcut deadline uses the epoch or survives after no candidates remain · case 01

The event trace violates the pending deadline rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32287

Deferred short shortcut versus longer key sequence: Partial shortcut deadline uses the epoch or survives after no candidates remain · case 02

The event trace violates the pending deadline rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32288

Deferred short shortcut versus longer key sequence: Partial shortcut deadline uses the epoch or survives after no candidates remain · case 03

The event trace violates the pending deadline rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32289

Deferred short shortcut versus longer key sequence: Partial shortcut deadline uses the epoch or survives after no candidates remain · case 04

The event trace violates the pending deadline rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32290

Deferred short shortcut versus longer key sequence: Partial shortcut deadline uses the epoch or survives after no candidates remain · case 05

The event trace violates the pending deadline rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32291

Bounded keyboard queue with lossless release backpressure: Keyboard pump admits over-capacity presses or wastes its final available slot · case 01

The event trace violates the capacity boundary rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32292

Bounded keyboard queue with lossless release backpressure: Keyboard pump admits over-capacity presses or wastes its final available slot · case 02

The event trace violates the capacity boundary rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32293

Bounded keyboard queue with lossless release backpressure: Keyboard pump admits over-capacity presses or wastes its final available slot · case 03

The event trace violates the capacity boundary rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32294

Bounded keyboard queue with lossless release backpressure: Keyboard pump admits over-capacity presses or wastes its final available slot · case 04

The event trace violates the capacity boundary rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32295

Bounded keyboard queue with lossless release backpressure: Keyboard pump admits over-capacity presses or wastes its final available slot · case 05

The event trace violates the capacity boundary rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32296

Bounded keyboard queue with lossless release backpressure: An enqueued keyboard press is not retained in the release-admission set · case 01

The event trace violates the admitted down rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-32297

Bounded keyboard queue with lossless release backpressure: An enqueued keyboard press is not retained in the release-admission set · case 02

The event trace violates the admitted down rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32298

Bounded keyboard queue with lossless release backpressure: An enqueued keyboard press is not retained in the release-admission set · case 03

The event trace violates the admitted down rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32299

Bounded keyboard queue with lossless release backpressure: An enqueued keyboard press is not retained in the release-admission set · case 04

The event trace violates the admitted down rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32300

Bounded keyboard queue with lossless release backpressure: An enqueued keyboard press is not retained in the release-admission set · case 05

The event trace violates the admitted down rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗

INSPECTABLE BY DESIGN

Every result has a runnable source.

Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.

Read the methodology ↗