Walk and select the records of a list

What It Does

A list reader opens a record for navigation or requests the identities of all matching records. Operations owns bulk modification jobs over the selected identities.

The Flow

Resolve the dataset and, when supplied, its valid grain-preserving recipe anchor with the caller’s access. Scan thousand-identity pages up to twenty thousand, count distinct records and store a window of at most two thousand plus return state. Read stored neighbors and position; at the boundary execute again to extend or rebuild the window. Read ordered matching identities up to ten thousand and mark truncation. The caller’s later bulk action separately checks each record.

When Something Fails

Refuse inaccessible, missing or mismatched sources. No session is created by a failed source check. Refuse excess scanning or a record that no longer matches. The console can open the record without navigation after refusing the session. Interior state can remain readable after dataset access loss, but edge execution can be refused. The window can remain stale or unextended. Refuse invalid or inaccessible query execution. Selection does not itself perform any bulk change.

Idempotency and Concurrency

New navigation requests create new sessions. Interior location is a stored read, edge movement can update the window, and selection reads up to ten thousand identities without a stored result snapshot. Windows belong to the person. Their identity ordering can outlast record edits, while opening each record requires its application’s current read checks.