Domain operating systems
Implement product domains from one contract layer
AuthOS, BillingOS, CompanyOS, CommunicationOS, and the adjacent operating domains are reusable system slices. Each one should define contracts once, then project them into web, mobile, integrations, workflows, and evidence trails.
AuthOS
Identity, roles, permissions, sessions, and tenant-safe access decisions, with one session authority and consistent multi-surface enforcement.packages/domains/identity/moduleGrowthOS
Referral and affiliate acquisition, deterministic attribution, governed rewards, balances, and provider-neutral payouts.packages/domains/growth/moduleBillingOS
Plans, subscriptions, invoices, payments, entitlements, and financial evidence across web and mobile, with a France-ready quote-to-cash issuance path.packages/domains/billing/moduleCompanyOS
Company workspace, operating graph, teams, objectives, and decision records.packages/domains/company/moduleCommunicationOS
Messages, channels, outbound-send gates, inboxes, and provider transport bindings.packages/domains/communication/moduleSupportOS
AI-native customer operations, live support, deterministic decision graphs, and evidence-bound living SOPs.packages/domains/customer-support/moduleOrganization Planning
Planning, profiles, owned booking links, and calendar-backed execution.packages/domains/organization-planning/moduleContext Storage
Durable context, memory, provenance, and retrieval boundaries for agents and apps.packages/platform/agents/context-storage-moduleLifecycle
Delivery loops, review evidence, release readiness, and managed lifecycle guidance.packages/platform/delivery/lifecycle-coreNotifications
Notification preferences, delivery channels, unread state, and escalation rules.packages/domains/communication/notificationsCross-platform rule
A domain is compatible with web and mobile when its contracts can be resolved into both shells without duplicating business logic. Mobile should receive compact, resumable, gesture-aware surfaces rather than a reduced afterthought.
Domain contracts own intent, policy, data shape, and generated surface expectations.
Web and mobile shells own platform routing, gestures, transitions, and native affordances.
Provider-specific behavior stays in integrations instead of leaking into domain pages.
Every domain page should link back to source packages so users can move from docs to code.