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.
Operate
Safety is part of the system model, not an afterthought.
ContractSpec is meant to survive real change: new generated surfaces, policy updates, migrations, integration churn, and operator handoffs. The safety layer makes those changes inspectable, reversible, and governed.
Use policies, signing, audit trails, and migrations to keep the system legible even as AI-assisted workflows accelerate change volume.
Spec signing
Protect the integrity of what gets deployed and make changes verifiable.
Policy decision points
Apply governance consistently across operations, data access, and generated surfaces.
Audit trails
Record operational and policy decisions with enough context to inspect and explain them later.
Migrations
Evolve data and schema boundaries without losing control of the system.
Tenant isolation
Keep configuration, access rules, and sensitive data bounded by tenant.
Security and trust
Understand the trust model, release process, and security expectations around the OSS system.
Architecture
See how the spec layer, runtimes, integrations, and multi-surface outputs fit together.
CI diff gating
Use deterministic checks to block drift and risky changes before they reach production.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.