Skip to content
ContractSpec
Start here
AI index

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.

Cross-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.