State
What was accepted?
Kam retains admitted records, exact versions, and receipts. byIds reads exact retained revisions; allIds browses fixed, ordered, versioned membership.
Architecture
Strands or your chosen harness runs the agent loop. Amazon Bedrock AgentCore hosts it; AG-UI carries the interaction. Your backend explicitly records supported results in Kam State for exact readback and inspection. Stream completion, State acceptance, and external effects remain separate outcomes. Live integration requires separate qualification.
Read the integration guide →Across sessions
A model request has a finite context window. Retained State can outlive that request; each new turn receives selected evidence, not the entire history.
What was accepted?
Kam retains admitted records, exact versions, and receipts. byIds reads exact retained revisions; allIds browses fixed, ordered, versioned membership.
What might help next?
Your configured memory service retrieves summaries and preferences. A retrieved memory is not proof that a tool completed or that a State write committed.
What enters this turn?
Your application selects evidence. Kam’s exact Context contract assembles a versioned manifest with item and byte limits. Preparation does not prove model consumption.
Exact History and Context assembly are implemented in source for private evaluation. Automatic selection and managed AgentCore wiring remain planned.
| Layer | Role | Responsibility |
|---|---|---|
| Chat UI + hooks | CopilotKit or your toolkit | Render messages and projected UI state. A streamed update is not a durable save receipt. |
| AG-UI | Interface protocol | Carries messages, state snapshots, and deltas. It is not the database or the harness that runs the model/tool loop. |
| Application + harness | Strands or your chosen harness | The harness runs the model/tool loop. Your application authorizes scope, selects evidence, validates inputs, and explicitly records supported outcomes. |
| AgentCore Runtime | AWS runtime | Hosts your agent code. Keep runtime sessions, application conversation IDs, and configured checkpoint recovery distinct. |
| Kam State | Accepted records and evidence | Admits supported State writes, retains exact references, and assembles bounded Context. It does not automatically capture every client mutation or tool call. |
| Semantic memory | Configured memory service | AgentCore Memory requires event capture and configured strategies for long-term extraction. Retrieval must be wired into the application. |
Your application restores the user, conversation, and permitted scope. Browser tabs and runtime sessions are not the durable identity.
Read exact State and, if configured, retrieve useful memories. The application chooses relevance; byIds/allIds provide identity and membership, not semantic search.
Assemble the selected exact references under item and byte limits. Required unavailable evidence blocks a complete package. The harness submits the request to the model.
Admit the supported outcome and exact input references. Stream UI updates separately. Keep preparation, reported submission, completion, and business acceptance distinct.
Keep configured harness checkpoints. Kam’s retained evidence does not resume an entire agent or establish an unknown tool outcome. Retained does not mean permanent; unavailable or expired revisions stay explicit and latest is never silently substituted. Automatic summarization, semantic ranking, and provider-token budgeting are not implied.
The read-only console inspects supplied records. It is not an automatic trace of every model call, tool effect, or hidden reasoning step.
Views keep the same selected revision and review boundary. Authorized History pages currently supply no exact dependency links; opaque source references do not create edges. Synthetic examples label their authored links.
Data flow
Kam data flow. Your application records results and agents read exact versions through the Kam History API, which checks access on every call. The Rust State engine keeps exact revisions and Views, and writes to DynamoDB with conditional writes. Publishing to AgentCore Memory is optional and off by default.
Choose a path
Submit a recorded outcome with stable identity.
Check scope, revision, and bounded input.
Commit the recorded outcome under version conditions.
Keep a durable record of downstream work still owed.
Conceptual examples of contracts implemented in source. They are not live traces. Optional AgentCore Memory delivery is implemented, off by default, and not live-qualified.
One workflow, five paths
These synthetic paths show what gets recorded and which checks can reject a write. They do not prove a release is safe.
A release report across three agents. One agent records a build, another tests that exact version, and a third reads the saved readiness result.
Each agent reads the exact State the previous one wrote.
Normal path trajectory. Each agent reads the exact State the previous one wrote. Readiness is current and points to build@1 and tests@1.
Outcome: Readiness is current and points to build@1 and tests@1.
Agent A resends the same build after a timeout.
Retry trajectory. Agent A resends the same build after a timeout. The same submission returns the original receipt. It adds no revision or repeated calculation in this example.
Outcome: The same submission returns the original receipt. It adds no revision or repeated calculation in this example.
The build result is corrected after tests already ran.
Correction trajectory. The build result is corrected after tests already ran. build@1 stays readable while retained; readiness is not current until tests target build@2.
Outcome: build@1 stays readable while retained; readiness is not current until tests target build@2.
A delayed worker tries to commit readiness from old inputs.
Stale worker trajectory. A delayed worker tries to commit readiness from old inputs. The required-version check rejects the old write and keeps the newer State.
Outcome: The required-version check rejects the old write and keeps the newer State.
The wakeup is lost while a worker restarts.
Restart trajectory. The wakeup is lost while a worker restarts. A saved work record lets the maintenance pass retry unfinished work in this example.
Outcome: A saved work record lets the maintenance pass retry unfinished work in this example.
An example. Each step shown is built in code; the scenario has not run on a live deployment.
One system, clear responsibilities
| Responsibility | Owner |
|---|---|
| Agent execution and tool orchestration | Your agents and application on AgentCore |
| Business data and source-of-truth updates | Your existing databases and services |
| Accepted History and exact revisions | Kam |
| Supported derived State and dependency reconciliation | Kam |
| Conversational recall and semantic retrieval | AgentCore Memory or a retrieval system |
| General-purpose analytics | Your warehouse or analytics platform |
For engineers
Which tool for which job
| Job | Kam | Your database | AgentCore Memory | Vector database | Warehouse |
|---|---|---|---|---|---|
| Read the exact version a decision usedKam: byIds resolves (id, revision) and reports missing or expired explicitly. | Built for this | Varies by system | Outside its role | Outside its role | Varies by system |
| Keep one fixed list across agent turnsKam: allIds pages one generation; a late write publishes a successor instead of shifting the page. | Built for this | Varies by system | Outside its role | Outside its role | Varies by system |
| Update the related State a change affectsKam: Views reconcile same-scope dependents; metrics and watch are planned. | Built for this | Varies by system | Outside its role | Outside its role | Varies by system |
| Keep business transactions and source-of-truth writesYour database stays authoritative for its records. | Outside its role | Built for this | Outside its role | Outside its role | Outside its role |
| Recall what was said in past conversationsAgentCore Memory owns recall; Kam can optionally publish to it. | Outside its role | Outside its role | Built for this | Varies by system | Outside its role |
| Find similar documents or passagesSimilarity search belongs in a vector store beside Kam. | Outside its role | Varies by system | Varies by system | Built for this | Outside its role |
| Run custom analytics across all your dataKam does not offer general SQL or arbitrary joins. | Outside its role | Varies by system | Outside its role | Outside its role | Built for this |
One State model, many questions
Each question on the right is answered by the blocks wired to it. Some belong to AgentCore or a model, and say so.
One State model, many questions. Eight primitives on the left; each concept on the right is answered by the primitives connected to it, or belongs to the runtime or a model.
| Concept | Question | Status | How |
|---|---|---|---|
| Calendar periods | What exact History belongs to this year, month, week, day, or saved date range? | Derivable from existing primitives | The frontend calendar builds normalized yearById, monthById, weekById, dayById, and customById selectors over supplied exact History. Ordered year, month and day children share one occurrence catalogue; structural dates have unknown source coverage. One displayed year can include 366 calendar dates without widening the 365-date read or custom-range limits. Browser presets save date preferences only; cross-page collection, scheduling, and Google Calendar synchronization are not implemented. |
| Recommended reviews | Which supplied changes and recorded readers match a declared review rule? | Derivable from existing primitives | A frontend review policy groups exact input-version differences, reported failed checks and unavailable lookups into bounded, inspectable review roots. Candidates preserve source coordinates, recorded paths, coverage and work limits. Calendar containment is separate from dependency reads. The authorized console does not supply exact dependency edges today; it cannot infer them from opaque source references. Recommendations do not certify importance, confidence, safety, or action eligibility, and do not execute work. |
| Calendar summaries and patch notes | What changed in this period, and which exact versions have recorded readers? | Derivable from existing primitives | A bounded frontend selector summarizes supplied occurrences, compares successive exact revisions of the same State identity, and searches recorded labels, values and reader references. A prior supplied revision may sit outside the chosen dates; its boundary remains visible. Patch notes show supplied before/after evidence and name recorded readers without implying that a newer revision was consumed. Summaries use deterministic counts and templates, not model inference. Missing pages, prior revisions and dependency evidence remain unknown. |
| Personal watchlist | What records do I want to follow, in my order? | Planned | An ordered reference collection with per-entry selectors. The public explorer has a temporary fixture preview; authorized, durable watchlist mutations are not implemented. |
| Since my last review | What changed, and why does my declared review rule flag it? | Derivable from existing primitives | The release-verification fixture View separates endpoint differences, retained activity, and a named domain rule. Explicit review actions acknowledge displayed exact boundaries in memory only; durable reviews and notifications are not implemented. |
| Saved calculation selection | Which supported calculation, inputs and period produced this result? | Planned | A definition selects a qualified domain calculator and pinned inputs; its result is versioned State displayed by Views. No new backend primitive or generic business calculator is claimed. |
| Operational memory | What work can a replacement agent recover? | Planned | History and obligations are retained; an explicitly opened local SQLite host can recover accepted records and pending projection work. Managed recovery of whole agent tasks remains planned; the explorer runs no agent. |
| Workflow coordination | Which parent-child work is eligible? | Planned | Ordered membership and explicit dependencies are separate. The explorer previews valid order; hosted customer workflow management is planned. |
| Computation reuse | What can be reused without mistaking stale input for a cache hit? | Planned | Local comparison reuse and bounded reads exist. General calculation caching needs explicit applicability and live measurement; fixture counts are not savings. |
| History | What exactly was recorded? | Implemented in source | allIds() names exact revision references; byIds() returns exactly those revisions. |
| Correction | What was revised, and what did it replace? | Implemented in source | A correction is the next revision; the earlier one stays readable while retained. |
| Snapshot | What did this collection look like when it was published? | Implemented in source | A generation fixes ordered membership; pages are read against it. |
| Difference | What changed between two publications? | Derivable from existing primitives | Compare exact membership from two generations. The SDK also has bounded diffRevisions over two declared selected-reference arrays; it does not establish a generic generation-diff endpoint or external source completeness. |
| Dependency | What relies on this information? | Implemented in source | Views register versioned dependencies; a reverse index finds dependents. |
| Invalidation | Which derived State must be recomputed after this change? | Implemented in source | Reconciliation pages through affected Views and recomputes only those. |
| Freshness | Is this current enough to act on? | Implemented in source | Active State reports current, stale, blocked or absent. Only current carries usable items; the application still decides whether to act. |
| Authority | Who may read this, in which scope? | Implemented in source | The service resolves the principal's workspaces; a tenant in a request is not permission. |
| Expiration | When does this evidence stop being usable? | Implemented in source | Reads report expired at the deadline, before storage cleanup. |
| Receipt | What work is still owed, and what was acknowledged? | Implemented in source | Delivery keeps one obligation per eligible generation and separate receipts. |
| Bounded query | Which current evidence matches, within declared work limits? | Implemented in source | explain() reports the query plan and fixed work limits; value() executes the query over one Active State’s evidence references. |
| Context budget | Which selected exact evidence fits this context budget? | Implemented in source | An ordered, versioned Context manifest selects exact captured evidence and full, descriptor or excluded representations. Assembly enforces item and byte limits; unavailable required evidence blocks a complete package. Automatic relevance ranking and provider-token budgeting remain planned. |
| Subscription | Which agents should wake when this changes? | Planned | watch() is planned; the internal event path is not a customer subscription. |
| Authorized history | What was this agent allowed to see yesterday? | Needs data Kam does not record | Access is checked at read time and is not itself recorded as History. |
| Decision | What should the agent do next? | AgentCore or your runtime | Your agents and application on AgentCore plan, decide, and call tools. Kam records the outcome and the exact State the application reported as input. |
| Confidence | How likely is this forecast to be right? | A model, not Kam | A model computes it; Kam can retain the output and its inputs as evidence. |
Delivery · built, off by default
A delivery record keeps unfinished work visible. A sent receipt and a verified match are different results.
Each arrow is a step the backend can take. Sent and verified are separate receipts.
Delivery state graph. Stages, the transitions between them, and the stop states each stage can reach.
AWAITING_PUBLICATIONWaiting to publishAn eligible generation has a durable delivery record. The publisher uses its authorized destination and stable request identity.
AWAITING_VERIFICATIONWrite acknowledgedSubmission is confirmed. An exact retrieval check is still required; this is not a claim that an agent has read it.
VERIFIEDExact record matchedThe read matched content, destination, metadata, and local-generation lineage at the verification time.
An uncertain response keeps the same stage and request identity and retries after a bounded delay. Retries are bounded, not unlimited.
REJECTEDThe publication was rejected. It remains visible in delivery status.
AUTHORITY_BLOCKEDLifecycle authority closed or the destination binding changed. Old work is not silently rebound.
RECONCILIATION_REQUIREDA mismatch or exhausted attempt budget needs review. The worker does not repair remote content.
SUPERSEDEDPolicy v2 only: a newer generation replaced a candidate that was never planned, dispatched or submitted. The replaced obligation is kept with the replacing generation. Submitted or uncertain work is never coalesced.
Inspect an example
Go deeper
One application. One operation.
Bring a correction or an uncertain save. Agree the exact readback, failure checks, scope, duration, and price before starting.