How the event-driven paths fit together
Kam State adds versioned application state to Amazon Bedrock AgentCore.
Inspect Kam State’s durable processing path for AgentCore results, including the records that let pending work resume after a lost wakeup.
Guide context
Review Kam State processing alongside Amazon Bedrock AgentCore: durable work, bounded reconciliation and separate delivery receipts make unfinished State work inspectable.
AgentCore runs the agent while Kam State accepts recorded results, updates derived State and serves exact History. Durable work records let Kam resume its own unfinished processing within declared limits, reducing the recovery machinery teams must otherwise build around accepted State. Optional Memory delivery has separate receipts; processing progress does not prove execution, delivery or model consumption.
On this page · 4 sections
Follow each owner across the handoff
Execute in AgentCore
The runtime hosts the agent; your application controls decisions and tools.
Maintain State in Kam
Accept results, reconcile supported Views and serve exact evidence.
Deliver only when configured
Optional Memory delivery has its own receipts and is off by default.
DynamoDB stores Kam's accepted History#
Acceptance commits immutable revisions, day membership, and durable work together. A separate publication transaction commits the checkpoint, trajectory generation, and eligible delivery obligation. These are two transactions at different stages, not a transaction across AWS services.
Rust computes supported rolling views#
The worker takes saved state, accepted transitions, and an explicit time input. It performs no AWS or model I/O. last10 compares two disjoint groups of ten; utc30 and utc90 compare disjoint calendar windows and include today’s partial UTC day.
Rates use summed success and failure counts. An empty denominator is null. Deltas are percentage points. These are descriptive comparisons, not significance tests or evidence of causation.
Queues wake workers; durable records preserve unfinished work#
Bounded queue jobs and the scheduled maintenance sweep resume pending work and advance quiet histories. A delivery generation is not forgotten when enqueue fails; its durable obligation can be rediscovered after the scheduling lease.
The delivery scheduler rotates across registered scopes. Automatic recovery has explicit attempt limits and stop states; it does not imply automatic repair of every failure.
Keep archive proposals separate#
Accepted History is in DynamoDB. A source reference is not an archived copy or an atomic acceptance receipt. Automatic S3 archival and carry-forward consolidation are not implemented.