Retention boundaries
Retention, inspection, and deletion
Four data layers require distinct retention and deletion policies.
Do not promise an inspectable history after its evidence is gone.
Kam working history
365 UTC dates
The candidate maintains today and the preceding 364 UTC dates. This is a working-window contract, not observed uptime.
Kam supporting evidence
May extend beyond one year
The candidate retains supporting revisions and references for up to 730 days, with direct-prior-revision extensions for corrections. Inspection ends when its evidence expires.
AgentCore raw events
Configurable, up to 365 days
AWS applies this retention setting to raw short-term events. It is not a universal long-term-memory retention policy.
AgentCore long-term records
Separate lifecycle policy
AWS describes explicit deletion workflows. Do not assume the raw-event expiry setting automatically deletes long-term records.
AWS documentation
AWS documents up to 365 days for raw short-term events. Its long-term-memory lifecycle example uses explicit record deletion rather than treating raw-event expiry as universal TTL.
Deletion is an operation, not a number
Logical expiry, export, physical erasure, downstream cleanup, and backup restoration have different responsibilities. Kam’s end-to-end customer-deletion and backup anti-resurrection workflows remain release gates.