Intra-transaction coordinate: a transaction and an index within it
(events today; any per-transaction-indexed lane). Boundary cursors may
point at slots with no item.
A request’s checkpoint window resolved into the checkpoint-sequence interval to scan. Cursors
do not narrow it: ResolvedScan::resolve applies them by scan position. Unlike
ResolvedScan<u64>/ResolvedScan<IntraTxCoordinate>, the scan domain here is
checkpoint space, so the entry and terminal checkpoints derive from range directly and need
no extra fields.
A request’s checkpoint window in a lane’s scan-position space, narrowed to the request’s start
and end positions inside the window’s edge checkpoints (see
CheckpointPositions).
The error for a request that needs versions of an object (a package, for one) below
oldest_retained_version, the oldest one this server keeps: the object’s version at the end of
floor_checkpoint, the lowest checkpoint whose object state it keeps. Older versions are
pruned and permanently gone. It is below_serving_floor for floor_checkpoint, with the
version as lowestAvailableVersion too, so a client can list from it instead.
The error for a request that needs data below this server’s serving floor, whose lowest
available checkpoint is floor_checkpoint: that data is pruned and permanently gone.
It is OutOfRange with a BELOW_EARLIEST_AVAILABLEErrorInfo whose
lowestAvailableCheckpoint is floor_checkpoint; retrying it on this server fails the same
way.
The requested checkpoint window’s validity check, standalone so backends
can sequence it independently of options parsing (kv validates bounds
before the read mask and options; the fused resolution re-runs it
harmlessly).