Core Concepts

A case is the attention surface for a unit of work Atlas is tracking: a quote follow-up, delayed purchase order, customer request, approval, or exception.

Atlas can perform safe reads autonomously, but risky writes and external communications route through configured approval gates.

• Low-risk actions can proceed under policy.
• Medium-risk actions can request operator confirmation.
• High-risk or destructive actions require explicit approval.

An integration is not just a credential. Atlas treats each connection as a source of operational evidence with a known identity, permission boundary, and set of supported actions.

• Email integrations provide event signals and conversation evidence.
• ERP integrations provide structured state, identifiers, and write targets.
• Schema discovery maps ERP-native objects into Atlas concepts such as customers, quotes, purchase orders, pickings, and invoices.
• Approval policy decides whether Atlas can act directly, request approval, or escalate.

1. 1

   Observe only

   Atlas reads email and ERP state, classifies events, and records what it would do.

2. 2

   Approve every action

   Operators review drafts, ERP write proposals, and routing decisions before anything external changes.

3. 3

   Allow bounded autonomy

   Low-risk actions can proceed automatically while risky actions remain approval-gated.