Skip to main content

Keep the Observation when current State changes

Inspect the recorded assessment an AgentCore task could read, without claiming model consumption.

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

Inspect the retained assessment behind an AgentCore application's State change. An Observation records Kam's selection, not what a model consumed.

When current State changes, inspect the retained assessment and exact sources behind the change. An AgentCore application can use that evidence for review. The Observation records what Kam selected; it does not reconstruct later prompt formatting or prove model consumption.

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