Skip to main content

Track changed inputs in an AgentCore workflow

Kam State is an add-on for Amazon Bedrock AgentCore, planned for AWS Marketplace.

Keep an AgentCore workflow’s saved check tied to the input version it covered so the application can inspect applicability after a request changes.

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

Record exact input references with AgentCore results. Inspect which retained checks match a changed request and let your application decide what to refresh.

An agent may finish a check before the customer changes the request. Keep the check and its exact input references together to inspect whether it still matches. Kam State evaluates supported declared relationships; your AgentCore application supplies those relationships, chooses what to refresh and decides whether to act.

On this page · 4 sections

Inspect which input a check covers

  1. Record the exact reference

    Keep the check tied to the input version it evaluated.

  2. Inspect the changed request

    A retained earlier check does not establish applicability to a newer input.

  3. Refresh in the application

    The application decides what to rerun and whether to act.

Record what the check actually covered#

In the synthetic refund example, the application records request@1 and a check named eligibility@1 that refers to request@1. The reference identifies the input version covered by the check. A retained result with no established input relationship cannot be assumed to apply to the next request.

The application or trusted adapter supplies the admitted relationship. An opaque History sourceRefs string alone is not a trusted exact witness. Keep input identity, revision and the supported evidence requirements aligned with the State contract.

Observation and evidence contract

Inspect the change without erasing the earlier check#

  1. Original request

    eligibility@1 refers to request@1. The example reports matching evidence for that declared input.

  2. Customer changes the request

    request@2 is a different input version. eligibility@1 still describes request@1; retaining it does not make it current for request@2.

  3. Application refreshes the check

    If the application chooses to call its eligibility tool again, it can record eligibility@2 with the exact request@2 reference.

  4. Application decides on the action

    Matching evidence is one input to the decision. Business rules, present permission and external-effect checks remain the application’s responsibility.

Inspect the synthetic refund example and its recorded output

Read the required evidence for the next task#

Use byIds for the exact retained revision required by the task. Use allIds with its fixed generation and cursor when browsing a UTC-day History collection. A later correction does not justify substituting the latest revision for an explicitly requested older one.

For supported State Views, declare which evidence is required and inspect the returned status and limits. Configuration acknowledgment does not establish that reconciliation has completed. Missing, expired or unauthorized evidence must remain explicit.

Current State and required evidence Exact History reads

Evaluate the correction in your own workflow#

Choose one real request that can change, the check that depends on it and the application decision that consumes that check. Document how the adapter establishes the exact relationship and how the application handles blocked or unavailable evidence.

Compare the original input, a changed input, a refreshed check and an unavailable source. The local public example gives a contract to inspect; connecting an authorized endpoint, running AgentCore and measuring the complete workload require separate evaluation evidence.

Integrate Kam State with AgentCore Evaluate the implementation evidence
Agent-readable documentation manifest