# Accepted work remains accountable

Review how Kam preserves recorded State, authority and unfinished processing when an AgentCore workload is interrupted or delivery is uncertain.

Status: Implemented in source. Prelaunch; not a live service guarantee.

Reviewed: 2026-10-14.
Backend source: e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
Native toolkit: merged in PR #176, reviewed at e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
HTML: /docs/reliability

## In short

When an AgentCore workload is interrupted, separate the runtime's next action from Kam's unfinished State processing. Recheck authority and inspect uncertain delivery before retrying. Kam keeps uncertainty visible instead of converting an unknown effect into a successful result.

**Available today:** Source recovery and lifecycle controls exist. Live cancellation, downstream erasure, restore drills and AgentCore integration remain separate qualification gates.

> Recover recorded State alongside AgentCore work while keeping uncertain effects explicit.

## 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.

> **Current release boundary**
> Marketplace availability, production p99, and production AgentCore write-back remain qualification gates. The delivery loop is implemented, disabled by default, and tested through simulated transport. This is not live production qualification.

## 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.

[Read the customer lifecycle boundary](/docs/marketplace)