Accepted work remains accountable
Kam State adds versioned application state to Amazon Bedrock AgentCore.
Review Kam State’s durable progress and authority checks for AgentCore workloads, keeping uncertain effects explicit while recovering accepted State processing.
Guide context
Review how Kam State preserves accepted work beside Amazon Bedrock AgentCore. Durable progress, authority fences and explicit uncertain outcomes define the State recovery work the source supports.
When an AgentCore workload is interrupted, separate its next action from Kam State’s unfinished processing. Durable progress and authority fences support accepted-State recovery within declared limits, reducing custom recovery work. Recheck authority and uncertain delivery before retrying. Kam does not turn unknown effects into success or resume the whole application workflow.
On this page · 4 sections
Recover State without guessing effects
Inspect unfinished processing
Separate Kam obligations from AgentCore execution progress.
Retain the attempt evidence
An ambiguous effect stays unknown until the relevant evidence resolves it.
Recheck authority
The application must validate permission before another external action.
Keep local processing and delivery separate#
Lifecycle fencing and bounded draining are implemented candidates. Delivery additionally owns one obligation per eligible generation. Local application does not prove remote submission, and remote submission does not prove retrieval.
Do not let an old job inherit new authority#
An outcome keeps its acceptance epoch. Cancellation closes new acceptance and may authorize a bounded local drain. Renewal advances authority again. Delivery stops new remote attempts when the lifecycle closes or its destination binding changes; an old obligation is not silently rebound.
Uncertain is not failed, cancelled, or complete#
An ambiguous response preserves the request identity and durable receipt. Recovery waits for the relevant lease or scheduled retry boundary. Exhausted publication or verification attempts require reconciliation; they are not counted as success. A failed read does not trigger a new create.
Implemented exit controls still need live qualification#
Bounded owner export, export-bound primary deletion, and a separately retained restore fence are implemented. Marketplace reconciliation is license-scoped. Live purchase, cancellation, downstream erasure, and restore drills remain separate gates. A restored table being available does not establish that it is safe to serve.