Skip to content
ContractSpec
Start here
AI index

Domain docs

Organization Planning

Planning, profiles, owned booking links, and calendar-backed execution.

Source packages

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

  • packages/domains/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

  • Individual, team, workspace, and organization profiles

  • Hosted and embedded booking workflows

Implementation notes

  • Derive every protected owner scope server-side from current membership and grants.

  • Scheduling effects reprove persisted human approval, current policy, authority and lease before provider credentials are resolved; legacy queued commands require fresh authorization.

  • Keep public availability provider-neutral and free of private calendar identifiers.

  • Use the versioned loader or React 18/19 package for allowlisted booking embeds.

  • Capture intake uses private owner scope, explicit revocable consent, current policy, and encrypted resumable chunks; clients cannot declare processing complete.

  • CompanyOS exposes capture configuration and consent routes. Native device capture, transcription processing and deployment qualification remain separate release gates.