@contractspec/bundle.library 3.8.10 → 3.8.12

package/dist/components/docs/safety/SafetyMigrationsPage.js

@@ -1,154 +1,5 @@
 // @bun
-// src/components/docs/safety/SafetyMigrationsPage.tsx
-import Link from "@contractspec/lib.ui-link";
-import { ChevronRight } from "lucide-react";
-import { jsx, jsxs } from "react/jsx-runtime";
-function SafetyMigrationsPage() {
-  return /* @__PURE__ */ jsxs("div", {
-    className: "space-y-8",
-    children: [
-      /* @__PURE__ */ jsxs("div", {
-        className: "space-y-4",
-        children: [
-          /* @__PURE__ */ jsx("h1", {
-            className: "font-bold text-4xl",
-            children: "Migrations"
-          }),
-          /* @__PURE__ */ jsxs("p", {
-            className: "text-muted-foreground",
-            children: [
-              "A ",
-              /* @__PURE__ */ jsx("strong", {
-                children: "schema migration"
-              }),
-              " (also called a database migration) is a set of incremental, reversible changes to a database schema. According to",
-              " ",
-              /* @__PURE__ */ jsx("a", {
-                href: "https://en.wikipedia.org/wiki/Schema_migration",
-                target: "_blank",
-                rel: "noopener noreferrer",
-                className: "text-violet-400 hover:text-violet-300",
-                children: "Wikipedia"
-              }),
-              `, schema migrations "allow the database schema to evolve as the application's requirements change, while preserving existing data."`
-            ]
-          })
-        ]
-      }),
-      /* @__PURE__ */ jsxs("div", {
-        className: "space-y-4",
-        children: [
-          /* @__PURE__ */ jsx("h2", {
-            className: "font-bold text-2xl",
-            children: "Why migrations matter"
-          }),
-          /* @__PURE__ */ jsx("p", {
-            className: "text-muted-foreground",
-            children: "As your application evolves, you'll need to change your data model\u2014adding new fields, renaming tables, changing data types, or restructuring relationships. Without a disciplined approach, these changes can lead to:"
-          }),
-          /* @__PURE__ */ jsxs("ul", {
-            className: "list-inside list-disc space-y-2 text-muted-foreground",
-            children: [
-              /* @__PURE__ */ jsx("li", {
-                children: "Data loss or corruption"
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Downtime during deployments"
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Inconsistencies between environments (dev, staging, production)"
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Difficulty rolling back failed changes"
-              })
-            ]
-          }),
-          /* @__PURE__ */ jsx("p", {
-            className: "text-muted-foreground",
-            children: "Migrations solve these problems by treating schema changes as versioned, tested, and reversible operations."
-          })
-        ]
-      }),
-      /* @__PURE__ */ jsxs("div", {
-        className: "space-y-4",
-        children: [
-          /* @__PURE__ */ jsx("h2", {
-            className: "font-bold text-2xl",
-            children: "How MigrationSpec works"
-          }),
-          /* @__PURE__ */ jsxs("p", {
-            className: "text-muted-foreground",
-            children: [
-              "In ContractSpec, migrations are defined using",
-              " ",
-              /* @__PURE__ */ jsx("strong", {
-                children: "MigrationSpec"
-              }),
-              ". Each migration has:"
-            ]
-          }),
-          /* @__PURE__ */ jsxs("ul", {
-            className: "list-inside list-disc space-y-2 text-muted-foreground",
-            children: [
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Version"
-                  }),
-                  ' \u2013 A unique identifier (e.g., "2025-11-13-001") that determines the order of execution.'
-                ]
-              }),
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Up function"
-                  }),
-                  ` \u2013 The forward migration that applies the change (e.g., "add column 'email_verified'").`
-                ]
-              }),
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Down function"
-                  }),
-                  ` \u2013 The reverse migration that undoes the change (e.g., "drop column 'email_verified'").`
-                ]
-              }),
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Dependencies"
-                  }),
-                  " \u2013 Other migrations that must run before this one."
-                ]
-              }),
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Validation"
-                  }),
-                  ' \u2013 Optional checks to ensure the migration succeeded (e.g., "verify all users have an email address").'
-                ]
-              })
-            ]
-          })
-        ]
-      }),
-      /* @__PURE__ */ jsxs("div", {
-        className: "space-y-4",
-        children: [
-          /* @__PURE__ */ jsx("h2", {
-            className: "font-bold text-2xl",
-            children: "Example MigrationSpec"
-          }),
-          /* @__PURE__ */ jsx("p", {
-            className: "text-muted-foreground",
-            children: "Here's a migration that adds an email verification field to the users table:"
-          }),
-          /* @__PURE__ */ jsx("div", {
-            className: "overflow-x-auto rounded-lg border border-border bg-background/50 p-4 font-mono text-muted-foreground text-sm",
-            children: /* @__PURE__ */ jsx("pre", {
-              children: `migrationId: add-email-verified
+import A from"@contractspec/lib.ui-link";import{ChevronRight as B}from"lucide-react";import{jsx as q,jsxs as z}from"react/jsx-runtime";function F(){return z("div",{className:"space-y-8",children:[z("div",{className:"space-y-4",children:[q("h1",{className:"font-bold text-4xl",children:"Migrations"}),z("p",{className:"text-muted-foreground",children:["A ",q("strong",{children:"schema migration"})," (also called a database migration) is a set of incremental, reversible changes to a database schema. According to"," ",q("a",{href:"https://en.wikipedia.org/wiki/Schema_migration",target:"_blank",rel:"noopener noreferrer",className:"text-violet-400 hover:text-violet-300",children:"Wikipedia"}),`, schema migrations "allow the database schema to evolve as the application's requirements change, while preserving existing data."`]})]}),z("div",{className:"space-y-4",children:[q("h2",{className:"font-bold text-2xl",children:"Why migrations matter"}),q("p",{className:"text-muted-foreground",children:"As your application evolves, you'll need to change your data model\u2014adding new fields, renaming tables, changing data types, or restructuring relationships. Without a disciplined approach, these changes can lead to:"}),z("ul",{className:"list-inside list-disc space-y-2 text-muted-foreground",children:[q("li",{children:"Data loss or corruption"}),q("li",{children:"Downtime during deployments"}),q("li",{children:"Inconsistencies between environments (dev, staging, production)"}),q("li",{children:"Difficulty rolling back failed changes"})]}),q("p",{className:"text-muted-foreground",children:"Migrations solve these problems by treating schema changes as versioned, tested, and reversible operations."})]}),z("div",{className:"space-y-4",children:[q("h2",{className:"font-bold text-2xl",children:"How MigrationSpec works"}),z("p",{className:"text-muted-foreground",children:["In ContractSpec, migrations are defined using"," ",q("strong",{children:"MigrationSpec"}),". Each migration has:"]}),z("ul",{className:"list-inside list-disc space-y-2 text-muted-foreground",children:[z("li",{children:[q("strong",{children:"Version"}),' \u2013 A unique identifier (e.g., "2025-11-13-001") that determines the order of execution.']}),z("li",{children:[q("strong",{children:"Up function"}),` \u2013 The forward migration that applies the change (e.g., "add column 'email_verified'").`]}),z("li",{children:[q("strong",{children:"Down function"}),` \u2013 The reverse migration that undoes the change (e.g., "drop column 'email_verified'").`]}),z("li",{children:[q("strong",{children:"Dependencies"})," \u2013 Other migrations that must run before this one."]}),z("li",{children:[q("strong",{children:"Validation"}),' \u2013 Optional checks to ensure the migration succeeded (e.g., "verify all users have an email address").']})]})]}),z("div",{className:"space-y-4",children:[q("h2",{className:"font-bold text-2xl",children:"Example MigrationSpec"}),q("p",{className:"text-muted-foreground",children:"Here's a migration that adds an email verification field to the users table:"}),q("div",{className:"overflow-x-auto rounded-lg border border-border bg-background/50 p-4 font-mono text-muted-foreground text-sm",children:q("pre",{children:`migrationId: add-email-verified
 version: 2025-11-13-001
 dependencies: []
 
@@ -171,212 +22,4 @@ validation:
   - sql: |
       SELECT COUNT(*) FROM users
       WHERE email_verified IS NULL;
-    expectZeroRows: true`
-            })
-          })
-        ]
-      }),
-      /* @__PURE__ */ jsxs("div", {
-        className: "space-y-4",
-        children: [
-          /* @__PURE__ */ jsx("h2", {
-            className: "font-bold text-2xl",
-            children: "Running migrations"
-          }),
-          /* @__PURE__ */ jsx("p", {
-            className: "text-muted-foreground",
-            children: "Migrations are applied automatically during deployment. The ContractSpec runtime:"
-          }),
-          /* @__PURE__ */ jsxs("ol", {
-            className: "list-inside list-decimal space-y-2 text-muted-foreground",
-            children: [
-              /* @__PURE__ */ jsx("li", {
-                children: "Checks which migrations have already been applied (stored in a migrations table)."
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Identifies new migrations that need to run."
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Executes them in order, respecting dependencies."
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Runs validation checks to ensure success."
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Records the migration as applied."
-              })
-            ]
-          }),
-          /* @__PURE__ */ jsx("p", {
-            className: "text-muted-foreground",
-            children: "If a migration fails, the deployment is aborted, and the system remains in its previous state. You can then fix the migration and redeploy."
-          })
-        ]
-      }),
-      /* @__PURE__ */ jsxs("div", {
-        className: "space-y-4",
-        children: [
-          /* @__PURE__ */ jsx("h2", {
-            className: "font-bold text-2xl",
-            children: "Rolling back migrations"
-          }),
-          /* @__PURE__ */ jsxs("p", {
-            className: "text-muted-foreground",
-            children: [
-              "If you need to roll back a deployment, ContractSpec automatically runs the ",
-              /* @__PURE__ */ jsx("strong", {
-                children: "down"
-              }),
-              " functions of any migrations that were applied. This restores the database to its previous state."
-            ]
-          }),
-          /* @__PURE__ */ jsx("p", {
-            className: "text-muted-foreground",
-            children: "Note that rollbacks are not always possible\u2014for example, if you've deleted a column, you cannot recover the data unless you have a backup. For destructive changes, it's best to use a multi-step migration:"
-          }),
-          /* @__PURE__ */ jsxs("ol", {
-            className: "list-inside list-decimal space-y-2 text-muted-foreground",
-            children: [
-              /* @__PURE__ */ jsx("li", {
-                children: "Add the new column (reversible)."
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Backfill data from the old column to the new column (reversible)."
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Update application code to use the new column (reversible)."
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Drop the old column (irreversible\u2014only do this after confirming the new column works)."
-              })
-            ]
-          })
-        ]
-      }),
-      /* @__PURE__ */ jsxs("div", {
-        className: "space-y-4",
-        children: [
-          /* @__PURE__ */ jsx("h2", {
-            className: "font-bold text-2xl",
-            children: "Best practices"
-          }),
-          /* @__PURE__ */ jsxs("ul", {
-            className: "list-inside list-disc space-y-2 text-muted-foreground",
-            children: [
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Test migrations locally"
-                  }),
-                  " \u2013 Run them against a copy of production data to catch issues before deploying."
-                ]
-              }),
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Keep migrations small"
-                  }),
-                  " \u2013 Each migration should do one thing. This makes them easier to understand and roll back."
-                ]
-              }),
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Write reversible migrations"
-                  }),
-                  " \u2013 Always provide a down function, even if you don't plan to roll back."
-                ]
-              }),
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Use transactions"
-                  }),
-                  " \u2013 Wrap migrations in database transactions so they either fully succeed or fully fail."
-                ]
-              }),
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Avoid destructive changes"
-                  }),
-                  " \u2013 Prefer additive changes (adding columns) over destructive ones (dropping columns). If you must delete data, archive it first."
-                ]
-              }),
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Version your migrations"
-                  }),
-                  " \u2013 Use timestamps or sequential numbers to ensure migrations run in the correct order."
-                ]
-              }),
-              /* @__PURE__ */ jsxs("li", {
-                children: [
-                  /* @__PURE__ */ jsx("strong", {
-                    children: "Document breaking changes"
-                  }),
-                  " \u2013 If a migration requires application code changes, note this in the migration description."
-                ]
-              })
-            ]
-          })
-        ]
-      }),
-      /* @__PURE__ */ jsxs("div", {
-        className: "space-y-4",
-        children: [
-          /* @__PURE__ */ jsx("h2", {
-            className: "font-bold text-2xl",
-            children: "Zero-downtime migrations"
-          }),
-          /* @__PURE__ */ jsx("p", {
-            className: "text-muted-foreground",
-            children: "Some migrations can cause downtime if not handled carefully. For example, adding a NOT NULL column to a large table can lock the table for minutes. To avoid this, use a multi-step approach:"
-          }),
-          /* @__PURE__ */ jsxs("ol", {
-            className: "list-inside list-decimal space-y-2 text-muted-foreground",
-            children: [
-              /* @__PURE__ */ jsx("li", {
-                children: "Add the column as nullable."
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Backfill the column in batches (without locking the table)."
-              }),
-              /* @__PURE__ */ jsx("li", {
-                children: "Add the NOT NULL constraint once all rows are populated."
-              })
-            ]
-          }),
-          /* @__PURE__ */ jsx("p", {
-            className: "text-muted-foreground",
-            children: "ContractSpec's migration system supports this pattern by allowing you to split a logical change into multiple versioned migrations."
-          })
-        ]
-      }),
-      /* @__PURE__ */ jsxs("div", {
-        className: "flex items-center gap-4 pt-4",
-        children: [
-          /* @__PURE__ */ jsx(Link, {
-            href: "/docs/safety/auditing",
-            className: "btn-ghost",
-            children: "Previous: Audit Logs"
-          }),
-          /* @__PURE__ */ jsxs(Link, {
-            href: "/docs/advanced/renderers",
-            className: "btn-primary",
-            children: [
-              "Next: Advanced Topics ",
-              /* @__PURE__ */ jsx(ChevronRight, {
-                size: 16
-              })
-            ]
-          })
-        ]
-      })
-    ]
-  });
-}
-export {
-  SafetyMigrationsPage
-};
+    expectZeroRows: true`})})]}),z("div",{className:"space-y-4",children:[q("h2",{className:"font-bold text-2xl",children:"Running migrations"}),q("p",{className:"text-muted-foreground",children:"Migrations are applied automatically during deployment. The ContractSpec runtime:"}),z("ol",{className:"list-inside list-decimal space-y-2 text-muted-foreground",children:[q("li",{children:"Checks which migrations have already been applied (stored in a migrations table)."}),q("li",{children:"Identifies new migrations that need to run."}),q("li",{children:"Executes them in order, respecting dependencies."}),q("li",{children:"Runs validation checks to ensure success."}),q("li",{children:"Records the migration as applied."})]}),q("p",{className:"text-muted-foreground",children:"If a migration fails, the deployment is aborted, and the system remains in its previous state. You can then fix the migration and redeploy."})]}),z("div",{className:"space-y-4",children:[q("h2",{className:"font-bold text-2xl",children:"Rolling back migrations"}),z("p",{className:"text-muted-foreground",children:["If you need to roll back a deployment, ContractSpec automatically runs the ",q("strong",{children:"down"})," functions of any migrations that were applied. This restores the database to its previous state."]}),q("p",{className:"text-muted-foreground",children:"Note that rollbacks are not always possible\u2014for example, if you've deleted a column, you cannot recover the data unless you have a backup. For destructive changes, it's best to use a multi-step migration:"}),z("ol",{className:"list-inside list-decimal space-y-2 text-muted-foreground",children:[q("li",{children:"Add the new column (reversible)."}),q("li",{children:"Backfill data from the old column to the new column (reversible)."}),q("li",{children:"Update application code to use the new column (reversible)."}),q("li",{children:"Drop the old column (irreversible\u2014only do this after confirming the new column works)."})]})]}),z("div",{className:"space-y-4",children:[q("h2",{className:"font-bold text-2xl",children:"Best practices"}),z("ul",{className:"list-inside list-disc space-y-2 text-muted-foreground",children:[z("li",{children:[q("strong",{children:"Test migrations locally"})," \u2013 Run them against a copy of production data to catch issues before deploying."]}),z("li",{children:[q("strong",{children:"Keep migrations small"})," \u2013 Each migration should do one thing. This makes them easier to understand and roll back."]}),z("li",{children:[q("strong",{children:"Write reversible migrations"})," \u2013 Always provide a down function, even if you don't plan to roll back."]}),z("li",{children:[q("strong",{children:"Use transactions"})," \u2013 Wrap migrations in database transactions so they either fully succeed or fully fail."]}),z("li",{children:[q("strong",{children:"Avoid destructive changes"})," \u2013 Prefer additive changes (adding columns) over destructive ones (dropping columns). If you must delete data, archive it first."]}),z("li",{children:[q("strong",{children:"Version your migrations"})," \u2013 Use timestamps or sequential numbers to ensure migrations run in the correct order."]}),z("li",{children:[q("strong",{children:"Document breaking changes"})," \u2013 If a migration requires application code changes, note this in the migration description."]})]})]}),z("div",{className:"space-y-4",children:[q("h2",{className:"font-bold text-2xl",children:"Zero-downtime migrations"}),q("p",{className:"text-muted-foreground",children:"Some migrations can cause downtime if not handled carefully. For example, adding a NOT NULL column to a large table can lock the table for minutes. To avoid this, use a multi-step approach:"}),z("ol",{className:"list-inside list-decimal space-y-2 text-muted-foreground",children:[q("li",{children:"Add the column as nullable."}),q("li",{children:"Backfill the column in batches (without locking the table)."}),q("li",{children:"Add the NOT NULL constraint once all rows are populated."})]}),q("p",{className:"text-muted-foreground",children:"ContractSpec's migration system supports this pattern by allowing you to split a logical change into multiple versioned migrations."})]}),z("div",{className:"flex items-center gap-4 pt-4",children:[q(A,{href:"/docs/safety/auditing",className:"btn-ghost",children:"Previous: Audit Logs"}),z(A,{href:"/docs/advanced/renderers",className:"btn-primary",children:["Next: Advanced Topics ",q(B,{size:16})]})]})]})}export{F as SafetyMigrationsPage};

package/dist/components/docs/safety/SafetyOverviewPage.js

@@ -1,102 +1,2 @@
 // @bun
-// src/components/docs/safety/SafetyOverviewPage.tsx
-import Link from "@contractspec/lib.ui-link";
-import { jsx, jsxs } from "react/jsx-runtime";
-var safetyPages = [
-  {
-    title: "Spec signing",
-    body: "Protect the integrity of what gets deployed and make changes verifiable.",
-    href: "/docs/safety/signing"
-  },
-  {
-    title: "Policy decision points",
-    body: "Apply governance consistently across operations, data access, and generated surfaces.",
-    href: "/docs/safety/pdp"
-  },
-  {
-    title: "Audit trails",
-    body: "Record operational and policy decisions with enough context to inspect and explain them later.",
-    href: "/docs/safety/auditing"
-  },
-  {
-    title: "Migrations",
-    body: "Evolve data and schema boundaries without losing control of the system.",
-    href: "/docs/safety/migrations"
-  },
-  {
-    title: "Tenant isolation",
-    body: "Keep configuration, access rules, and sensitive data bounded by tenant.",
-    href: "/docs/safety/tenant-isolation"
-  },
-  {
-    title: "Security and trust",
-    body: "Understand the trust model, release process, and security expectations around the OSS system.",
-    href: "/docs/safety/security-trust"
-  }
-];
-function SafetyOverviewPage() {
-  return /* @__PURE__ */ jsxs("div", {
-    className: "space-y-10",
-    children: [
-      /* @__PURE__ */ jsxs("div", {
-        className: "space-y-3",
-        children: [
-          /* @__PURE__ */ jsx("p", {
-            className: "editorial-kicker",
-            children: "Operate"
-          }),
-          /* @__PURE__ */ jsx("h1", {
-            className: "font-serif text-4xl tracking-[-0.04em] md:text-5xl",
-            children: "Safety is part of the system model, not an afterthought."
-          }),
-          /* @__PURE__ */ jsx("p", {
-            className: "max-w-3xl text-lg text-muted-foreground leading-8",
-            children: "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."
-          })
-        ]
-      }),
-      /* @__PURE__ */ jsxs("div", {
-        className: "editorial-proof-strip",
-        children: [
-          /* @__PURE__ */ jsxs("div", {
-            className: "editorial-stat",
-            children: [
-              /* @__PURE__ */ jsx("span", {
-                className: "editorial-label",
-                children: "Operating rule"
-              }),
-              /* @__PURE__ */ jsx("span", {
-                className: "editorial-stat-value",
-                children: "explicit change beats hidden mutation"
-              })
-            ]
-          }),
-          /* @__PURE__ */ jsx("p", {
-            className: "max-w-2xl text-muted-foreground text-sm leading-7",
-            children: "Use policies, signing, audit trails, and migrations to keep the system legible even as AI-assisted workflows accelerate change volume."
-          })
-        ]
-      }),
-      /* @__PURE__ */ jsx("div", {
-        className: "grid gap-4 md:grid-cols-2",
-        children: safetyPages.map((page) => /* @__PURE__ */ jsxs(Link, {
-          href: page.href,
-          className: "editorial-panel",
-          children: [
-            /* @__PURE__ */ jsx("h2", {
-              className: "font-semibold text-xl",
-              children: page.title
-            }),
-            /* @__PURE__ */ jsx("p", {
-              className: "mt-2 text-muted-foreground text-sm leading-7",
-              children: page.body
-            })
-          ]
-        }, page.href))
-      })
-    ]
-  });
-}
-export {
-  SafetyOverviewPage
-};
+import i from"@contractspec/lib.ui-link";import{jsx as e,jsxs as t}from"react/jsx-runtime";var s=[{title:"Spec signing",body:"Protect the integrity of what gets deployed and make changes verifiable.",href:"/docs/safety/signing"},{title:"Policy decision points",body:"Apply governance consistently across operations, data access, and generated surfaces.",href:"/docs/safety/pdp"},{title:"Audit trails",body:"Record operational and policy decisions with enough context to inspect and explain them later.",href:"/docs/safety/auditing"},{title:"Migrations",body:"Evolve data and schema boundaries without losing control of the system.",href:"/docs/safety/migrations"},{title:"Tenant isolation",body:"Keep configuration, access rules, and sensitive data bounded by tenant.",href:"/docs/safety/tenant-isolation"},{title:"Security and trust",body:"Understand the trust model, release process, and security expectations around the OSS system.",href:"/docs/safety/security-trust"}];function o(){return t("div",{className:"space-y-10",children:[t("div",{className:"space-y-3",children:[e("p",{className:"editorial-kicker",children:"Operate"}),e("h1",{className:"font-serif text-4xl tracking-[-0.04em] md:text-5xl",children:"Safety is part of the system model, not an afterthought."}),e("p",{className:"max-w-3xl text-lg text-muted-foreground leading-8",children:"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."})]}),t("div",{className:"editorial-proof-strip",children:[t("div",{className:"editorial-stat",children:[e("span",{className:"editorial-label",children:"Operating rule"}),e("span",{className:"editorial-stat-value",children:"explicit change beats hidden mutation"})]}),e("p",{className:"max-w-2xl text-muted-foreground text-sm leading-7",children:"Use policies, signing, audit trails, and migrations to keep the system legible even as AI-assisted workflows accelerate change volume."})]}),e("div",{className:"grid gap-4 md:grid-cols-2",children:s.map((a)=>t(i,{href:a.href,className:"editorial-panel",children:[e("h2",{className:"font-semibold text-xl",children:a.title}),e("p",{className:"mt-2 text-muted-foreground text-sm leading-7",children:a.body})]},a.href))})]})}export{o as SafetyOverviewPage};