What has been tested
Read the evidence for a pinned source revision—not a blanket certification.
Guide context
Source behavior, packaged execution, and a live customer deployment answer different questions.
Tests on source code, tests on a packaged build, a live qualification, and a production authorization prove different things. Each capability is shown at the highest of those six levels its evidence still supports.
On this page · 5 sections
Six evidence levels
Planned → implemented
A design becomes source with tests.
Local → live
Local or simulated evidence does not qualify AWS behavior.
Pilot → production
Explicit scope and authorization remain separate gates.
Six evidence levels#
Every capability is shown at the highest level its recorded evidence still supports. Each level needs the one beneath it, and missing, stale, failed, or mismatched evidence lowers the shown level automatically.
Planned · not available
Design direction. No implementation is claimed.
Source-implemented
Implemented in reviewed source with source-level tests. Not executed as a packaged artifact.
Locally qualified
Exercised as a packaged or local artifact (CI, local lab, or simulated AWS transports). No live AWS deployment.
Live-qualified
A passed live qualification receipt binds this exact package to an isolated AWS deployment.
Pilot only
Live-qualified and authorized for a named, bounded pilot. Not general availability.
Production-authorized
Live-qualified and explicitly authorized for production use.
The release combination behind these pages#
No deployment of the History/State candidate was found in the inspected AWS Regions. Existing Kam resources belong to earlier products and are not evidence for this one.
Live qualification receipts recorded: 0. Live receipts are accepted only in the backend schema kam.live-agentcore-qualification-receipt.v6 with status passed, bound to the exact recorded package commit.
Source the website claims were reviewed against: 1db8cf00
main through PR #219. Every public capability statement is checked against this checkpoint.
Reviewed source, packaged and qualified in CI: 1db8cf00
main · qualification run 37686977815. Same commit as the reviewed source. Package, SDK and native artifact round trips passed with simulated AWS transports; not a live deployment.
Packaged candidate selected for live qualification: 284f26e5
PR #206 candidate · merged as a215d31f · run 37605352449. Named by the backend live-AWS approval document at the reviewed checkpoint. No live receipt exists.
Native developer toolkit: 1db8cf00
merged in PR #176 (d5056454) · native artifact round trip in run 37686977815. Linux x64 only. No public distribution.
History and State SDK candidate: 1db8cf00
SDK 0.36.0 · artifact round trip in run 37686977815. Not published to npm. The website console vendors this exact tarball.
History — Locally qualified
Package qualification is not a live deployment.
Identity & membership — Locally qualified
Covered by the same package qualification as History.
Views & current State — Source-implemented
Not deployed. Package coverage of View reconciliation is not confirmed for the website.
State queries & Components — Source-implemented
SDK 0.36.0 candidate; whether the SDK artifact round trip exercises queries is not confirmed for the website.
Metrics, materialize & watch — Planned · not available
Design preview only.
Turn Lifecycle — Locally qualified
Merged native toolkit; reference-only local frames.
Context compiler — Planned · not available
Design direction only.
Operational durability — Source-implemented
History and reconciliation progress are durable in source; no named checkpoint API.
Profiler & developer toolkit — Locally qualified
Merged; Linux x64 only; no public distribution.
Optional AgentCore delivery — Locally qualified
Default off; simulated AWS transports only.
Export, deletion & restore fence — Source-implemented
Live erasure and restore drills are qualification gates.
Current evidence boundary#
Ordered, versioned ledger — Source and package tested
Exact revisions, pinned daily pages, corrections, rolling windows, and independent 400/730-day synthetic-history checks. Synthetic time is not observed uptime.
Rust State and Observations — Source implemented
State pointers, immutable structured Observations, and change evidence are conditionally persisted. The SDK 0.36.0 candidate reads current Active State and exact retained Observations. No State or Context endpoint is deployed.
State reconciliation — Source implemented
Bounded View registration, acyclic reverse-dependency membership, replay-safe cursor/task progress, and bounded same-scope multi-source dependency processing are implemented. Cross-scope joins and a deployed State endpoint remain staged.
State queries — Source implemented
The reviewed SDK 0.36.0 baseline, unpublished and undeployed, implements state(), component(), and bounded select stages (where, pick, orderBy, take) with explain() and value() over the admitted evidence of one View's Active State. SDK 0.37.0 merged in PR #220 (not publicly published and not included in the pinned 0.36.0 website qualification) adds bounded operators over that same selected collection. General source-payload queries, managed metrics, calculation caching, graph traversal, materialize(), watch(), and lifecycle integration remain separate planned capabilities.
Turn Frames and profiler — Merged · locally qualified
Validated local Turn Frames, reference preparation, and State profiling exist in the merged native toolkit and run locally only. They do not intercept live AgentCore turns, submit model requests, persist managed Turn Receipts, or authorize external effects.
Live Turn Lifecycle and Context — Planned · not available
The product direction is to resolve current operational checkpoints, detect typed changes, compile bounded Observations, bind turns to exact ReadSets, and revalidate consequential effects. No live runtime hook or managed action barrier is claimed.
Native developer toolkit — Merged · locally qualified
Native toolkit 0.1.0 is merged into the backend (PR #176) and qualified in CI as a network-disabled Linux x64 artifact. No public binary release, macOS/Windows distribution, or live AWS connection is offered here.
Customer lifecycle — Source implemented · live unqualified
Bounded owner export, primary-state deletion, restore fences, and Marketplace entitlement reconciliation are implemented in source. Live buyer, erasure, restore, and revocation journeys remain qualification gates; no deployed completeness is claimed.
AgentCore delivery — Implemented · default off
Destination binding, per-generation obligations, scheduling, publication receipts, exact retrieval verification, and metadata-only status are implemented. Optional Memory write-back remains separately qualified with simulated AWS transports.
Carry-forward consolidation — Proposed · not implemented
A versioned long-term summary baseline and automatic S3 archival are not implemented. Checkpoint recovery does not preserve expired contributions as institutional knowledge.
Real-history verification (Kam Sports) — Planned · not executed
The verification plan replays real Kam Sports history through the unchanged History contract across the 365-UTC-date working window and checks exact reads, corrections, and recovery. Kam Sports grading stays authoritative; Kam records grades, it never computes them. No run has completed yet.
History console — Implemented in website source
A read-only, Amplify-authenticated console browses workspaces, scopes, UTC days, and exact revisions through existing History API reads. It is not connected to a live History deployment, because none exists yet; without configuration it reads nothing.
Production assurance — Not yet qualified
Source checks and independent artifact execution do not establish deployed IAM, a Marketplace listing, production SLOs, compliance approval, or measured costs and latency.
Reference workload, not enterprise semantics#
NFL helped establish patterns in the separate sports project. This extracted service uses a terminal-outcome reducer; it does not import ATS grading, provider capture, or game finalization into customer workflows.
Bounded work is not a latency measurement#
Candidate limits include 32 scopes per licensed workspace, eight cumulative categories, 4,096 identities per scope/day, and up to 32 references per read. These are supported-envelope limits, not throughput or cost promises.
Live acceptance/read latency, local publication lag, AgentCore visibility, costs, and oldest-pending work still need measurement. The website charts use synthetic records and do not report production performance.