OSS-first docs
These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.
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.
packages/modules/auth-os
BillingOS
Plans, subscriptions, invoices, payments, entitlements, and financial evidence across web and mobile.
packages/modules/billing-os
CompanyOS
Company workspace, operating graph, teams, objectives, and decision records.
packages/modules/companyos
CommunicationOS
Messages, channels, outbound-send gates, inboxes, and provider transport bindings.
packages/modules/communication-os
Organization Planning
Planning cycles, org context, priorities, and execution alignment.
packages/modules/organization-planning
Context Storage
Durable context, memory, provenance, and retrieval boundaries for agents and apps.
packages/modules/context-storage
Lifecycle
Delivery loops, review evidence, release readiness, and managed lifecycle guidance.
packages/modules/lifecycle-core
Notifications
Notification preferences, delivery channels, unread state, and escalation rules.
packages/modules/notifications
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.
Architecture
See how the spec layer, runtimes, integrations, and multi-surface outputs fit together.
AuthOS
Implement identity, roles, permissions, sessions, and tenant-safe access decisions as a reusable domain.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.