module.companyos

@lssm-tech/module.companyos

Thin CompanyOS execution composition over canonical @lssm-tech/lib.companyos-spec contracts and pure @lssm-tech/lib.companyos-runtime projections.

The module exposes typed adapter ports for agent, job, integration, human, dry-run, and manual-record dispatch lanes. It does not call providers, networks, queues, filesystems, apps, bundles, examples, integrations, or peer modules by default. Production execution must be supplied by caller-owned adapters. Host applications that persist CompanyOS state should consume the ./persistence schema contribution and bind its database.mutation.plan / database.mutation.execute intents to provider-database adapters outside this module.

Positioning

Long-term governance/runtime layer behind proofs like CompanyOS VoiceOps.

Public entrypoints

• @lssm-tech/module.companyos — root barrel
• @lssm-tech/module.companyos/executor — executor composition and adapter port types
• @lssm-tech/module.companyos/fake-adapters — deterministic fake adapters for tests and examples
• @lssm-tech/module.companyos/flagship-fixture — replayable proof from communication-style source evidence to CompanyOS execution outcome
• @lssm-tech/module.companyos/persistence — provider-free CompanyOS schema contribution and governed database mutation intents for host-bound persistence
• @lssm-tech/module.companyos/outcome-value-view — deterministic view model for outcome value reports, review queues, readiness, and top prompt/skill influences
• @lssm-tech/module.companyos/ui — reusable, data-prop-driven CompanyOS preview screens and deterministic view-model data
• @lssm-tech/module.companyos/ui/CompanyOsPreview — canonical React preview shell for starter kits and examples

Outcome value view

./outcome-value-view keeps module-level presentation data deterministic: it summarizes evidence-backed business value reports, review queue size, autonomy readiness, and top prompt/skill influence groups without providers, storage, network calls, or production action execution.

Safety

The executor preserves CompanyOS policy-gate verdicts. Approval-required, denied, and reserved-human-only plans return operator-facing results instead of dispatching. Successful dispatches are represented by typed execution dispatch and receipt contracts. Non-dry-run lanes (agent, job, integration, human, and manual_record) also require ExecutionDispatchAuthorization before any adapter is called; missing, mismatched, denied, expired, or revoked authorization returns a typed operator-facing result and leaves adapters untouched. Dry-run dispatch remains available for deterministic proof and preview flows without production authorization.

Flagship proof

companyOsFlagshipExecutionProof demonstrates a communication-style source thread becoming a CompanyOS work item, policy-gate request/decision, dry-run dispatch, execution receipt, and outcome receipt linked to objective, memory, and cadence projections.

Reusable UI boundary

./ui is an isolated product-surface subpath for deterministic CompanyOS previews. It may use React, @lssm-tech/lib.design-system, and lucide-react; executor/core entrypoints remain side-effect-free and provider-free. The UI data is local fixture/view-model data only and does not perform network calls, filesystem writes, provider dispatch, outbound sends, or production action execution.

Focused examples should treat this module UI as canonical reusable presentation and keep package-level UI exports as thin compatibility/adopter adapters.

import { CompanyOsPreview } from '@lssm-tech/module.companyos/ui';
import { CompanyOsScreen } from '@lssm-tech/module.companyos/ui/companyos.types';

export function Demo() {
  return <CompanyOsPreview initialScreen={CompanyOsScreen.WORK_GRAPH} />;
}

Domain-command persistence

./persistence models the CompanyOS execution-receipt write path without importing provider-database, Drizzle, Postgres, or credentials. The exported companyOsPersistenceSchemaContribution declares companyos.execution_receipts and companyos.domain_command_outbox; buildCompanyOsExecutionReceiptPersistenceIntent() emits managed/BYOK-compatible mutation envelopes whose durable write authority is companyos.command.execution-receipt.persist.

Feature Hub profile

./hub exposes the CompanyOS define/install entrypoints, provider-neutral store and authority ports, and the /company presentation view model. Compatibility aliases /companyos and /companyos/overview are declared by the manifest. The profile references the canonical CompanyOsSpecFeature and imports no peer module or managed bundle. Routes cover brain, graph, inbox, action review, routing, operating reviews, autonomy, governance, evidence, replay, health, knowledge, and improvement. Workflow, CommunicationOS, and Auth Admin are optional Hub dependencies; signed widget and workspace action extension points remain host-composed. The CommunicationOS dependency accepts the version 2 Hub manifest series used by the composed reference runtime.

Published browser conditions select the emitted browser artifacts alongside existing Node/Bun/type targets. Export keys and source behavior are preserved; this packaging metadata does not activate providers or grant execution authority.

Canonical portable composition declarations use narrow @lssm-tech/lib.contracts-spec-core leaves. The original package i18n factory and hydration stack are owned by @lssm-tech/lib.translation-runtime/contracts/i18n-factory; historical facade paths remain compatible. This import migration does not qualify providers or authorize host actions.