Area guide · 26 packages · Trace an operating proposal into Work
Company, work and service operations
Connect operating goals, shared work, planning, meetings and support through their canonical domain boundaries.
What are you trying to do?
- Which package owns tasks and project state?
- How do CompanyOS projections use shared work?
- How can support and meeting workflows hand off work without copying another domain?
Why start with these packages
Suggested entry point
@lssm-tech/lib.work-runtimeStart with immutable Work events, recurrence, sync conflict handling and durable-store ports.
Suggested entry point
@lssm-tech/lib.companyos-runtimeUse CompanyOS authority, operating-loop, graph and outcome projections over shared references.
Suggested entry point
@lssm-tech/lib.organization-planning-runtimeInspect OPA planning/meeting services and their current authority and consent boundaries.
Suggested entry point
@lssm-tech/lib.customer-support-runtimeInspect SupportOS lifecycle, case concurrency, routing and reference-based ecosystem handoffs.
Practical steps
Step 01
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.
Step 02
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.
Step 03
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.
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.
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.
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.
Follow a practical path.
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.
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.
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.
Packages in this area (26)
26 of 26 shown
- Open manual →
Postgres persistence for Company Intelligence canonical records and the durable document evidence ledger.
- Open manual →
Managed and self-hosted PostgreSQL authority adapter for SupportOS.
- Open manual →
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.
- Open manual →
Governed bridges from existing knowledge providers to OPA MeetingContextSourcePort.
- Open manual →
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.
- Open manual →
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.
- Open manual →
PostgreSQL event, idempotency, projection, and outbox adapter for the canonical Work Graph.
- Open manual →
Pure CompanyOS V0 runtime helpers for authority, autonomy, inbox routing, and operating review projections.
Use CompanyOS authority, operating-loop, graph and outcome projections over shared references.
- Open manual →
Contract-first CompanyOS V0/V1 specifications for bounded company operations.
- Open manual →
Portable behavioral conformance harness for managed and self-hosted SupportOS authorities.
- Open manual →
Provider-neutral SupportOS case authority, SLA, autonomy, and ecosystem bridge runtime.
Inspect SupportOS lifecycle, case concurrency, routing and reference-based ecosystem handoffs.
- Open manual →
Provider-neutral SupportOS customer-support contract definitions: case, authority, operation, event, schema and feature specs extracted unchanged from ContractSpec compatibility.
- Open manual →
Headless React clients for governed Organization Planning workspaces.
- Open manual →
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/.
Inspect OPA planning/meeting services and their current authority and consent boundaries.
- Open manual →
Provider-neutral organization, planning, agenda, booking, and auto-scheduling contracts for autonomous-company operations.
- Open manual →
AI support bot framework with RAG and ticket management
- Open manual →
Provider-free fenced job execution and handler composition for the SupportOS worker.
- Open manual →
Pure Work Graph reducers, event processing, recurrence, idempotency, and sync conflict decisions.
Start with immutable Work events, recurrence, sync conflict handling and durable-store ports.
- Open manual →
Canonical provider-neutral Work Graph contracts for CompanyOS and modular Work OS consumers.
- Open manual →
Governed CompanyOS metric definitions, deterministic aggregation, collection, alerts, digests, and publications.
- Open manual →
CompanyOS execution composition module with typed adapter ports over CompanyOS spec/runtime contracts.
- Open manual →
Reusable SupportOS inbox, AI canvas, messenger, host, and agent surfaces.
- Open manual →
Shared leadership briefs, risks, commitments, and decision packets.
- Open manual →
Organization planning composition module with typed adapter ports for cross-module integration.
- Open manual →
Reusable Work OS application services and web/native view models.
- Open manual →
Hosted and headless React integration for OPA booking links.
Curated but no longer in the workspace: app.meeting-effect-worker, app.meeting-intake-worker, app.organization-planning-host, app.supportos-api, app.supportos-desktop, app.supportos-web, app.supportos-worker, integration.meeting-effect-worker-postgres-http, integration.meeting-intake-worker-postgres-http, integration.supportos-worker-managed
What connects to this area
Core contracts
Each domain declares the operation and event identity it owns.
Identity and access
Work and service operations are scoped to the current subject and workspace.
Communication and notifications
Communication owns message bodies and delivery used by these workflows.
Forms and data
Forms owns submitted answers and verification evidence.