Retention, rolling history, and checkpoints
Saved processing state is not the same thing as permanent historical memory.
Guide context
The active working window, retained evidence, and AgentCore memory have different owners and clocks.
Kam calculates over a rolling 365-day window, keeps supporting evidence on its own clock (up to 730 days), and leaves AgentCore Memory retention to AWS. A saved checkpoint lets processing resume; it is not a permanent summary of everything ever seen.
On this page · 8 sections
Separate clocks and owners
Working History
The bounded rolling UTC-date read window.
Retained evidence
Explicit availability; expiry is never a latest fallback.
External memory
AgentCore policies are separate; archival is not a built Kam guarantee.
A rolling window. A maintained state.#
Kam advances working state as outcomes arrive and time moves forward. A recovery checkpoint keeps processing continuous; it is not a permanent summary of everything the system has seen.
Rolling operational history
The working window contains today and the previous 364 UTC dates. It advances each day, not through annual resets.
Checkpointed rolling state
Processing resumes from the persisted checkpoint and applies accepted transitions. Exact reads use published views rather than rebuilding the full history.
Versioned supporting evidence
Revisions and references support inspection until their deadlines. Supporting evidence may be retained for up to 730 days, with correction-related extensions.
Kam working history#
365 UTC dates
Today and the preceding 364 UTC dates. The window advances daily; out-of-window contributions are removed from rolling state, not consolidated into a permanent baseline.
Kam supporting evidence#
Separate inspection limits
Supporting revisions and references may remain for up to 730 days, with direct-prior-revision extensions for corrections. Inspection ends when its evidence expires; this is not automatic cold-tier archival.
AgentCore raw events#
Configurable, up to 365 days
AWS applies this retention to raw short-term events. It is separate from Kam’s window and AgentCore long-term records.
AgentCore long-term records#
Separate lifecycle policy
AWS documents explicit deletion workflows. Raw-event expiry is not a universal long-term-record deletion policy.
Carry-forward consolidation#
Preserve selected historical meaning in a versioned summary baseline while older evidence follows a separate archive policy. This is a proposed extension, not the behavior of the current rolling reducer.
Summary selection, provenance, corrections, archive verification, retrieval, and deletion need their own implementation and qualification. A summary is derived context, not a replacement for exact evidence or a guarantee against context drift.
AWS documentation#
The AWS sources below explain raw-event retention and an explicit long-term-record deletion workflow. They do not define Kam’s history contract.
Expiry does not prove erasure#
Reads enforce logical expiry before asynchronous TTL cleanup. Bounded owner export, primary-state deletion, and a restore fence are implemented in source. Live downstream erasure and restore drills remain separate release gates. A missing old reference is not rebuilt on demand or silently replaced with a newer record.