# CompanyOS + CommunicationOS Operating Cockpit

Deterministic combined example that turns CommunicationOS thread/action evidence into a CompanyOS work execution plan, runs it through policy-gated dry-run execution, and feeds the result back into a CommunicationOS audit/action state.

## Boundaries

- Provider-free by default: no network I/O, credentials, outbound messages, deployments, or production actions.
- Imports reusable modules/libs only; it does not import other examples.
- Package-local `src/contracts` describe proof fixtures for this example, not canonical reusable cross-OS contracts.
- CompanyOS execution uses deterministic module adapters from `@lssm-tech/module.companyos`.
- Message-originated commands enter the CommunicationOS command inbox as evidence only; production sends and CompanyOS high-impact bypass attempts are blocked before execution.


## Rich cockpit proof

- The UI exports an app-like `TemplateShell` cockpit from `@lssm-tech/lib.example-shared-ui/TemplateShell` with ten named screens: home, dashboard, CommunicationOS inbox, thread detail, evidence map, CompanyOS work graph, policy gate, dry-run console, audit feedback, and starter-kit guide.
- The start/home and dashboard screens introduce the cross-OS story, deterministic safety boundaries, metrics, production-readiness checks, command lanes, operator notes, and quick actions before the deeper workflow screens.
- Sidebar navigation, thread selection, evidence drill-down, workflow-stage inspection, policy approval, dry-run execution, audit viewing, operator notes, and reset are backed by a pure reducer so the preview is interactive without providers or side effects.
- Selecting a CommunicationOS thread advances deterministic state into CompanyOS work mapping; running the dry-run advances the proof into CommunicationOS audit feedback without outbound effects.
- Reusable starter-kit proof imports CompanyOS and CommunicationOS UI/runtime surfaces from `@lssm-tech/module.companyos` and `@lssm-tech/module.communication-os`; scenario copy and fixtures remain package-local.
- The proof summary includes `commandInboxStatus: blocked` and `companyOsBridgeStatus: blocked` so release evidence catches any accidental execution bypass.

## Commands

```bash
bun run --cwd packages/examples/companyos-communicationos-operating-cockpit test
bun run --cwd packages/examples/companyos-communicationos-operating-cockpit typecheck
bun run --cwd packages/examples/companyos-communicationos-operating-cockpit build
bun run --cwd packages/examples/companyos-communicationos-operating-cockpit lint:check
bun run --cwd packages/modules/examples generate:registry
bun test packages/bundles/marketing/src/components/templates/template-catalog.test.ts packages/bundles/marketing/src/components/templates/template-preview.test.ts
```