How the event-driven paths fit together
Persist the work before relying on a wakeup.
Guide context
Acceptance, rolling calculation, exact reads, and AgentCore delivery have separate responsibilities.
Accepting a record, calculating rolling comparisons, reading exact history, and delivering to AgentCore are four separate paths. Each saves its own progress, so a lost wakeup delays work instead of losing it.
On this page · 4 sections
Who owns each handoff?
Acceptance
Kam retains admitted outcome revisions.
Projection
Kam maintains bounded State and dependencies.
Serving
AgentCore owns recall; the application uses the returned evidence.
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.
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.
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.