Skip to main content
Harmonia has four distinct continuity layers. They are intentionally not interchangeable.

Invocation state

Short-lived typed handoffs inside one managed cognition call.

Chat history

Bounded continuity for one authenticated operator and interface.

DynamoDB

Authoritative durable workflow, approval, effect, cost, and failure state.

AgentCore Memory

Evidence-linked decisions and verified outcomes that may inform later jobs.

​
Ownership matrix

​
Conversation retention

When a scoped conversation exceeds 300 retained messages, Harmonia prunes old turns and stores only metadata boundaries: counts, time range, and linked durable IDs. Summaries do not retain transcripts, drafts, approvals, credentials, or generated claims. Dashboard and Telegram histories never merge because the interface is part of the scope key.

​
Memory eligibility

AgentCore Memory writes accept only typed candidates linked to durable DynamoDB evidence.
  • explicit operator decisions;
  • verified publishing outcomes;
  • measured engagement takeaways with durable record IDs; and
  • workspace-and-brand-scoped preferences supported by evidence.
Retrieval is bounded to five facts and formatted within a fixed character budget. A cross-scope or malformed result fails visibly instead of entering a model prompt.
DynamoDB remains the recovery source after a crash or SQS redelivery. AgentCore Memory improves later judgment; it cannot reconstruct or overwrite workflow truth.
The scope, eligibility, and failure contracts below are verified offline. Do not claim live cross-job memory until a real AgentCore Runtime write, a later same-scope retrieval, and a different-scope negative retrieval have been captured from the authenticated deployment.
Each cognitive operation derives a stable, non-content-bearing AgentCore Runtime session ID. A restarted worker retrieves that exact session before continuing; concurrent creators converge on the same ID. The caller payload is copied only when the session is first created, and retrieved session objects are never mutated in process. This preserves managed event continuity for a single operation without allowing session state to authorize, replay, or advance the DynamoDB workflow. Durable stage leases still decide whether a crashed operation may continue or must be quarantined as uncertain. See the exhaustive state ownership and retention matrix. For the complete optimisation strategy—deterministic projections, prune + spill, artifact retrieval, operation fencing, and crash-boundary measurements—see Context and memory continuity.
Last modified on September 14, 2026