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 docs
CommunicationOS
Messages, channels, outbound-send gates, inboxes, and provider transport bindings.
Source packages
Start with packages/modules/communication-os, then use the spec and runtime packages as compatibility boundaries.
- packages/libs/communication-spec
- packages/libs/communication-runtime
Platform stance
Define the domain once. Render web and mobile with platform-native shells after contract, role, tenant, and policy resolution.
Canonical surfaces
- Message contracts
- Provider channel bindings
- Outbound policy gates
Implementation notes
- Normalize provider transport before exposing app actions.
- Gate outbound sends with policy and audit evidence.
CompanyOS
Implement company workspace, operating graph, teams, objectives, and decision records as a reusable domain.
Organization Planning
Implement planning cycles, org context, priorities, and execution alignment with explicit contracts.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.