Skip to main content
Harmonia separates agentic judgment from deterministic workflow authority. Models analyze, plan, write, review, compose bounded interfaces, and answer read-only questions. Application services own state transitions, approvals, external effects, receipts, and verification.

How Harmonia uses it

DynamoDB is the durable workflow authority. AgentCore Runtime sessions, AgentCore Memory facts, model output, telemetry, and external API responses cannot approve or authorize an effect.

Evidence status

Repository tests and local emulator runs establish contract behavior. A technology page labels authenticated cloud or provider evidence separately. Code presence, mock mode, or a deploy script is not proof that a managed service or external effect has run successfully.

Source map

  • src/ — Next.js UI, APIs, state, integrations, and telemetry
  • agent/harmonia_agent/ — Strands team, worker stages, media, memory, and provider clients
  • infra/ — AWS CDK and deployment wrappers
  • docs/ — operational contracts and evidence runbooks
Last modified on September 14, 2026