# Company, work and service operations

Connect operating goals, shared work, planning, meetings and support through their canonical domain boundaries.

Source snapshot: bcc79fcc27c4d801c2119bef81ddcce7b4e86498

## Follow the owner of durable state

WorkRuntime is the shared owner for task/project reducers and persistence ports. It consumes immutable events, checks revision order, expands recurrence and resolves sync authority/conflicts. CompanyOS runtime uses Work references for operating reviews and graph projections. Keep that direction when adding a feature: a dashboard or assistant should reference the canonical task rather than maintaining a parallel mutable task copy. Concrete PostgreSQL, queue, realtime and connector behavior belongs to the selected integrations and host.

Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/work/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/company/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/organization-planning/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/customer-support/runtime/README.md

## Understand domain-specific handoffs

CompanyOS adds authority explanations, autonomy classification, operator inbox routing and evidence-backed outcome projections. OPA contributes profile and meeting-workspace behavior, while SupportOS contributes case lifecycle, routing and service operations. Support routing can evaluate candidate projections deterministically, but assignment remains a separate governed effect. Message bodies stay with CommunicationOS and form answers with Forms. A cross-domain handoff should therefore name the exact referenced work or operation and the evidence needed by its receiving owner.

Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/work/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/company/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/organization-planning/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/customer-support/runtime/README.md

## Inspect retries and active capabilities

Work outbox delivery uses leased, destination-specific records and fenced acknowledgements; current source requires the exact delivery attempt for settlement. OPA distinguishes its operation catalog, partial handler map and installed registry. Saving an automation policy does not itself activate background execution. These distinctions are useful product states, not implementation trivia: an operator needs to know whether a proposal exists, a handler is installed, delivery is pending or an external effect completed. Preserve that vocabulary in a composed product.

Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/work/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/company/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/organization-planning/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/customer-support/runtime/README.md

## Trace one work item

Open its contract and follow event reduction, revision checks, storage and the projection used by the UI. Compare a repeated command and a conflicting update using the owning runtime’s existing tests or fixtures.

Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/work/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/company/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/organization-planning/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/customer-support/runtime/README.md

## Follow one domain handoff

Choose a support-to-work or meeting-to-work path. Identify which domain owns the original record, which references cross the boundary and where authority is rechecked before the receiving action.

Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/work/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/company/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/organization-planning/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/customer-support/runtime/README.md

## Inspect the composed availability

Check the bundle’s installed modules, handlers, required ports and selected capabilities. Show proposals, queued actions and completed effects separately, then link an operator to the evidence or recovery path relevant to that exact state.

Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/work/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/company/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/organization-planning/runtime/README.md
Source: https://github.com/lssm-tech/contractspec/blob/bcc79fcc27c4d801c2119bef81ddcce7b4e86498/packages/domains/customer-support/runtime/README.md

## Packages

- [@lssm-tech/integration.company-intelligence-postgres](https://lssm.co/docs/packages/integration.company-intelligence-postgres/): Postgres persistence for Company Intelligence canonical records and the durable document evidence ledger.
- [@lssm-tech/integration.customer-support-postgres](https://lssm.co/docs/packages/integration.customer-support-postgres/): Managed and self-hosted PostgreSQL authority adapter for SupportOS.
- [@lssm-tech/integration.meeting-effect-worker-postgres-http](https://lssm.co/docs/packages/integration.meeting-effect-worker-postgres-http/): Production PostgreSQL, BYOK, authority, rollout, and HTTP delivery composition for the meeting effect worker.
- [@lssm-tech/integration.meeting-intake-worker-postgres-http](https://lssm.co/docs/packages/integration.meeting-intake-worker-postgres-http/): Production PostgreSQL queue and protected HTTP execution composition for the OPA meeting intake worker.
- [@lssm-tech/integration.opa-calendar-bridge](https://lssm.co/docs/packages/integration.opa-calendar-bridge/): Bridge adapting the real CalendarProvider (e.g. GoogleCalendarProvider from integration.provider-calendar) to the organization-planning module's CalendarExecutionAdapterPort. Port → provider; no new Google SDK code.
- [@lssm-tech/integration.opa-meeting-context-bridge](https://lssm.co/docs/packages/integration.opa-meeting-context-bridge/): Governed bridges from existing knowledge providers to OPA MeetingContextSourcePort.
- [@lssm-tech/integration.opa-notification-bridge](https://lssm.co/docs/packages/integration.opa-notification-bridge/): Bridge implementing the organization-planning CommunicationSendAdapterPort + JobsScheduleAdapterPort over injected email (EmailOutboundProvider), SMS (SmsProvider), and durable job-queue (JobQueue) transports. Feature-flag gated, fail-closed, no secrets in code.
- [@lssm-tech/integration.opa-personalization-bridge](https://lssm.co/docs/packages/integration.opa-personalization-bridge/): Bridge mapping the canonical @lssm-tech/lib.personalization surfaces (preference-dimensions, preference-evolution, behavior-signals, adaptive-surface) onto OPA optimizer objective weights, the behavior→preference learning loop, and role-aware booking/UI adaptation. No ad-hoc preference state.
- [@lssm-tech/integration.supportos-worker-managed](https://lssm.co/docs/packages/integration.supportos-worker-managed/): Managed PostgreSQL, AuthOS, evidence, and incident-alert composition for the SupportOS worker.
- [@lssm-tech/integration.work-durable-store](https://lssm.co/docs/packages/integration.work-durable-store/): PostgreSQL event, idempotency, projection, and outbox adapter for the canonical Work Graph.
- [@lssm-tech/module.company-metrics](https://lssm.co/docs/packages/module.company-metrics/): Governed CompanyOS metric definitions, deterministic aggregation, collection, alerts, digests, and publications.
- [@lssm-tech/module.executive-intelligence](https://lssm.co/docs/packages/module.executive-intelligence/): Shared leadership briefs, risks, commitments, and decision packets.
- [@lssm-tech/module.companyos](https://lssm.co/docs/packages/module.companyos/): CompanyOS execution composition module with typed adapter ports over CompanyOS spec/runtime contracts.
- [@lssm-tech/lib.companyos-runtime](https://lssm.co/docs/packages/lib.companyos-runtime/): Pure CompanyOS V0 runtime helpers for authority, autonomy, inbox routing, and operating review projections.
- [@lssm-tech/lib.companyos-spec](https://lssm.co/docs/packages/lib.companyos-spec/): Contract-first CompanyOS V0/V1 specifications for bounded company operations.
- [@lssm-tech/lib.customer-support-conformance](https://lssm.co/docs/packages/lib.customer-support-conformance/): Portable behavioral conformance harness for managed and self-hosted SupportOS authorities.
- [@lssm-tech/module.customer-support](https://lssm.co/docs/packages/module.customer-support/): Reusable SupportOS inbox, AI canvas, messenger, host, and agent surfaces.
- [@lssm-tech/lib.customer-support-runtime](https://lssm.co/docs/packages/lib.customer-support-runtime/): Provider-neutral SupportOS case authority, SLA, autonomy, and ecosystem bridge runtime.
- [@lssm-tech/lib.customer-support-spec](https://lssm.co/docs/packages/lib.customer-support-spec/): Provider-neutral SupportOS customer-support contract definitions: case, authority, operation, event, schema and feature specs extracted unchanged from ContractSpec compatibility.
- [@lssm-tech/lib.support-bot](https://lssm.co/docs/packages/lib.support-bot/): AI support bot framework with RAG and ticket management
- [@lssm-tech/lib.supportos-worker-runtime](https://lssm.co/docs/packages/lib.supportos-worker-runtime/): Provider-free fenced job execution and handler composition for the SupportOS worker.
- [@lssm-tech/module.organization-planning](https://lssm.co/docs/packages/module.organization-planning/): Organization planning composition module with typed adapter ports for cross-module integration.
- [@lssm-tech/opa-booking-react](https://lssm.co/docs/packages/opa-booking-react/): Hosted and headless React integration for OPA booking links.
- [@lssm-tech/lib.organization-planning-react](https://lssm.co/docs/packages/lib.organization-planning-react/): Headless React clients for governed Organization Planning workspaces.
- [@lssm-tech/lib.organization-planning-runtime](https://lssm.co/docs/packages/lib.organization-planning-runtime/): Organization Planning & Agenda (OPA) execution runtime: wires the organization-planning module's adapter ports to real adapters while preserving fail-closed approval gates. Provider SDKs stay in integrations/.
- [@lssm-tech/lib.organization-planning-spec](https://lssm.co/docs/packages/lib.organization-planning-spec/): Provider-neutral organization, planning, agenda, booking, and auto-scheduling contracts for autonomous-company operations.
- [@lssm-tech/module.work-management](https://lssm.co/docs/packages/module.work-management/): Reusable Work OS application services and web/native view models.
- [@lssm-tech/lib.work-runtime](https://lssm.co/docs/packages/lib.work-runtime/): Pure Work Graph reducers, event processing, recurrence, idempotency, and sync conflict decisions.
- [@lssm-tech/lib.work-spec](https://lssm.co/docs/packages/lib.work-spec/): Canonical provider-neutral Work Graph contracts for CompanyOS and modular Work OS consumers.
- [@lssm-tech/app.meeting-effect-worker](https://lssm.co/docs/packages/app.meeting-effect-worker/): Inspect the package guide, declared imports and source relationships.
- [@lssm-tech/app.meeting-intake-worker](https://lssm.co/docs/packages/app.meeting-intake-worker/): Inspect the package guide, declared imports and source relationships.
- [@lssm-tech/app.organization-planning-host](https://lssm.co/docs/packages/app.organization-planning-host/): Thin OPA host: mounts the organization-planning operation registry on REST, GraphQL, and MCP surfaces via the shared contracts-runtime adapters.
- [@lssm-tech/app.supportos-api](https://lssm.co/docs/packages/app.supportos-api/): Inspect the package guide, declared imports and source relationships.
- [@lssm-tech/app.supportos-desktop](https://lssm.co/docs/packages/app.supportos-desktop/): Tauri 2 standalone desktop shell for SupportOS.
- [@lssm-tech/app.supportos-web](https://lssm.co/docs/packages/app.supportos-web/): Standalone SupportOS web and PWA operator product.
- [@lssm-tech/app.supportos-worker](https://lssm.co/docs/packages/app.supportos-worker/): Inspect the package guide, declared imports and source relationships.