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.