How the Kami fleet works

An owner-directed network of specialist AI agents

How the Kami fleet works An owner-directed network of specialist AI agents Owner · Sets intent, approves · Architecture component Owner Sets intent, approves Chat channels · Messaging apps · Architecture component Chat channels Messaging apps Agent gateway · Auth, routing, sessions · Architecture component Agent gateway Auth, routing, sessions Kami · Orchestrator · Architecture component Kami Orchestrator Shared memory · Durable context · Architecture component Shared memory Durable context Scheduler · Cron and heartbeats · Architecture component Scheduler Cron and heartbeats Alerting · Health and failures · Architecture component Alerting Health and failures Viper · Engineering · Specialist agent fleet Viper Engineering Greedy · Revenue research · Specialist agent fleet Greedy Revenue research Raju · Social messaging · Specialist agent fleet Raju Social messaging Atlas · Inventory product · Specialist agent fleet Atlas Inventory product Mira · Customer support · Specialist agent fleet Mira Customer support Sterling · Bookkeeping · Specialist agent fleet Sterling Bookkeeping Pips · Trade journal · Specialist agent fleet Pips Trade journal Public website · Marketing and docs · Systems of record Public website Marketing and docs Fulfilment ops · 3PL and ecommerce · Systems of record Fulfilment ops 3PL and ecommerce PriceWatch · Price tracking app · Systems of record PriceWatch Price tracking app Market feed · Charts and signals · Systems of record Market feed Charts and signals Trading host · Execution terminal · Systems of record Trading host Execution terminal instructions inbound routed task ships builds leads quotes fills context timers health Specialist agent fleet Systems of record

One owner, many hands

  • • The owner states intent, never micromanages steps
  • • Kami holds context and routes the work

Specialists, not clones

  • • Each agent owns one domain end to end
  • • Escalation and approvals stay with the owner