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
Compose multiple Hubs
Resolve dependencies, reject collisions, and start Hubs in deterministic dependency order.
Semantic identity
Route, capability, operation, workflow, and navigation IDs remain stable across hosts.
Fail closed
Duplicate IDs, unknown routes, unresolved refs, cycles, and missing required ports block installation.
Lifecycle
Start, readiness refresh, cancellation, compensation, and disposal are concurrency-safe.
Local code
Signed registries may advertise metadata, but executable definitions resolve only from a local allowlist.
Copy-ready example
const composition = await composeFeatureHubs({ context, definitions: allNineHubs, ports, registries });
await composition.start();
const route = composition.resolveRoute("company-os.brain.route");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
Install your first Hub
Declare explicit context and ports, install read-only, inspect readiness, then start effects intentionally.
Customize without forking authority
Replace presentation and infrastructure adapters while keeping operations, policy decisions, and state machines canonical.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.