Contracts and schemas
Explicit specs define the durable boundary for behavior, data, and governance.
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 architecture keeps contracts, runtime behavior, and operations in the same system.
ContractSpec is not a single runtime. It is a layered system that lets you define explicit boundaries, bind real-world configuration, and then serve or generate aligned surfaces without losing control of the output.
Bindings and configuration
Apps, tenants, integrations, and knowledge sources are wired through explicit configuration instead of hidden glue.
Runtimes and generators
Serve or generate aligned surfaces for API, UI, workflows, docs, and agent-facing interfaces.
Operate and observe
Carry auditability, policy, tracing, migrations, and tenant isolation through the same model.
UI composition belongs in the bundle runtime layer
When the system needs adaptive layouts, entity workbenches, assistant slots, and safe overlays, use module bundles as the layer between the contract model and the rendered surface.
Follow the architecture by responsibility
Use the architecture pages when you need to understand how the pieces snap together in a real deployment.
App configuration
How blueprint-level and tenant-level config stay explicit and merge safely.
Integration binding
How apps connect to tenant-owned integrations without leaking provider logic everywhere.
Knowledge binding
How trusted knowledge enters the system and stays isolated by context and tenant.
Control plane runtime
How intent, policy, planning, and execution flow through the system runtime.
OSS docsbuildStart with OSS. Adopt Studio when you want the operating layer.
Previous
Design system
Adopt high-level product UI primitives, actionable object references, responsive AdaptivePanel overlays, forms, data tables, and theme helpers.
Next
Operate safely
Add auditability, migrations, policy controls, and trustworthy release behavior from the start.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.