nemo_gym.token_id_capture.lineage
nemo_gym.token_id_capture.lineage
Resolve the recorded call that a request continues.
A rollout can contain several model calls. Training consumes their exact tokens as one contiguous sequence. Request-time lineage identifies the earlier call that each request continues.
assistant_fingerprint is the lookup key.
It hashes model-authored turns and ignores user and tool content added between calls.
conversation_digest verifies the unchanged request context.
A digest mismatch rejects the claimed lineage before any parent tokens are reused.
The shared LineageResolver resolves entries already committed by TokenSink.
FileLineageStore tails the token JSONL through the token store’s lock.
Each child receives its parent’s cumulative tokens.
Downstream inference consumes those tokens to supply the exact prompt prefix.
Every supported record distinguishes a root, a resolved parent, and an unresolved boundary. The builder uses token-prefix matching only when a verified parent is absent from the frozen snapshot. It never uses prefix matching to cross an unresolved boundary.
A delivered chain contains exactly the tokens the policy emitted over the recorded context. The hashes ignore reasoning and selected items that a harness may omit when it echoes model output. These differences do not change the captured token sequence. Ambiguous matches remain unresolved rather than risking tokens from the wrong call.
Module Contents
Classes
Functions
Data
API
Bases: IncrementalLineageStore
Resolve lineage from the token JSONL committed by TokenCaptureStore.
The reference IncrementalLineageStore backend: cursor = (inode, offset),
ref = byte offset, reads under the store’s shared flock so a committed
put is immediately visible.
Delete, as delete does, the rollouts that no server has marked started.
The check and the removal hold the rollout’s lock, so a concurrent mark_started either comes first,
and the ledger stays, or comes after the ledger is gone.
Return every ledger row of rollout_id in commit order, for a checkpoint.
Install checkpointed rows as the complete ledger of rollout_id; see import_rows_many.
Install several rollouts’ ledgers from a checkpoint, then sync the directory once.
Restore runs on a freshly started model server, so capture files already present for a target attempt, or for a later attempt of the same rollout, belong to executions that died after an earlier restore of the checkpoint. They are deleted first, retire fences included: a stale ledger would mix a dead execution’s calls into the replacement’s lineage, and a fence would silently discard the replacement’s rows once the episode reached that attempt again.
The ledgers are not synced one by one: the checkpoint they come from is the durable copy, and a crash during or after the import only means importing again. A later append to a ledger syncs its file.
Record, for every server sharing this ledger, that a restored attempt has started.
A policy server marks a restored attempt before the attempt’s first call there can write a row or be held,
so delete_unstarted on another server leaves the attempt’s ledger alone.
A retired attempt is not marked: its calls are refused, and the marker would outlive its ledger.
Reference resolver for in-process framework backends and tests.
Production wiring uses FileLineageStore when a token store exists.
Its index is memory-only.
Eviction or restart leaves affected continuations unresolved.
That failure mode is safe but can mask otherwise usable rollouts.
Multi-worker deployments require a shared LineageResolver.
The resolution index evicts rollouts under memory bounds, so this store
cannot serve as an external-staging capture ledger (completeness would
break); it remains for unit tests and single-worker development. Its
ledger rows are kept in a separate unbounded map so ledger unit tests see
file-store semantics.
Delete the rollouts no mark_started names; see FileLineageStore.delete_unstarted.
Record that a restored attempt has started; see FileLineageStore.mark_started.
Publish one committed entry to the worker-local index.
Base class for lineage resolvers over any committed-entry backend.
An external backend implements two hooks. It inherits Gym’s matcher, bounded index, locking, and token materialization. Hash-for-hash agreement is the wire contract. The backend remains the source of truth when cache rows are evicted. A resolved match loads only the winning call’s token chain.
Required hooks:
_fetch_new_entries(rollout_id, cursor) -> (items, new_cursor) where
items is [(TokenEntry, ref), ...] in commit order since cursor
(None means from the beginning) and ref is any handle that
_load_entry can use later (byte offset, KV key, …). Raise
CursorReset when the cursor no longer describes the backend (file
rotated, namespace recreated); the base refetches from the beginning.
_load_entry(rollout_id, ref) -> TokenEntry for one committed record.
Optional hooks:
_load_entries(rollout_id, refs) — batch-load one parent chain
(default: call _load_entry for each reference).
_read_locked(rollout_id) — context manager held around fetch+resolve
for backends with a read-lock discipline (default: no lock).
is_process_shared() — default True; an external backend exists to
be shared, and the multi-worker startup check trusts this answer.
Insert or touch a cache row with LRU semantics.
Reinsert a touched row so dictionary order tracks recency. Eviction only requires a later backend refetch.
Load several committed entries.
Backends can override this hook to fetch a parent chain in one operation.
Load one RESOLVED parent’s cumulative tokens from the backend.
Read the chain in one batch and append each token segment once. Digest verification makes stale references fail closed.
Bound worker-local lineage by rollout and cumulative token counts.
This index backs the single-worker fallback. Shared stores provide cross-worker visibility. Eviction removes the oldest rollout. An evicted parent leaves later continuations unresolved and the builder masks them. The only live rollout is never evicted.
Release a rollout’s lineage early.
Gym’s model server has no rollout-completion signal. An in-process framework can call this when it retires the records.
Keep an append-only per-rollout call index.
Return whether this request extends the node’s recorded context.
The leading context_len items must match the recorded request.
A rewritten or summarized context fails verification.
Verification excludes the model response because dialects can echo it as different item counts.
Index lookup metadata carried by one committed token entry.
store_tokens=False keeps token arrays in the durable log.
Index a completed call by its continuation fingerprint.
context_len counts the request items before the model response.
The default assumes one synthesized response item.
cum_len must be passed explicitly for token-free custody rows,
where cum_tokens is empty; a child’s prev_len reads it.
Return the immutable parent decision for this request.
A request without model-authored history is a root. A request with unverified history is unresolved. Never guess among calls with identical output.
Return the parent decision without touching token arrays.
Matching needs only fingerprints, digests, and lengths. The caller materializes tokens for the single winner.
The episode attempts with capture files among names, grouped by rollout.
Return the ledger custody columns for one committed CallRecord.
_manifest_from_rows rebuilds the CallRecord from these columns, so
the mapping must stay a lossless round trip.
Capture keys with files of the same rollout as capture_key and a later attempt.
Build the token-free RolloutManifest payload from ledger rows.
Committed custody rows become CallRecord payloads; failure rows become
failures entries. Lineage-only rows (local capture) carry no custody
columns and are not part of a capture manifest.
Add compact lookup metadata before the token entry is committed.