Choose a canonical owner for each layer
Reusable modules own their domain feature behavior and surfaces. Bundles compose approved modules and libraries for a product. Apps bind that composition to routes, authenticated requests, providers and deployment. The managed CompanyOS bundle illustrates this split: it consumes module-owned Integration, Auth, Agent, Workflow, CommunicationOS and CompanyOS hubs while keeping product route aliases. Keep modules canonical when adding another product so a new app does not require copying their implementation or making a lower layer import an app.
Supply the product’s real dependencies
The managed bundle keeps provider SDKs, raw credentials, databases, schedulers and topology with the host. Its public composition surfaces use redacted references and explicit ownership modes. A product’s usable capability therefore depends on the selected modules, installed handlers, ports, authority and configuration together. Document those requirements per workflow and deployment. LSSM OS names the integrated product relationship; CompanyOS remains a specific domain and composition name where the source uses it.
Measure the selected product experience
The bundle’s experience-coverage surface provides a governed journey manifest and product-health projection. Its README describes explicit productIds filtering that recomputes the denominator for the selected product set and rejects empty/unknown scopes. Status comes from evidence gates; a route or fixture rendering alone does not count as implementation. Use this existing product-oriented evidence alongside package reference docs. An administrator needs to know which journey is available in their composition and what blocks it, not merely how many source packages exist.
Follow a practical path.
Trace one visitor or operator journey
Start at a real route and follow its bundle, canonical module, operation/handler and concrete ports. Identify where the host constructs trusted subject/workspace scope and which feature flags apply.
Inspect composition availability
Read the installed capability/handler and experience-coverage information for the selected product. Distinguish preview data, an inactive background loop, a pending provider connection and a ready live workflow.
Reuse a module in another host
Choose the public module or bundle entry, supply its documented dependencies and keep product-specific routing and copy in the host. Qualify that new composition independently and link users to its deployment-specific setup and recovery guidance.