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
Customize without forking authority
Replace presentation and infrastructure adapters while keeping operations, policy decisions, and state machines canonical.
Components
Swap a screen or layout through a semantic route override.
Copy
Override tenant copy and translation inputs without changing operation behavior.
Aliases
Mount Hub route IDs under a host base path and preserve legacy URLs.
Ports
Use Vercel, Railway, Supabase, Docker, or custom providers behind the same contracts.
Copy-ready example
overrides: [{
hubKey: "integration",
routeId: "integration.connections",
alias: "/settings/apps",
componentKey: "acme.integration.connections",
}]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
Compose multiple Hubs
Resolve dependencies, reject collisions, and start Hubs in deterministic dependency order.
Security and production readiness
Separate candidate templates from consumer-qualified deployments and preserve local authority for every effect.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.