Skip to content
ContractSpec
Start here
AI index

Domain docs

SupportOS

AI-native customer operations, live support, deterministic decision graphs, and evidence-bound living SOPs.

Source packages

Start with packages/domains/customer-support/module, then use the spec and runtime packages as compatibility boundaries.

  • packages/platform/delivery/contracts-spec-compat/src/customer-support

  • packages/domains/customer-support/runtime

  • packages/platform/governance/decision-runtime

  • packages/platform/governance/sop-runtime

  • packages/integrations/customer-support-postgres

  • packages/integrations/provider-customer-support

Platform stance

Define the domain once. Render web and mobile with platform-native shells after contract, role, tenant, and policy resolution.

Canonical surfaces

  • Cases, queues, assignment, SLA, CSAT, portal, messenger, and help center

  • Deterministic decision graphs shared by Forms, Workflows, and SOPs

  • Generated, simulated, qualified, revision-pinned living SOPs

  • Intercom shadow, reconciliation, dual-write, cutover, and rollback

  • Graduated AI autonomy with consent, citations, hard budgets, and Connect policy

  • Web, PWA, mobile, desktop, embed, native SDK, and governed MCP surfaces

Implementation notes

  • SupportOS owns cases and service operations; CommunicationOS owns messages, channels, attachments, identities, consent, and delivery.

  • Use DecisionGraph only for pure branching and replay. Compile executable SOPs into WorkflowSpec so Workflow remains the effects, retry, approval, and compensation owner.

  • Derive tenant/workspace/actor authority from authenticated server context, enforce forced PostgreSQL RLS, and retain message bodies only in CommunicationOS.

  • Begin at L1 copilot. Promote only qualified SOP/locale/channel scopes with Connect evidence, tested rollback, and hard token/cost/time/tool budgets.

  • Keep Intercom authoritative until a signed cutover; webhooks are reconciled against cursor backfills and fixed watermarks.