Start with OSS when you need:
- explicit contracts and generated surfaces you still own
- incremental adoption inside an existing codebase
- runtime governance, integrations, and safe regeneration without a managed operating product
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.
Studio bridge
Studio is the operating layer built on top of OSS ContractSpec.
Start with the open system first: contracts, generated surfaces, runtimes, integrations, and safe regeneration. Move to Studio when a team wants the product-facing workflow, decision loop, and managed operator surface on top of that foundation.
What stays opencontracts, code, generated surfaces
Studio is additive. It does not replace the OSS source of truth or ask teams to abandon their contract layer.
Adopt Studio when you need:
- decision workflows that turn product evidence into proposed spec changes
- governed execution loops and task packs on top of the OSS contract layer
- operator surfaces for teams that need a managed workflow instead of raw building blocks
- deeper product-facing workflows that sit above the open system without replacing it
Go to the Studio product docs for the full product surface
The OSS site keeps this section intentionally short. Deep Studio product guidance belongs in the Studio app docs.
OSS docsstudioStudio is additive to OSS, not the source of truth.
Previous
Examples
Explore runnable examples and use them as reference implementations for new systems.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.