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
Security and production readiness
Separate candidate templates from consumer-qualified deployments and preserve local authority for every effect.
Policy
Use allow, deny, or require_approval plus enforceable redaction/session/re-evaluation obligations.
Readiness
Required ports block; optional ports degrade only their dependent capabilities and schedules.
Evidence
Record bounded lifecycle, policy, federation, publication, reconciliation, and replay evidence.
Qualification
Qualified requires live provider, security, restore, failover, canary, rollback, and operator evidence.
Copy-ready example
const report = await composition.refreshReadiness();
if (report.state !== "ready") throw new Error("Candidate is not live-qualified");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
Customize without forking authority
Replace presentation and infrastructure adapters while keeping operations, policy decisions, and state machines canonical.
Mount Hubs on web and React Native
Project the same semantic routes, capability gates, operations, states, and workflows into different host navigation systems.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.