Skip to main content

From accepted outcome to verified retrieval

A queue message is a wakeup. An obligation is unfinished work. A receipt is evidence.

Implemented in sourceReviewed 2026-10-07 · prelaunchRead this guide as Markdown
Guide context

The implemented delivery loop schedules eligible local generations and keeps publication and verification receipts separate.

When enabled, Kam can publish a finished result to AgentCore Memory and then read it back to confirm it arrived. "Sent" and "confirmed" are tracked as different steps, and failures stay visible instead of being retried forever.

On this page · 4 sections

Delivery keeps its own evidence

  1. Accepted

    The outcome revision is retained.

  2. Delivered / verified

    Separate receipt states; acceptance is not delivery.

  3. Stopped

    An unfinished obligation stays visible. Default-off delivery is not live qualification.

Select an authorized destination and starting point#

A prospective delivery policy names the scope, lifecycle epoch, destination binding/version, and first eligible checkpoint version. Older generations are not implicitly backfilled. Under policy v1 every eligible generation keeps its own obligation. Under policy v2 a newer generation may replace only a candidate that was never planned, dispatched or submitted; the replaced obligation is kept as SUPERSEDED with the replacing generation. Submitted or uncertain work is never coalesced.

Read the progression and stop states#

  1. AWAITING_PUBLICATION

    Durable work exists for one eligible generation. The worker plans the authorized request and records publication attempts.

  2. AWAITING_VERIFICATION

    The write has been acknowledged. A separate exact read still needs to match the expected content and lineage.

  3. VERIFIED

    The exact record matched through the approved namespace at verification time. This is not proof of semantic-search ranking or agent consumption.

  4. Explicit stops

    REJECTED, AUTHORITY_BLOCKED, and RECONCILIATION_REQUIRED remain visible. The orchestrator does not repair mismatched remote content.

  5. SUPERSEDED (policy v2)

    A never-submitted candidate replaced by a newer generation. Counted separately from unresolved work; it is neither a failure nor a delivery.

See the delivery-state diagram

Separate local correction from remote cleanup#

Local revisions and new generations are implemented. Remote supersession, deletion, and operator reconciliation require separate work. A failed verification read does not become another create. Do not infer that publishing a newer memory automatically removes all older destination records.

Count like with like#

deliveryStatus() reports accepted/applied outcome revisions separately from local-generation delivery counts. Do not subtract verified generations from accepted revisions or chart them as one funnel.

The status read covers at most 32 scopes and 100 obligations per scope. Check coverage.complete before treating counts as complete. Counts of due or leased work overlap workflow stages; they are not extra stages to add to a total. Oldest-work reporting includes non-verified stop states.

Agent-readable documentation manifest