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.

AI index

Domain docs

Organization Planning

Planning cycles, org context, priorities, and execution alignment.

Source packages

Start with packages/modules/organization-planning, then use the spec and runtime packages as compatibility boundaries.

  • packages/libs/organization-planning-spec

Platform stance

Define the domain once. Render web and mobile with platform-native shells after contract, role, tenant, and policy resolution.

Canonical surfaces

  • Planning contracts
  • Priority views
  • Execution review workflows

Implementation notes

  • Bind plans to explicit owners and review cadence.
  • Project planning views into web and mobile shells through shared DataViews.
OSS docsdomainsStart with OSS. Adopt Studio when you want the operating layer.

Why ContractSpec

Keep educational and comparison content reachable without letting it define the primary OSS learning path.