ENGINEERING UPDATES / SOURCE-REVIEWED

What changed. What is ready to evaluate.

History remains the durable kernel. Merged View/reconciliation work, the local Turn-Frame/profiler candidate, and planned live Turn/Context capabilities are separate milestones with separate evidence.

REVIEWED 2026-10-06

Important implementation changes.

This is a fixed content review, not live deployment status. Each entry states its remaining boundary.

Local candidate · in review

PR #176 review candidate

Turn-cycle preparation joins the Rust developer toolkit

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

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.

Validated local Turn Frames, reference preparation, and State profiling exist in the unmerged native-toolkit candidate. They do not intercept live AgentCore turns, submit model requests, persist managed Turn Receipts, or authorize external effects.

Read the implementation guide ↗

Internal implementation

Merged backend through PR #186

State retains evidence and owner-configured Views

The backend now combines the trajectory-current State slice with a bounded Rust-admitted versioned View registry and reverse-dependency memberships.

Rust normalizes and hash-binds owner-configured View definitions.
Graph mutations are versioned and cyclic successors are rejected inside the bounded membership set.
The executable dependent slice currently supports one required same-scope source.

A bounded owner-configured View registry and reverse-dependency memberships are implemented in source. The managed execution path currently supports one required same-scope source; multi-source joins, public current-State serving, live Turn interception, and customer realtime subscriptions remain staged.

Read the implementation guide ↗

Internal implementation

Merged backend implementation

Durable affected-View progress executes one bounded slice

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.

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

General multi-source joins, public current-State reads, full typed semantic early cutoff and customer realtime subscriptions remain future work.

Read the implementation guide ↗

Implemented in source

Merged SDK and control-plane implementation

SDK 0.31.0 exposes bounded View configuration

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

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.

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

Read the implementation guide ↗

AVAILABILITY IS PART OF THE CONTRACT

Source does not equal subscription.

Implemented in source

The reviewed source contains this capability. Access, package publication, and live deployment are separate.

Internal implementation

A supported internal service path exists. Do not infer a general public API.

Local candidate · in review

Implemented on a separate, unmerged candidate branch. Local qualification does not make it a public release.

Implemented · default off

Implemented behind explicit activation controls. Live permissions and behavior still require qualification.

Planned · not available

A design or future product direction, not an available capability.

THE PLATFORM AT A GLANCE

One foundation. Explicit capability boundaries.

Implemented in source

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 source

Identity & membership

Use generation-bound membership plus exact hydration as the normalized primitive beneath change detection, checkpoints, and replay.

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

Read identity & membership docs

Internal implementation

Views & Active State

Rust admits bounded versioned Views, reverse dependencies, freshness rules, and supported dependent-State reconciliation.

The executable managed slice supports one required same-scope source; multi-source joins and public State serving remain staged.

Read views & active state docs

Local candidate · in review

Turn Lifecycle

Treat each reasoning turn as a validated render over evolving Active State and bind local Turn Frames to exact reference preparation.

Read turn lifecycle docs

Planned · not available

Context compiler

Compile required evidence first, deduplicate exact references, admit optional evidence within explicit budgets, and preserve provenance.

No managed payload-bearing context service, complete provider-request budgeting, or live runtime injection is available yet.

Read context compiler docs

Internal implementation

Operational durability

Persist History, reconciliation progress, State identities, Observations, and receipts so operational understanding survives worker and agent lifecycles.

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

Read operational durability docs

Local candidate · in review

Profiler & developer toolkit

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

Unmerged Linux x64 candidate. Metrics do not claim live cache hits, model consumption, latency, or avoided-work percentages.

Read profiler & developer toolkit docs

Implemented · default off

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 announced as available: public current-State/Observation serving, multi-source managed joins, live Turn interception, payload-bearing Context compilation, action barriers, WakePlans, production operational checkpoints, cloud sandboxes, public sharing, automatic S3 archives, or a live Marketplace listing. See reliability and release gates.

ONE WORKLOAD. A CLEAR ACCEPTANCE TEST.

Bring the history your agents depend on.

Discuss your AgentCore workload, data boundary, and the failure cases an evaluation must prove.

Discuss an evaluation See evaluation scopePrelaunch. No production commitment implied.