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
Workflow Hub
Install definitions, DAGs, schedules, approvals, workers, retries, leases, cancellation, dead letters, and replay.
Replaceable execution
Inject scheduler, worker, persistence, clock, policy, evidence, and observability ports.
Canonical policy
Workflow decisions use the shared Hub vocabulary and obligations.
Copy-ready example
import { installWorkflowHub } from "@lssm-tech/module.workflow-orchestration/hub";
const hub = await installWorkflowHub({
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
Agent Network Hub
Coordinate multiple systems through discovery, shared sessions, delegation, evidence, and signed federation.
Auth User Hub
Ship user-owned identity, authentication, recovery, MFA, passkeys, sessions, consent, and personal security.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.