Skip to main content

Exact identity + versioned membership

Kam State adds versioned application state to Amazon Bedrock AgentCore.

Share exact Kam State references across AgentCore inspection views, using fixed History membership and retained revisions.

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

Use Kam State identity and membership contracts in an Amazon Bedrock AgentCore application. Exact revisions and generation-pinned lists support repeatable inspection while sharing retained records across views.

Give an AgentCore application exact references it can inspect later through Kam State. allIds() fixes ordered History membership; byIds() fetches precisely those retained revisions. Keeping membership separate from payloads allows graph, timeline and comparison views to share the same recorded evidence. Inspection does not rerun the original agent or tool, and these methods retain their bounded History contract.

On this page · 3 sections

Two primitives beneath the workspace

  1. allIds()

    Fix the ordered History references for the application's read.

  2. byIds()

    Fetch exactly the retained revisions that membership names.

  3. Views

    Use graph and timeline to inspect those answers without rerunning AgentCore work.

allIds() fixes membership#

A bounded day generation names ordered exact revision references. Preserve the returned generation and cursor while paging; a late arrival belongs to a successor generation rather than silently changing the collection being read.

The broader platform reuses this normalized-state idea, but the existing allIds() API keeps its exact History contract rather than becoming a generic dependency endpoint.

byIds() hydrates exactly what was named#

Hydration restores caller order and reports found, unresolved, unavailable and expired positions explicitly. It does not replace an unavailable historical revision with the latest value.

Stable identity plus immutable revisions makes a later diff inspectable: unchanged references can be structurally shared while changed membership becomes an explicit input to reconciliation.

Exact reads depend on the contract#

The value comes from the contract: stable logical identity, immutable revision identity, ordered bounded membership, generation pinning, correction rules, authorization, retention and recovery.

That foundation can support exact checkpoints, replay, State and Context profiling and turn-to-turn change explanations without making probabilistic retrieval the source of operational truth.

Agent-readable documentation manifest