The 90-second ContractSpec story
Start with open contracts. Add Studio only when the team is ready.
ContractSpec is the open spec system for AI-native software: typed contracts keep APIs, data, interfaces, tools, and evidence aligned so teams can regenerate safely. Studio is the packaged operating layer on top, not a replacement for the OSS foundation.
90-second story
The OSS foundation comes first.
In the first 90 seconds, the homepage should make the path obvious: install the open contract layer, prove one risky module, then evaluate Studio only when the operating loop needs packaging.
- Keep the code and the standards you already use.
- Stabilize one module at a time instead of rewriting your app.
- Move into Studio only when you want the packaged operating layer on top.
Why teams end up here
Agents do not break software because they are fast. They break what is implicit.
Once agents touch code, data, UI, workflows, and tools, the failure mode is not simply bad generated code. It is that the company cannot state the system rules precisely enough for every surface to stay aligned.
Implicit rules drift first
Prompt chains and AI edits move faster than the product rules they are supposed to respect.
Surfaces stop agreeing
API, UI, database, events, and MCP tools evolve independently unless something explicit keeps them aligned.
Teams lose safe regeneration
Without a stable contract layer, every regeneration feels like rewriting production in the dark.
The promise
Declare contracts once. Project them into every surface that drifts.
ContractSpec is broader than code generation: it is a static, inspectable contract layer that adapters, interfaces, agent tools, and evidence flows can share.
Contracts and specs
Write the canonical product rules before generators, agents, or interfaces reinterpret them.
Aligned surfaces
Project the same contract into APIs, data, UI, events, and tools instead of maintaining parallel truths.
Agent-readable operations
Expose MCP/tool surfaces from explicit intent, scope, policy, approval, and evidence contracts.
Evidence and replay
Inspect what was generated, approved, executed, and replayed before trusting more automation.
Proof routes
Choose the next page by the question you have.
The homepage stays short. Product, use cases, docs, and Studio each answer one deeper adoption question.
Can I see what this builds?
Open use cases and templates to inspect scenario problems, contracts, generated surfaces, and proof paths.
How does the system work?
Use the product page for the conceptual layer model before diving into API docs.
How do I start?
Go to docs/install when you are ready to wire a first contract into code you already own.
What happens after OSS?
Explore Studio only when the open contract layer is understood and you want the managed operating product.
Choose your path
Build on the open substrate. Choose Studio when you want the operating layer.
ContractSpec is the technical foundation for AI-native software. Studio is the invite-led operating layer for teams that want the company brain, role-aware operations, and evidence loop packaged for them.