Skip to main content

Prove one outcome all the way to an exact read

Kam State adds versioned application state to Amazon Bedrock AgentCore.

Evaluate the Kam State integration with one repeatable record, retry and exact-read journey for an AgentCore workload.

Implemented in sourceBackend review 2026-10-14 · prelaunchRead this guide as Markdown
Guide context

Trace one Amazon Bedrock AgentCore workload result through the Kam State SDK contract. Reusable acceptance, retry and exact-read checks support a bounded evaluation; execution and delivery need separate evidence.

Take one declared AgentCore workload result through Kam State acceptance, exact retry, pinned listing and exact readback. The SDK journey provides a repeatable way to check the supported contract and retain stage-specific evidence for integration review. It does not invoke the agent or prove Memory delivery, model use or external completion. The service journey requires an authorized evaluation endpoint.

On this page · 2 sections

Prove the recorded result, one stage at a time

  1. Submit a declared outcome

    Use approved evidence from the workload; pending or unknown is not failure.

  2. Keep the list pinned

    Carry generation and cursor through bounded History pages.

  3. Read exact versions

    Check returned dispositions without claiming AgentCore or Memory consumption.

One small journey, separate evidence stages#

  1. Map a protected external result

    Use an approved terminal check result and stable business identity. Unknown or pending is not automatically failure.

  2. Accept and retry exactly

    Keep the original payload and revision identity. Compare the returned acceptance behavior without creating another logical outcome.

  3. Enumerate a pinned day

    Preserve the generation across bounded allIds pages. A short page with a cursor is not completion.

  4. Fetch exact revisions

    Use byIds and inspect each records[] status. Check the exact event rather than assuming any successful JSON is a match.

  5. Keep the right receipt

    The harness result explains the stages it actually performed. It is not proof of live Memory delivery or model-input consumption.

Do not confuse three different demonstrations#

The website example is synthetic browser data and does not call the backend. The native toolkit supplies synthetic storage observations to the actual Rust engine. An authorized SDK/service Golden Journey crosses the real HTTP boundary.

Local source/package tests and these demonstrations do not substitute for separately authorized deployed buyer, IAM, recovery, or AgentCore qualification.

Agent-readable documentation manifest