03 / Cognitive identity runtime

AOTX-1 / CONTINUITY & PORTABILITY

CCIR

Containerised Cognitive
Identity Runtime

A runtime that carries
its continuity.

Models, identity, memory and the recorded state that connects them, carried together in one complete file.

Explore the container

COMPLETE RUNTIME CONTAINER.aotxccirASSETS / STATE / RECOVERY

01 / CONTAINER ANATOMYILLUSTRATED STRUCTURE

One file. Connected parts.

A runtime is a set of connected dependencies. CCIR keeps those dependencies with the saved state that uses them, under a declared profile.

01 / MODELS & PROCESSING

Execution begins with the complete model.

Weights travel with their tokenizer, message-processing assets and the other dependencies selected by the profile. A media-capable runtime also carries the trained encoders, projectors or specialist models its inputs require.

Activation reads these packaged assets, so the continuing runtime can be reconstructed with the original model directories unavailable and without downloading the same dependencies again.

WEIGHTS + PROCESSING

02 / IDENTITY & SETTINGS

The runtime carries its authored identity.

Authored identity and selected settings belong alongside the model and memory they configure. The container preserves these assets, while later generations record the state accumulated during operation.

Keeping identity, configuration and history together gives a restored runtime a defined starting point. Model-specific assets remain associated with the configuration that uses them.

IDENTITY + CONFIGURATION

03 / MEMORY & SOURCES

Sources remain connected to what was retained.

Prepared knowledge and acquired memory carry their source references, revisions and access scope. Retained media and required cold-memory payloads form part of the complete dependency set.

The file preserves the relationships needed to reconstruct memory. During operation, the GPU owns the active catalogue and selection decisions, including when an explicitly selected offload mode is in use.

MEMORY + PROVENANCE

04 / COGNITIVE POLICY

Rules travel with their restorable state.

A profile can select supplied policy, authored policy data or trusted CUDA/PTX modules. Required native assets and the state they maintain are packaged with that selection.

The destination checks compatibility and local execution trust before activation. Preserving state during a creator-policy update requires a compatible ABI, schema and size, with an explicit operator affirmation that the saved state retains its meaning.

POLICY + PERSISTENT STATE

05 / CHECKPOINT & JOURNAL

A generation identifies a coherent saved history.

The checkpoint and replay representation describe a consistent state, tied to the assets required to reconstruct it. The drain acknowledges the generation when that representation is complete.

Recovery starts from this recorded boundary. New operations then continue the restored history, with completed receipts and interrupted work retaining their distinct meanings.

CHECKPOINT + REPLAY

06 / MANIFEST & PROVENANCE

The dependency graph is part of the file.

The manifest binds assets to identities, digests, versions and dependencies. Provenance and licences accompany the required components, allowing the package to describe both its contents and their origins.

Inspection reads that account without starting a model or activating native code. Activation additionally establishes that every required component is supported and permitted on the destination.

DEPENDENCIES + COMPATIBILITY

Assets, recorded state and their dependency graph form the complete runtime profile.

Continuity across a restart

AOTX keeps live authority on the GPU while the disk drain maintains the recoverable file. CCIR connects those two positions through acknowledged generations: a defined state, its recorded history and all required assets.

01
Run
Models execute against active device-owned state.
02
Save
The drain acknowledges a coherent saved generation.
03
Restore
A compatible runtime validates and reconstructs that state.

A restart or transfer begins from a complete acknowledged generation. This gives continuation a precise meaning: the destination knows which history it has received and where new work will begin.

What travels

A self-contained dependency set

The declared profile’s cognitive assets, retained memory, settings, policy and recovery representation travel together. The complete file supplies the dependencies needed to restore the runtime, even when the original component directories are no longer available.

A portable account of state

CCIR records logical state and the information needed to reconstruct it. The destination creates its own device allocations and execution caches around that saved account.

What the destination provides

A compatible environment

The destination provides an installed AOTX runtime, CUDA driver and device with the required execution support and capacity. Activation checks the file against that environment before admitting new work.

Local control

Credentials, tool permissions and native-code grants are established by the destination’s operator. Recorded identity travels with the runtime; deployment authority remains a local decision.

One identity, shared access

A continuing instance

A hosted CCIR can serve several authenticated participants through one authoritative runtime. Private and shared spaces determine how they contribute to and recall its history.

A deliberate continuation

Copying a saved generation creates an independent continuation from that point. Use one running instance for shared access, or a complete copy when a separate history is intended.

Choosing a runtime

A continuing environment

Choose CCIR when identity, retained memory, policy and recovery should belong to one persistent unit. Its saved generations give that environment a defined path through restart and transfer.

An individual request

Ordinary supplied-context inference remains available as a separate service mode. An application can submit its own context for an operation without adopting a continuing cognitive runtime.

An explicit choice

The selected profile and effective capabilities determine the work available to each mode. The interface chapter describes their access and persistence contracts.

From one machine to the next

Prepare the continuation

A transfer starts with the source instance’s saved generation. The supported copy or export path carries its complete assets and recorded state together. The generation’s acknowledgement identifies the recoverable history, even if the live device has since advanced further.

Establish the destination

The destination inspects the file, validates its dependencies and applies local compatibility and trust decisions. It reconstructs logical state and establishes persistence before accepting new input. A completed operation can retain its recorded result; an admitted operation without a saved terminal outcome is marked interrupted.

Continue from a known point

The new instance begins with the saved identity, memory and history. Its later work forms a continuation from that boundary, with fresh local execution resources and explicitly granted access.

Read the complete portability contract