# Prove one outcome all the way to an exact read

Map one declared workload result into Kam History and read it back exactly. The SDK journey qualifies those stages, not AgentCore execution or Memory consumption.

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/golden-journey

## In short

Take one declared result from an AgentCore workload through acceptance, exact retry, pinned listing and exact readback. The SDK journey records evidence for each stage it performs. It does not invoke the agent or prove Memory delivery, model use or external completion.

**Available today:** The documented SDK harness requires an authorized evaluation endpoint. Source/package runs and a live AgentCore qualification are distinct.

> Trace one result from an AgentCore workload through State recording and exact reads. Verify execution and Memory delivery separately.

## Prove the recorded result, one stage at a time

- **Submit a declared outcome** — Use approved evidence from the workload; pending or unknown is not failure.
- **Keep the list pinned** — Carry generation and cursor through bounded History pages.
- **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.

[Open the synthetic History example](/#trajectory)

[Read the scoped SDK example](/docs/integrate)

[Explore the native candidate](/developers)