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
Mount Hubs on web and React Native
Project the same semantic routes, capability gates, operations, states, and workflows into different host navigation systems.
Next.js
Map semantic IDs to paths plus fresh-session, cache, and security metadata.
React Native
Map the same IDs to screens, tab/stack hierarchy, icons, and gesture hints.
Parity
Workflow semantics are equal; visual and component identity may be platform-specific.
Unsupported
Mark a route degraded or blocked instead of silently omitting it.
Copy-ready example
const web = [...composition.installations.values()].flatMap((installation) =>
createNextFeatureHubRouteRegistry(installation),
);
const native = [...composition.installations.values()].flatMap((installation) =>
createReactNativeFeatureHubRouteRegistry(installation),
);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
Security and production readiness
Separate candidate templates from consumer-qualified deployments and preserve local authority for every effect.
Integration Hub
Catalog, connect, configure, sync, secure, and audit managed or BYOK integrations.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.