Treat State as current only while its evidence remains valid
Kam State adds versioned application state to Amazon Bedrock AgentCore.
Use Kam State’s declared dependencies and validity checks to reuse current evidence for AgentCore tasks or inspect an explicit blocker.
Guide context
Read current evidence through Kam State for an Amazon Bedrock AgentCore task. Declared dependencies, validity checks and bounded reconciliation support State reuse while keeping blockers explicit.
Ask a defined State question through Kam State, such as whether required checks are current. Current evidence requires inputs that are present, applicable and within limits; otherwise Kam reports blockers. Supported unchanged assessments reuse their pointer and avoid an unnecessary State write. Your AgentCore application decides whether work may continue; current evidence is not action approval.
On this page · 5 sections
Read State for the next task
Declare the evidence
Name the exact required and optional inputs for the application's View.
Read current State
Kam checks applicability and fixed work limits.
Decide in the application
An AgentCore task proceeds only under the application's own action rules.
The View owns requiredness#
A View declares exact source identities, required and optional dependencies, priorities, freshness windows, and selection limits. Observations report lookup results; they cannot change that policy. Current invalidation counters are supplied separately.
An omitted required observation blocks selection. Foreign sources, duplicate or missing fences, future observation times, and unexpected fields are rejected. A late read from an older fence is invalidated even when it arrives last.
Current means reusable evidence, not approval#
Missing or unresolved required evidence
State is blocked with explicit issues and no usable selection identity. Missing evidence is not silently removed.
Required references exceed the budget
State blocks instead of trimming them. Optional references follow deterministic priority with explicit budget exclusions.
Current evidence describes a failure
The result may be current and still accurately report a failed security check. Admission is not a deployment decision.
Freshness differs from retention#
A freshness deadline makes evidence stale. Its availability deadline makes it expired. A newer invalidation counter can invalidate it earlier. All deadlines are exclusive; a reuse deadline is an upper bound, not permission to ignore later changes.
Exact versions across several sources do not establish one atomic cross-source snapshot. The runtime must check current permissions and source conditions at the serving or conditional-commit boundary.
Views are connected to durable history#
The server-owned trajectory-current View is connected end to end, and owner-configured Views can depend on it within the same scope. When a View's answer changes, Kam saves the new current pointer, a frozen Observation of the assessment, and a record of what changed in one conditional write. When the answer is unchanged, Kam reuses the existing pointer and avoids an unnecessary State write.
Change notifications are queued, bounded, and re-sent by a maintenance sweep if a wakeup is lost. When a source changes, Kam pages through the Views that depend on it, up to eight at a time, and saves its cursor so it can resume safely after a crash. Dependent execution supports one or more required sources in the same scope (PR #187); cross-scope joins remain staged. The private SDK reads the result with activeState() or a Component's read().
Measure the thing being limited#
Internal admission accepts 1–32 dependencies, maxItems of 1–32, and maxReferenceBytes of 2–32,768. Reference bytes mean the UTF-8 JSON selected-reference array, including its metadata and punctuation.
This does not measure rendered prompts, model tokens, total response bytes, fetched payloads, or production latency. The native candidate’s Atlas displays the reference measurement without inventing a token conversion.