# How the event-driven paths fit together

Follow the separate acceptance, calculation, exact-read and optional Memory-delivery paths beside AgentCore execution.

Status: Implemented in source. Prelaunch; not a live service guarantee.

Reviewed: 2026-10-14.
Backend source: e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
Native toolkit: merged in PR #176, reviewed at e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
HTML: /docs/event-driven-memory

## In short

AgentCore runs the agent while Kam accepts recorded results, updates derived State and serves exact History. Optional delivery to Memory is another path with its own evidence. Processing progress and delivery receipts must be inspected separately from execution.

**Available today:** These State and History paths are source implemented. AgentCore Memory delivery is optional, off by default and locally simulated.

> Separate AgentCore execution, State processing and optional Memory delivery.

## Follow each owner across the handoff

- **Execute in AgentCore** — The runtime hosts the agent; your application controls decisions and tools.
- **Maintain State in Kam** — Accept results, reconcile supported Views and serve exact evidence.
- **Deliver only when configured** — Optional Memory delivery has its own receipts and is off by default.

## DynamoDB owns the accepted history

Acceptance commits immutable revisions, day membership, and durable work together. A separate publication transaction commits the checkpoint, trajectory generation, and eligible delivery obligation. These are two transactions at different stages, not a transaction across AWS services.

[Read the write path](/docs/engineering-review#write-path)

## Rust computes supported rolling views

The worker takes saved state, accepted transitions, and an explicit time input. It performs no AWS or model I/O. last10 compares two disjoint groups of ten; utc30 and utc90 compare disjoint calendar windows and include today’s partial UTC day.

Rates use summed success and failure counts. An empty denominator is null. Deltas are percentage points. These are descriptive comparisons, not significance tests or evidence of causation.

[Inspect a chart and its source records](/?capability=workflows#trajectory)

## Queues wake workers; durable records own the work

Bounded queue jobs and the scheduled maintenance sweep resume pending work and advance quiet histories. A delivery generation is not forgotten when enqueue fails; its durable obligation can be rediscovered after the scheduling lease.

The delivery scheduler rotates across registered scopes. Automatic recovery has explicit attempt limits and stop states; it does not imply automatic repair of every failure.

## Keep archive proposals separate

Accepted History is in DynamoDB. A source reference is not an archived copy or an atomic acceptance receipt. Automatic S3 archival and carry-forward consolidation are not implemented.