OSS-first docs
These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.
Feature Hubs
CompanyOS Hub
Install the independent company brain, operating inbox, work routing, governance, evidence, replay, knowledge, and improvement surface.
Standalone
CompanyOS operates without companion Hubs and declares optional dependencies in its manifest.
Vertical slots
Hosts add domain records, routes, actions, and dashboards through extension slots.
Copy-ready example
import { installCompanyOsHub } from "@lssm-tech/module.companyos/hub";
const hub = await installCompanyOsHub({
context,
ports: yourProviderNeutralPorts,
evaluatePolicy: (policyId, operationRef) =>
policyEngine.evaluate({ policyId, operationRef, context }),
fulfillPolicyObligations: (request) => obligationRuntime.fulfill(request),
});
await hub.start();Production truth
Deterministic fixtures, adapters, and provider templates remain candidate. Qualified means the consumer has passed live provider, infrastructure, security, restore, failover, canary, rollback, and operator qualification in the exact environment.
Continue through the Hub ecosystem
Related package reference
Runnable all-nine reference app
CommunicationOS Hub
Operate inboxes, threads, channel identities, consent, triage, drafts, handoffs, escalation, audit, and replay.
Social Media Hub
Plan, approve, schedule, publish, reconcile, and analyze content across Instagram, LinkedIn, TikTok, X, and YouTube.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.