Memory and recovery

Retain the source. Record the change. Continue the history.

Memory gives a continuing system a history it can use and revise. AOTX keeps the original source, its interpretation and the context chosen for a reply as distinct records. Their relationships provide a way to trace what was retained, whose information it is and how the current account came to be.

PRIMARY RESIDENCY: Device memory
RECALL: Scoped selection
RECOVERY: Recorded state

Sources and interpretations

A source is the retained account of an input and its provenance. An assertion is an interpretation linked to that source. This distinction keeps the evidence available when an interpretation changes: the system can revise what it currently uses without losing the input from which that conclusion was drawn.

Ownership and attribution are recorded separately. The authenticated participant who submitted a message, the owner of a memory object and a person mentioned in its text can be three different identities. A quotation retains its recorded speaker; a name within the quotation remains part of the content.

From source to assertion

Where automatic interpretation is enabled, two bounded stages use the same resident language role. The first classifies complete supplied source spans, separating declarative statements from questions, commands and requests. The second interprets the accepted statements with an explicit catalogue of eligible earlier assertions that they may correct.

Validation checks coverage, exact source references and the permitted result structure before the result can enter memory. Behavioural qualification establishes whether the selected model configuration performs that interpretation reliably. The development programme describes the present qualification and the work extending it.

Scoped recall and correction

Recall begins with access. The GPU constructs eligible context from ownership, membership, visibility and the current recorded revision. It then selects within a finite reference and byte budget. Required context and active focus retain their priority; discretionary selection gives independent sources an opportunity before adding further representations of a source already represented.

This matters when one input has produced several useful fragments. Those fragments should not crowd every independent source out of the available context simply because they are numerous. Selection preserves the source relationship while deciding which representations fit the current query.

Corrections have a similarly explicit boundary. An interpretation receives a catalogue of eligible prior assertions and can supersede only targets in that catalogue. The resulting revision preserves its relationship to earlier evidence. Negation, uncertainty and unrelated statements receive their own treatment instead of becoming an unrestricted replacement of similarly worded material.

Context and attribution

Historical material carries its recorded actor separately from the authenticated sender of the current input. A recalled instruction is historical data. A generated reply is output from the system; any subsequent retention follows the applicable source and policy rules.

Residency and capacity

In the primary mode, the admitted active memory set and selection state reside on the GPU. Disk persistence runs alongside this as the recoverable replica. The active device position and the saved disk position are tracked independently, allowing the runtime to report both current work and recoverable progress.

Optional cold-memory offload provides a second residency arrangement. Eligible committed payloads move to storage while the GPU retains the authoritative catalogue, versions, permissions and selection decisions. When the runtime requests an extent, the disk feeder returns its bytes. Retrieval ranking and recall decisions remain device work.

Residency is an explicit operating choice. Returning the set to GPU-only operation first checks that it fits, and reclamation respects protected state and active references. An unavailable offloaded payload is reported as unavailable so that a consumer can distinguish missing material from an empty result.

Active memory, retained recovery history and total file capacity have separate budgets. Reclaiming an active object does not automatically retire every historical record associated with it.

Recovery without reinterpretation

Recovery reconstructs logical state from committed authoritative records. It validates recorded choices and result bytes against their saved identities, then restores the state those records establish. An earlier interpretation therefore remains the recorded decision, rather than being submitted to a model again during restart.

The journal supplies complete committed work. A CCIR generation binds the corresponding checkpoint, replay representation and required assets into a coherent saved unit. Recovery uses that acknowledged boundary; an unfinished tail remains outside it.

Operation receipts carry this distinction into shared service. If an operation has a saved terminal result, the service can return that outcome on reconnection. If admission survived but its terminal result did not, the operation is reported as interrupted. A new explicit operation can continue the work without silently duplicating earlier inputs, memory changes or external effects.

These same rules support transfer to a compatible machine. The container carries a saved history and the assets needed to reconstruct it; the destination supplies a fresh execution environment. The portability chapter follows that process from saved generation to renewed operation.