FA-44713 / Data systems / Member archive

A key-changing retraction is sent to the new key · case 03

A key-changing retraction is sent to the new key.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Maintain an identity-indexed keyed table while applying [id,newkey,newvalue] upserts. A moved identity retracts its old key/value before adding the new row. Identical upserts emit no change. State and emitted changelog preserve identity distinctions.

Why this case matters

A bounded deterministic data engine model makes representation and changelog faults reproducible.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
move key	`[[[10, 2, 4]], [[10, 2, 3, -1], [10, 2, 4, 1]]]`	`[[[10, 2, 4]], [[10, 1, 3, -1], [10, 2, 4, 1]]]`	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.