# Kam State documentation

Use Kam State alongside Amazon Bedrock AgentCore. Start with one recorded result, read its exact version, and learn which source capabilities and integration steps still need qualification.

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

## In short

Kam State is a State Management add-on for Amazon Bedrock AgentCore. Your application records results and selects exact retained evidence; AgentCore hosts agents and tools. Systems of record remain authoritative for their own business data, and Memory recall stays separate.

**Available today:** Private SDK 0.40.0 includes exact History, Views, current State, bounded queries and Context manifests. Local receipts do not establish a hosted or live-qualified AgentCore integration.

> Reduce custom state-management work around your AgentCore application with exact State and History.

## What Kam does today

Your app sends results to Kam. Kam keeps numbered versions and corrections, returns the exact retained version requested, and reports when it cannot. Kam uses declared dependencies to identify and reconcile affected Views. General metric APIs, materialize and watch remain planned.

Amazon Bedrock AgentCore hosts your agents and tools. Your application decides when to call them and what their results mean. Kam preserves the State and exact versions your application records; AgentCore Memory provides separate recall.

1. **Identity · Implemented in source** — Stable logical identity for every entity, so a correction updates the same thing instead of creating a duplicate.

2. **Versions · Implemented in source** — Immutable revisions. A newer revision never rewrites what an older read returned.

3. **Membership · Implemented in source** — A fixed, ordered list of the exact revisions that belong to one collection at one point in time.

4. **History · Implemented in source** — The retained record of accepted revisions, corrections, and published generations.

5. **Dependencies · Implemented in source** — Versioned records of which Views read which sources, so a change can find exactly what it affects.

6. **Views · Implemented in source** — Bounded, owner-configured definitions over source State, normalized and hash-bound by Rust.

7. **Materialization · Implemented in source** — Conditionally committed Active State for bounded same-scope Views with one or more sources. Source implementation, not a public hosted service.

8. **Queries · Implemented in source** — Bounded where, pick, orderBy and take over one Active State's evidence, with explain() before value().

9. **Replay · Implemented in source** — Re-run synthetic scenarios against the real Rust engine and explain why State changed or was reused.

10. **Metrics · Planned · not available** — General derived metrics that recompute when an input changes. Today only rolling outcome comparisons are implemented.

11. **Watch · Planned · not available** — Customer subscriptions that fire when a materialized view changes.

## Three questions Kam answers today

1. **What exact evidence existed?** — History preserves accepted revisions and fixed membership under stable identity.

2. **What changed, and which Views need reconciliation?** — Versioned Views and State reconciliation separate affected dependencies from retained immutable evidence.

3. **What should this reasoning turn see?** — Your app selects exact captured evidence in a versioned Context manifest. Bounded assembly exists in source; the native toolkit also prepares local reference-only Turn Frames. Managed runtime wiring remains planned.

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

[Follow the History example](/?capability=workflows#trajectory)

[Read the State API design](/docs/state-api)

## Choose the right entry point

Start with private SDK 0.40.0. Exact History, Views, current-State reads, bounded queries and versioned Context manifests are implemented in source. The reviewed package receipts qualify local or simulated execution; they do not establish a publicly offered hosted service, live production use or a Marketplace listing.

[Normalized State and collection architecture](/docs/normalized-state)

[State queries and the design preview](/docs/state-api)

[State and required evidence](/docs/state)

[Native toolkit](/docs/toolkit)

[What changed](/updates)

## A rolling view, not permanent recall

The working history covers 365 UTC dates. Supporting evidence has its own inspection limits. A recovery checkpoint is saved processing state, not a lifetime summary.

[Read the retention contract](/docs/retention)