Skip to main content

Module Boundaries

This page explains where responsibilities live in the API.

Core module groups​

  • Identity/workspace: auth, users, workspaces, members
  • Agent/message flow: assistants, actions, conversations, messages, contacts
  • Integrations: connections, senders, ingress, webhooks, providers
  • Runtime/ops: queue, workers, policy, usage, telegram-app

Rule of thumb​

  • controllers/jobs coordinate flow
  • services/collaborators own business logic
  • adapters normalize provider behavior

Why this is important​

Keeping modules focused makes the system easier to maintain, test, and scale as more providers and agent capabilities are added.