What has been tested
Check the evidence before treating an AgentCore State integration as qualified.
Guide context
Check the exact source, package and live evidence before evaluating Kam with AgentCore. Local tests and production authorization prove different things.
Before connecting an AgentCore workload, check which exact Kam package and capability the evidence covers. Source tests, local package runs, live qualification and production authorization are different stages. A deployed website or working fixture does not advance the backend's status.
On this page · 5 sections
Qualify the integration in stages
Pin the source and package
Check exactly which Kam capability and artifact was tested.
Separate local and live
A local fixture does not qualify an AgentCore connection.
Authorize production separately
A passed integration check does not grant permission to serve customers.
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. This label does not establish package or live qualification.
Locally qualified
Exercised as a packaged or local artifact (CI, local lab, or simulated AWS transports). This does not establish live AWS qualification.
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#
Reviewed source records isolated AWS qualification attempts, including failures and cleanup. No matched passed live receipt or customer-production authorization was verified for this release combination. The older regional inventory is a historical observation, not evidence of current global absence.
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: e16b81b4
main through PR #267. Backend capability claims in this review refer to this checkpoint.
Reviewed source, packaged and qualified in CI: e16b81b4
main · qualification run 38541006600. Same commit and tree as the reviewed source. Service, SDK and native artifact round trips passed; simulated transports and offline consumers do not establish live qualification.
Historical package candidate selected for live qualification: 284f26e5
PR #206 candidate · merged as a215d31f · run 37605352449. Preserved from the 2026-10-07 review; this older artifact is not the current main package. No matching passed live receipt is recorded here.
Native developer toolkit: e16b81b4
merged in PR #176 (d5056454) · native artifact round trip in run 38541006600. Linux x64 only. No public distribution.
History and State SDK candidate: e16b81b4
SDK 0.40.0 · artifact round trip in run 38541006600. Not published to npm. Exact source commit, package hash and offline clean-consumer receipt are recorded in docs/content-evidence.md.
Website runtime SDK: 96dff834
vendored SDK 0.46.0 · local producer 1792452589183 attempt 1 · official offline verification 2026-10-19. Independently qualified, unpublished SDK candidate pinned for server reads. Exact archive, release receipt, SBOM and official offline verifier retain the actual local producer identity and source branch in vendor/kam-history-sdk. SDK production is separate from hosted source qualification and live authorization. Older 0.45.0, 0.43.0, 0.40.0 and 0.36.0 records remain historical. Native application builds require separate qualification.
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
Reviewed View and reconciliation source; no live-qualified or publicly offered hosted State service is established.
State queries & Components — Source-implemented
SDK 0.40.0 has a passed offline artifact receipt; the source claim is limited to supported bounded operations, not arbitrary payload queries or live service qualification.
Metrics, materialize & watch — Planned · not available
Design preview only.
Turn Lifecycle — Locally qualified
Merged native toolkit; reference-only local frames.
Versioned Context manifests — Source-implemented
Exact capture, ordered manifests and bounded assembly exist in source. Automatic ranking, managed runtime wiring and live model-consumption proof are not established.
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 and package tested
State pointers, immutable Observations, and change evidence are conditionally persisted. The private SDK reads current Active State and retained exact Observations. Offline checks do not establish production qualification.
State reconciliation — Source implemented
Bounded View registration, acyclic reverse-dependency membership, durable cursor/task progress, and same-scope multi-source reconciliation are implemented. General cross-scope joins remain planned.
State queries — Source implemented
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.
Turn Frames and profiler — Merged · locally qualified
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.
Exact Context and request boundaries — Source implemented · live unqualified
Capture exact evidence, assemble ordered manifest references, and record hide/restore changes. A controlled injected adapter can report request stages. Automatic interception, provider-wide budgeting, and managed action barriers remain planned.
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) — 365-day plan · not executed
A separate bounded closing-ATS replay passed locally with real Rust and simulated storage at an earlier source checkpoint. The full 365-UTC-date real-history plan, live season workload, process-crash recovery, and hosted compatibility remain unqualified. Kam Sports supplies grades; Kam records them.
History console — Implemented in website source
The read-only console uses configured Cognito identity and existing History reads to browse authorized workspaces, manually entered scopes, UTC days, and exact revisions. Production History configuration is absent in the reviewed web deployment, so it reads no History data.
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.