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
Composable feature Hubs
Install complete vertical features, import granular components, or combine both without surrendering contracts, policy, or infrastructure choices.
Turnkey
Install a complete headless runtime, semantic routes, navigation, readiness, and web/native descriptors.
Granular
Import individual ports, view-models, screens, and templates from module subpaths.
Hybrid
Install the Hub, then override presentation, copy, aliases, or adapter ports without redefining policy.
Independent
Modules never import peer modules; hosts compose optional dependencies through the shared protocol.
Copy-ready example
import { runFeatureHubCompositionExample } from "@lssm-tech/example.feature-hub-composition";
import { createIntegrationHubViewModel } from "@lssm-tech/module.integration-hub/hub/presentation";
// Turnkey: install all nine Hubs and project identical web/native semantics.
const proof = await runFeatureHubCompositionExample();
// Granular: use one reusable view-model without installing a complete Hub.
const integrationCard = createIntegrationHubViewModel([
"integration.activation.manage",
]);
// Hybrid is included in the runner: /settings/apps overrides the canonical
// Integration route presentation while policy and operations stay unchanged.
console.log(proof.hubKeys, proof.hybridAlias, integrationCard);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
Architecture
See how the spec layer, runtimes, integrations, and multi-surface outputs fit together.
Install your first Hub
Declare explicit context and ports, install read-only, inspect readiness, then start effects intentionally.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.