Skip to main content

Keep the Observation when current State changes

Kam State adds versioned application state to Amazon Bedrock AgentCore.

Review Kam State’s retained assessment and exact sources for an AgentCore task, reducing the need to reconstruct an earlier evidence selection.

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

Inspect retained Kam State assessments for an Amazon Bedrock AgentCore application. Exact Observations and source references support review without reconstructing the original State selection.

When current State changes, inspect the retained Kam State assessment and exact source references behind it. An AgentCore application can use that Observation for review without reconstructing the original selection. It records what Kam selected, not later prompt formatting or model consumption. Retention and current applicability still apply; historical evidence is not automatically valid for the next turn.

On this page · 3 sections

Review a retained assessment

  1. Inspect the State change

    Read the exact retained Observation and its sources.

  2. Check current applicability

    Historical evidence is not automatically valid for the next AgentCore turn.

  3. Keep the capture boundary clear

    The application's later prompt formatting and model use are separate facts.

Three records with different jobs#

  1. Active State pointer

    Identifies the current assessment for the server-owned View, with lifecycle and source-version conditions.

  2. Immutable Observation

    Retains the exact structured assessment, scope, View, pointer version, and candidate hash for that successor.

  3. Change evidence and delivery receipt

    Describe a particular transition and its internal queue delivery. They do not establish that a customer agent received it.

Selection is not the final model input#

An application may filter, reorder, truncate, or reformat selected evidence before calling a model. The structured Observation alone cannot reconstruct those later transformations.

A separately qualified capture boundary must record the assembled evidence or an approved immutable content reference, ordered source revisions, and transformation versions. Submission is still not proof of internal reasoning, consumption, or decision quality.

Immutable does not mean retained forever#

Observations are derived customer data with availability and deletion responsibilities. Current source export classifies them with the State pointer, change events, delivery receipts, and cursor. Retention and live erasure have their own gates.

The private SDK reads an exact retained Observation with observation(); it never substitutes the latest version and always reports usableForCurrentReasoning: false. This source contract is not live production qualification. Automatic S3 History archival and universal historical reconstruction are not implemented.

Agent-readable documentation manifest