FA-52914 / Raster memory layout / Member archive

Capture Ring Frame Slots: Ring write origin omits slot framing or fence pitch · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at write_header.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

A capture ring holds four frame slots, each with an eight-byte generation header and image payload followed by a three-byte fence word. Frame generation maps monotonically to slot modulo capacity; byte addresses use slot, freshness uses full generation. Return the named intermediate layout descriptor and final address fields; all quantities are integer byte offsets unless explicitly stated.

Why this case matters

Offline raster resource, upload, readback, and storage-layout regression model.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
layout fixture 2	`{"allocation_end": 1348, "fence_address": 682, "fresh": true, "payload_bytes": 315, "read_address": 147, "read_header": 44, "read_slot": 0, "slot_pitch": 326, "write_header": 359, "write_slot": 1}`	`{"allocation_end": 1348, "fence_address": 693, "fresh": true, "payload_bytes": 315, "read_address": 147, "read_header": 44, "read_slot": 0, "slot_pitch": 326, "write_header": 370, "write_slot": 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.