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
CommunicationOS Hub
Operate inboxes, threads, channel identities, consent, triage, drafts, handoffs, escalation, audit, and replay.
Injected channels
Email, SMS, Slack, Telegram, voice, and custom providers remain adapters.
No fabricated authority
Communication evidence may propose CompanyOS work but cannot authorize it.
Copy-ready example
import { installCommunicationOsHub } from "@lssm-tech/module.communication-os/hub";
const hub = await installCommunicationOsHub({
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
Auth Admin Hub
Manage organizations, roles, invitations, SSO, SCIM, domains, posture, and tenant audit.
CompanyOS Hub
Install the independent company brain, operating inbox, work routing, governance, evidence, replay, knowledge, and improvement surface.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.