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
Integration Hub
Catalog, connect, configure, sync, secure, and audit managed or BYOK integrations.
Catalog vs connection
Availability and tenant activation are separate states.
Secrets
Runtime and evidence expose credential references only.
Copy-ready example
import { installIntegrationHub } from "@lssm-tech/module.integration-hub/hub";
const hub = await installIntegrationHub({
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
Mount Hubs on web and React Native
Project the same semantic routes, capability gates, operations, states, and workflows into different host navigation systems.
Agent System Hub
Operate one tenant-local agent system, whether it contains one agent or many.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.