Durability boundary
Durable execution outside. Durable operational state inside.
Kam complements AgentCore runtime checkpoints by making operational History, reconciliation progress, State lineage and evidence recoverable across long-running work.
Resume the workflow and independently re-resolve the world it is about to reason over.
History and reconciliation durability exist in source. A named managed operational-checkpoint API, live Turn Journal, WakePlan and persisted Turn Receipt lifecycle remain staged.
Two timelines should remain independent
The runtime can checkpoint where execution stopped while Kam advances operational state as external evidence changes. When a sleeping agent resumes, the next turn should not assume its previous operational Observation is still applicable.
Kam therefore should not become another Durable Task or Temporal engine. It supplies the operational coordinate that a runtime turn can bind to.
A checkpoint should be references, not a copied world
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.
That makes time travel and replay cheap enough to use as developer primitives rather than heavyweight database exports.
Durable reconciliation is already a core advantage
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.