FAILURE MAP
← Case archive

FA-33072 / Menu interactions / Member archive

Menu undo receipt captures another action on the same document · case 02

Menu undo receipt captures another action on the same document.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

Menu command receipts retain committed effects, invocation identity and reversible scope; receipt generation does not imply successful mutation.

Why this case matters

Cascading and context menus require coherent command and session state as content changes.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
scope contract[{"document": "d", "transaction": 2}, {"document": "d", "transaction": 3}][{"document": "d", "transaction": 2}]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.

Sign in to the archive ↗