Engineering updates

See what changed and what still needs testing.

Follow Kam State changes for Amazon Bedrock AgentCore builders. Each update links reviewed code to evidence, availability, and remaining live checks.

Reviewed commits and packages

Reviewed 2026-10-14

State Management changes reviewed on 2026-10-14.

2026-10-14Implemented in source

Backend through PR #267 · e16b81b4

Exact Context and history inspection in private SDK 0.40

Impact: The review at this checkpoint covers ordered exact Context manifests, explicit hide and restore, History inspection that preserves requested references, and local application-host composition. Backend CI qualified separate service, SDK, and Linux x64 native artifacts without live AWS.

What changed in detail

Capture exact evidence and assemble the references recorded in a versioned manifest; no generic relevance ranking.
Read exact History revisions with one byIds call, in requested-reference order, while preserving partial and unknown results.
Local SQLite host composition uses explicit authorization and restart recovery; it is a separate unpublished package.
Controlled request-boundary adapters report only stages explicitly observed by the injected boundary.

Readiness: Private packages, simulated AWS, and local tests. No public hosted service, automatic AgentCore interception, or passing current-main production qualification is claimed.

Read this change’s guide →

2026-10-14Implemented in source

Merged backend through PR #219 · 1db8cf00

State queries, Components, and the native toolkit land on main

Impact: SDK 0.36.0 adds a declarative state()/component() surface and bounded State queries, the reconciler supports same-scope multi-source Views, and the native toolkit is merged. Backend CI run 37686977815 qualified the package, SDK and native toolkit artifacts at this commit.

What changed in detail

query()/select() with where, pick, orderBy and take; explain() returns the admitted plan (tenant-bound, ≤ 34 storage reads, no table scan) and value() executes it over one Active State's evidence.
activeState() and observation() read current State and exact retained assessments; a missing version never falls back to latest.
Bounded same-scope multi-source dependency processing in the Rust reconciler.
The native toolkit (PR #176) is merged and qualified as a network-disabled Linux x64 artifact.

Readiness: Historical SDK 0.36.0 qualification. Later releases added bounded collection operators and exact Context; general metrics, materialize, watch, and arbitrary source queries remain planned.

Read this change’s guide →

2026-10-14Merged · local only

PR #176 · reviewed as a candidate, merged 2026-10-07

Turn-cycle preparation joins the Rust developer toolkit

Impact: The native candidate now includes validated local Turn Frames, reference preparation, State profiles, and one-way Rust ownership from evidence through turn context assembly.

What changed in detail

kam turn and the read-only MCP turn tool share one bounded pair handler.
Local frames bind exact assessment/input hashes, prior-frame identity, State identity and reference-artifact identity.
Prepared local evidence explicitly reports model submission, live authorization and persisted Turn Receipt as not observed or not committed.

Readiness: The Linux x64 native toolkit qualifies reference-only local Turn Frames. Exact Context capture, manifest assembly, and a controlled request-boundary adapter also exist in source. Automatic runtime interception and managed AgentCore wiring remain planned. Model submission, completion, and business acceptance are not observed unless an injected boundary explicitly reports them.

Read this change’s guide →

2026-10-14Implemented in source

Merged backend through PR #186

State retains evidence and owner-configured Views

Impact: At this checkpoint, the backend combines the trajectory-current State slice with a bounded, versioned View registry validated by Rust and an index of dependent Views.

What changed in detail

Rust normalizes and hash-binds owner-configured View definitions.
Graph mutations are versioned and cyclic successors are rejected inside the bounded membership set.
At this checkpoint the executable dependent slice supported one required same-scope source; PR #187 later added bounded same-scope multi-source processing.

Readiness: Versioned Views, dependencies, current State, and bounded reconciliation are implemented in reviewed source. The exact main package is locally qualified with simulated AWS transports. That does not establish customer-production use or a publicly offered hosted service.

Read this change’s guide →

2026-10-14Implemented in source

Merged backend implementation

Durable affected-View progress executes one bounded slice

Impact: Affected-View discovery persists cursor and task progress and the server-owned execution path point-reads exact source State and Observation evidence before conditionally committing dependent State.

What changed in detail

Lost initial enqueue is redriven from durable discovery progress.
Lifecycle, membership version and source-State version are checked again at commit.

Readiness: Superseded in part: PR #187 added same-scope multi-source processing and the SDK now reads current State. Cross-scope joins, full typed semantic early cutoff, and customer real-time subscriptions remain future work.

Read this change’s guide →

2026-10-14Implemented in source

Merged SDK and control-plane implementation

SDK 0.31.0 exposes bounded View configuration

Impact: The candidate SDK adds owner-only State View configuration while preserving scoped clients, History reads and explicit lifecycle and customer-exit controls.

What changed in detail

configureStateView() sends a versioned definition that Rust normalizes and hash-binds.
State dependency registration resolves the stored View revision rather than trusting a caller-provided hash.
kam-history doctor remains a separate authenticated metadata diagnostic.

Readiness: The SDK is not published to npm. Live buyer, revocation, erasure, restore and production State-serving journeys still need separate qualification.

Read this change’s guide →

At a glance

Check each capability’s status.

Every part and its status

Implemented in sourceLocally qualified

History

Preserve exact revisions and fixed membership so historical state never means whatever is latest now.

Availability and idempotency follow retained-evidence deadlines. Exact does not mean permanent.

Read history docs

Implemented in sourceLocally qualified

Identity & membership

Keep collection membership fixed to a generation, then read those exact revisions. This provides a stable basis for change detection, checkpoints, and replay.

This generalizes the design idea; today’s allIds() keeps its specific bounded day-membership contract.

Read identity & membership docs

Implemented in sourceSource-implemented

Views & Active State

Rust admits bounded versioned Views, reverse dependencies, freshness rules, and same-scope dependent-State reconciliation over one or more sources; the SDK reads current Active State and retained Observations.

Versioned Views, dependencies, current State, and bounded reconciliation are implemented in reviewed source. The exact main package is locally qualified with simulated AWS transports. That does not establish customer-production use or a publicly offered hosted service.

Read views & active state docs

Implemented in sourceSource-implemented

State queries & Components

Declare scoped State and Components, select admitted evidence references, and inspect the bounded plan before execution.

Private SDK 0.40.0 implements scoped State, Components, bounded evidence-reference queries, composition, and exact Context APIs (OpenAPI 1.31.0). Its clean offline artifact round trip passed on reviewed main. The SDK is not published to npm or qualified for customer production. Queries operate on admitted evidence references; general source-payload queries, managed metrics, materialize(), watch(), and managed lifecycle integration remain planned capabilities.

Read state queries & components docs

Planned · not availablePlanned · not available

Metrics, materialize & watch

Planned metrics would update derived Views when inputs change and notify your application, which decides when to run agents.

Design preview. Not implemented in any SDK; no customer subscription, source connector, or derived-metric service exists.

Read metrics, materialize & watch docs

Merged · local onlyLocally qualified

Turn Lifecycle

Inspect local preparation for an AgentCore turn: compare exact source versions and bind a local Turn Frame to the references it prepared.

The Linux x64 native toolkit qualifies reference-only local Turn Frames. Exact Context capture, manifest assembly, and a controlled request-boundary adapter also exist in source. Automatic runtime interception and managed AgentCore wiring remain planned. Model submission, completion, and business acceptance are not observed unless an injected boundary explicitly reports them.

Read turn lifecycle docs

Implemented in sourceSource-implemented

Exact Context

Capture exact evidence and assemble the ordered references an application records in a versioned manifest. Keep hide and restore changes inspectable.

Source implemented and privately packaged. No automatic runtime interception, generic relevance ranking, or complete provider-request budgeting is qualified.

Read exact context docs

Internal implementationSource-implemented

Operational durability

Persist History, reconciliation progress, State identities, Observations, and receipts so recorded evidence and pending Kam work can be recovered after interruptions.

Kam does not replace AgentCore execution checkpoints. A named managed operational-checkpoint API and live Turn Journal remain staged.

Read operational durability docs

Merged · local onlyLocally qualified

Profiler & developer toolkit

Inspect why State changed or was reused, compare local turn preparation, replay synthetic scenarios, and use read-only MCP tools.

Merged; qualified on Linux x64 only, with no public binary. Metrics do not claim live cache hits, model consumption, latency, or avoided-work percentages.

Read profiler & developer toolkit docs

Implemented · default offLocally qualified

Optional AgentCore delivery

Distinguish acknowledged submission, verified retrieval, retryable uncertainty, and explicit stop states.

Default off. Source and simulated package checks are not live AgentCore qualification.

Read optional agentcore delivery docs

Not available yet: a published SDK, public hosted access, live watch or metrics, automatic runtime interception, automatic S3 archives, or a live Marketplace listing. See what is tested and what is not.

One application. One workflow.

Evaluate Kam State for your AgentCore application.

Bring one workflow with a correction or retry. Agree the baseline, scope, and success checks before starting.

Plan an evaluation Read the evaluation scope