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
CompanyOS
Company workspace, operating graph, teams, objectives, and decision records.
Source packages
Start with packages/modules/companyos, then use the spec and runtime packages as compatibility boundaries.
packages/libs/companyos-spec
packages/libs/companyos-runtime
Platform stance
Define the domain once. Render web and mobile with platform-native shells after contract, role, tenant, and policy resolution.
Canonical surfaces
Workspace model
Company graph
Operating cockpit views
Implementation notes
Keep company-level records separate from auth identity.
Use explicit graph and runtime contracts before composing dashboards.
The first Managed CompanyOS activation is a private production-scoped pilot for one approved tenant/workspace and one governed readiness → expert attestation → founder approval → evidence/replay journey; GA, mobile, VPS worker, providers, outbound dispatch, and SLA/compliance claims remain deferred until separately approved.
GrowthOS
Implement referral and affiliate acquisition, attribution, rewards, balances, and payouts as a reusable domain.
CommunicationOS
Implement messages, channels, outbound-send gates, inboxes, and provider transport bindings.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.