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.
Build
The OSS foundation is a library system, not a closed platform.
ContractSpec is assembled from libraries that remain useful on their own and stronger together. Start with the contract and schema foundation, then add runtime, UI, integration, and operator packages as your system grows.
Keep reusable behavior in libraries, compose it into bundle-level surfaces, and reserve app packages for concrete delivery shells.
Contract and schema foundation
Use these packages to define explicit contracts, schemas, and generated artifacts without inventing a new platform-specific language.
Runtime and surface libraries
These packages execute the contract model across UI, data, observability, workflows, and generated runtime behavior.
@contractspec/lib.runtime
Run typed capability surfaces, execute policies, and connect runtime adapters.
@contractspec/lib.ui-kit
Render shared surfaces across web and React Native without forking the contract layer.
@contractspec/lib.design-system
Build higher-level product surfaces and documented marketing/docs primitives on top of the UI kit.
@contractspec/lib.data-views
Generate and render list/detail style surfaces that stay aligned with data contracts.
Operator and system packages
These packages matter once the system is live and you need governance, resilience, and observability.
@contractspec/lib.observability
Trace, log, and measure contract execution using the same system boundaries.
@contractspec/lib.resilience
Add circuit breakers, retries, and failure controls without hiding the integration model.
@contractspec/lib.multi-tenancy
Keep tenant-specific config, policy, and surface resolution explicit.
@contractspec/lib.workflow-composer
Compose and extend workflows without smearing orchestration concerns across apps.
Docs generation pipeline
Feed generated docs into the public docs site without breaking source-of-truth ownership.
Architecture
See how the spec layer, runtimes, integrations, and multi-surface outputs fit together.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.