# Recover recorded State alongside your workflow

Read recorded State again when an AgentCore application resumes work. Runtime continuation and Kam's durable reconciliation have separate owners.

Status: Internal implementation. Prelaunch; not a live service guarantee.
History and reconciliation durability exist in source. A named managed operational-checkpoint API, live Turn Journal, WakePlan and persisted Turn Receipt lifecycle remain staged.

Reviewed: 2026-10-14.
Backend source: e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
Native toolkit: merged in PR #176, reviewed at e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
HTML: /docs/durability

## In short

When an AgentCore application resumes work, read the State it needs again and recheck whether it applies. Kam retains accepted revisions and its own reconciliation progress. Runtime continuation, tool retries and the decision to act stay with the runtime and application.

**Available today:** Source History and reconciliation recover their own progress; the explicit local SQLite host also recovers accepted work. Managed operational checkpoints remain planned.

> Resume your AgentCore workload and recheck the recorded State it needs.

## Rejoin execution with recorded State

- **Resume the workload** — Your AgentCore runtime and application own continuation and tool attempts.
- **Read and revalidate State** — Kam retains admitted versions and recovers its own reconciliation progress.
- **Stop on uncertainty** — Your application must verify unknown external effects and current permissions before deciding whether to retry.

## Two timelines should remain independent

Your AgentCore application owns how execution resumes. Kam preserves accepted State and advances supported reconciliation as recorded evidence changes. On the next turn, the application must read again and check whether a previous Observation still applies.

Keep workflow continuation in the runtime and application. Kam supplies exact State references and its own recorded processing progress; neither proves that an external tool action completed.

## Use exact references for checkpoints

The planned operational checkpoint is a durable coordinate across exact Snapshot or generation, View, Active State, Observation, source fences and computational versions. Immutable referenced objects can be structurally shared across many checkpoints.

Exact references make retained versions inspectable without copying every payload. Replay does not rerun tools, prove outside actions or remove retention limits.

## Durable reconciliation preserves processing progress

Affected-View discovery persists bounded progress and can redrive lost wakeups. Conditional commits recheck lifecycle, membership and source-State versions so delayed work cannot overwrite newer authority.

The future Turn layer should carry the same discipline into model submission and effects: explicit UNKNOWN outcomes, idempotent stage receipts, and revalidation instead of blind retries.