FA-40315 / Heap invariants / Member archive

Heap resolution combines owner and generation checks to prevent ABA aliasing · case 05

The bounded handle generation certificate reports an incorrect resolved.

Member previewVariant 5 · 3 implementations · 7 checks per implementation

Case contract

A heap handle is [slot,generation,owner]. A slot table stores [live,generation,payload]. A handle resolves only for matching owner, in-range slot, live slot, and exact generation. Inspect each supplied handle; return per-handle ownership, bounds, liveness, generation match, resolution, and next generation after recycling each slot. Missing resolution is None.

Why this case matters

This isolates an internal heap representation or priority-structure invariant using deterministic finite records.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
regression certificate 4	`{"bounds": [true, true, true], "generation": [false, true, true], "live": [true, true, true], "owners": [true, true, false], "recycle": [5, 9], "resolved": ["a", "b", null]}`	`{"bounds": [true, true, true], "generation": [false, true, true], "live": [true, true, true], "owners": [true, true, false], "recycle": [5, 9], "resolved": [null, "b", 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.