var s=Object.defineProperty;var i=(t)=>t;function r(t,a){this[t]=i.bind(null,a)}var l=(t,a)=>{for(var n in a)s(t,n,{get:a[n],enumerable:!0,configurable:!0,set:r.bind(a,n)})};var c=(t,a)=>()=>(t&&(a=t(t=0)),a);import{jsx as e,jsxs as o}from"react/jsx-runtime";function m(){return o("div",{className:"space-y-8",children:[o("div",{className:"space-y-3",children:[e("p",{className:"editorial-kicker",children:"Why ContractSpec"}),e("h1",{className:"font-serif text-4xl tracking-[-0.04em] md:text-5xl",children:"Open system, explicit contracts, incremental adoption."}),e("p",{className:"max-w-3xl text-lg text-muted-foreground leading-8",children:"ContractSpec exists to make AI-native software more legible and more governable. The system should help teams express durable boundaries, keep generated surfaces aligned, and still own the code and contracts they ship."})]}),o("div",{className:"space-y-6",children:[o("section",{className:"editorial-panel space-y-3",children:[e("h2",{className:"font-serif text-3xl tracking-[-0.03em]",children:"Open system, not closed platform"}),e("p",{className:"text-muted-foreground text-sm leading-7",children:"The OSS layer should remain useful on its own. Teams need explicit contracts, readable code, and outputs they can keep. Studio can sit on top of that system, but it should never be the only way to own or understand the behavior."})]}),o("section",{className:"editorial-panel space-y-3",children:[e("h2",{className:"font-serif text-3xl tracking-[-0.03em]",children:"Contracts before surface sprawl"}),e("p",{className:"text-muted-foreground text-sm leading-7",children:"AI tooling accelerates surface creation faster than most teams can govern it. The answer is not more hidden glue. The answer is a durable contract layer that keeps API, UI, data, workflows, and operator behavior aligned."})]}),o("section",{className:"editorial-panel space-y-3",children:[e("h2",{className:"font-serif text-3xl tracking-[-0.03em]",children:"Incremental adoption wins"}),e("p",{className:"text-muted-foreground text-sm leading-7",children:"Most teams already have a codebase. The practical path is to stabilize one boundary at a time, prove the loop, and grow from there. That is why the docs and product should lead with one module, one endpoint, one workflow, one unsafe surface at a time."})]}),o("section",{className:"editorial-panel space-y-3",children:[e("h2",{className:"font-serif text-3xl tracking-[-0.03em]",children:"Studio should stay additive"}),e("p",{className:"text-muted-foreground text-sm leading-7",children:"The best operating product can and should exist on top of the open system. But the OSS foundation must remain strong enough that technical adopters trust it before they ever adopt Studio."})]})]})]})}export{m as ManifestoPage};
