@@ -51,7 +51,7 @@ <h1>One typed model → idiomatic code, in your language.</h1>
         for tasks,"</em> <em>"add a priority field and update everything."</em> Because <code>meta&nbsp;init</code> installs
         the MetaObjects skills, it knows the model is the source of truth: it edits the model, picks the generators the
         job needs, and <strong>generates the code</strong> — it never hand-writes the boilerplate. Every command and
-        output below is real <span class="real">verified</span>, run against <code>@metaobjectsdev/cli@1.0.9</code>.</p>
+        output below is real <span class="real">verified</span>, run against <code>@metaobjectsdev/cli@1.1.0</code>.</p>
     </section>
 
     <section>
@@ -147,14 +147,17 @@ <h2 class="section-label">3 · Pick your language</h2>
         <thead><tr><th>Language</th><th>Install</th><th>Generate</th></tr></thead>
         <tbody>
           <tr><td><strong>TypeScript</strong> (this guide)</td><td><code>npm i @metaobjectsdev/cli</code></td><td><code>meta gen</code></td></tr>
-          <tr><td>C# / .NET</td><td><code>dotnet add package MetaObjects</code></td><td><code>dotnet meta gen</code></td></tr>
-          <tr><td>Java / Kotlin</td><td><code>com.metaobjects</code> (Maven Central)</td><td><code>mvn metaobjects:generate</code></td></tr>
-          <tr><td>Python</td><td><code>pip install metaobjects</code></td><td><code>metaobjects gen</code></td></tr>
+          <tr><td>C# / .NET</td><td><code>dotnet tool install --global MetaObjects.Cli</code>, then <code>dotnet meta init</code></td><td><code>dotnet meta gen ./metaobjects --out ./Generated --namespace App</code></td></tr>
+          <tr><td>Java / Kotlin</td><td><code>com.metaobjects:metaobjects-maven-plugin</code> (Maven Central)</td><td><code>mvn metaobjects:generate</code></td></tr>
+          <tr><td>Python (3.11+)</td><td><code>pip install metaobjects</code></td><td><code>metaobjects gen</code></td></tr>
         </tbody>
       </table>
       <p class="gs-note">Every port works the same way: <strong>nothing is generated until you name the generators you
-        want</strong>. There is no default suite to switch off. <code>--list</code> is the catalog in each CLI, and the
-        C# and Python CLIs take the names you chose with <code>--generators</code>.</p>
+        want</strong>. There is no default suite to switch off. <code>--list</code> is the catalog in the TypeScript and C# CLIs. Each port keeps the
+        list you chose in a file you own: <code>generators</code> in <code>metaobjects.config.ts</code> (TypeScript),
+        <code>codegen/Generators.cs</code> (C#, which <code>dotnet meta init</code> writes empty), <code>metaobjects.config.yaml</code>
+        (Python), and the plugin's <code>&lt;generators&gt;</code> in your <code>pom.xml</code> (Java and Kotlin, set at plugin level
+        so the bare goal finds it). <code>--generators</code> only narrows a run to names that list already holds.</p>
     </section>
 
     <section>
@@ -198,7 +201,7 @@ <h2 class="section-label">5 · Choose your generators</h2>
   queries            —  Per-entity typed query helpers (findById/create/...).  [would emit 1]
                         requires: entity
 api  —  the HTTP surface — pick ONE framework
-  routes             —  Per-entity Fastify CRUD routes (drizzle-fastify mountCrudRoutes).  [fastify]
+  routes             —  Per-entity Fastify CRUD routes (drizzle-fastify mountCrudRoutes).  [fastify, would emit 1 once dbImport is set]
                         requires: entity
   routes-hono        —  Per-entity Hono CRUD routes (runtime-ts/hono mountCrudRoutes).  [hono, would emit 1]
 <span class="c"># … client, docs and capability generators, then the ai and iam libraries</span></pre>
@@ -216,7 +219,7 @@ <h2 class="section-label">5 · Choose your generators</h2>
 
 Install what the ejected generators and their output need:
 <span class="c">  # … the packages below</span>
-These generators read config: apiPrefix, collectionNameOverrides, columnNamingStrategy, dbImport, dialect, extStyle, …</pre>
+These generators read config: apiPrefix, collectionNameOverrides, dbImport, dialect, extStyle, outputLayout, …</pre>
       <p class="gs-note">Those five files are the point: they're plain TypeScript in your repo, and <strong>yours to
         edit</strong>. <code>meta gen</code> runs those local copies — not the ones inside the package — so changing
         the shape of the generated code is an ordinary edit to a file you own. Ejecting <code>routes</code> also copies
@@ -247,7 +250,6 @@ <h2 class="section-label">5 · Choose your generators</h2>
     namesFile(),            <span class="c">// &lt;Entity&gt;Names — physical table/column constants</span>
     barrel(),               <span class="c">// src/generated/index.ts re-exports</span>
   ],
-  docs: { outDir: <span class="s">"./docs/generated"</span>, layout: <span class="s">"flat"</span> },
 });</pre>
       <p class="gs-note">The rest of the catalog works the same way: React forms, TanStack hooks and grids, Hono routes,
         prompt renderers and parsers. <code>meta eject form</code> is all it takes to own one.</p>
 
@@ -3,8 +3,8 @@
 <head>
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
-  <title>MetaObjects — Cross-language metadata standard for codegen, runtime, drift detection, prompts, and requirements</title>
-  <meta name="description" content="Define typed entities once. Generate idiomatic code in TypeScript, Java, Kotlin, C#.NET, and Python. Runtime metadata. Drift detection. Conformance-gated. Apache 2.0. Installable in all five languages — npm, Maven Central, NuGet, and PyPI.">
+  <title>MetaObjects — One typed model of your app. Your agent writes it, your code is generated from it, your build is checked against it.</title>
+  <meta name="description" content="Coding agents get context — rules files, memories, MCP servers — and context is advisory: nothing fails when the code stops matching it.">
 
   <link rel="icon" href="/images/mo-logo-only.png" type="image/png">
 
@@ -14,11 +14,19 @@
 
   <link rel="stylesheet" href="/styles.css">
 
-  <meta property="og:title" content="MetaObjects — Cross-language metadata standard">
-  <meta property="og:description" content="Codegen, runtime metadata, drift detection, prompt construction, capability requirements, and libraries for TypeScript, Java, Kotlin, C#.NET, and Python. Installable in all five — npm, Maven Central, NuGet, PyPI. Apache 2.0.">
+  <meta property="og:title" content="One typed model of your app. Your agent writes it, your code is generated from it, your build is checked against it.">
+  <meta property="og:description" content="Coding agents get context — rules files, memories, MCP servers — and context is advisory: nothing fails when the code stops matching it.">
   <meta property="og:type" content="website">
+  <meta property="og:site_name" content="MetaObjects">
   <meta property="og:url" content="https://metaobjects.dev/">
-  <meta property="og:image" content="https://metaobjects.dev/images/mo-logo.png">
+  <meta property="og:image" content="https://metaobjects.dev/images/cli-drift-poster.png">
+  <meta property="og:image:width" content="1280">
+  <meta property="og:image:height" content="720">
+  <meta property="og:image:alt" content="A terminal recording of meta verify failing the build after a field rename">
+  <meta name="twitter:card" content="summary_large_image">
+  <meta name="twitter:title" content="One typed model of your app. Your agent writes it, your code is generated from it, your build is checked against it.">
+  <meta name="twitter:description" content="Coding agents get context — rules files, memories, MCP servers — and context is advisory: nothing fails when the code stops matching it.">
+  <meta name="twitter:image" content="https://metaobjects.dev/images/cli-drift-poster.png">
 
   <link rel="alternate" type="text/plain" href="/llms.txt" title="llms.txt — AI assistant index">
 </head>
@@ -176,9 +184,9 @@ <h3>Requirements and testing</h3>
           <p>A capability is a node in the same model as your entities, so
           <code>implementedBy</code> is <strong>resolved, not trusted</strong> — a claim whose
           implementation vanished fails the build, and one naming nothing is a warning.
-          <code>meta verify</code> reports the ledger on every run. It proves the links resolve,
+          <code>verify</code> reports the ledger on every run. It proves the links resolve,
           not that the implementation is correct.</p>
-          <p class="pillar-maturity">Vocabulary in all five ports; the <code>meta verify</code> checks run in the Node <code>meta</code> CLI; test scaffolding is TypeScript-only. Dogfooded on maintainer-owned projects, no outside adopter yet.</p>
+          <p class="pillar-maturity">Since 1.1.0 the requirement gate runs in every port's <code>verify</code>, and every port ships a <code>requirement-tests</code> generator; the authoring lint is TypeScript-only (<a href="https://github.com/metaobjectsdev/metaobjects/blob/main/docs/features/requirements.md">docs</a>). Dogfooded on maintainer-owned projects, no outside adopter yet.</p>
           <p class="pillar-read"><a href="/requirements.html">Read: capability requirements&nbsp;→</a></p>
         </article>
         <article class="pillar">
 
@@ -97,7 +97,7 @@
 
   <main>
     <article class="page">
-      <p class="page-eyebrow">Capability requirements · vocabulary in all five ports · checked by the Node <code>meta</code> CLI</p>
+      <p class="page-eyebrow">Capability requirements · vocabulary and the verify gate in all five ports</p>
       <h1>Check what your AI actually built.</h1>
       <p class="page-lede">
         A test exercises code that exists. That is the whole reason a passing suite can sit on
@@ -268,9 +268,9 @@ <h3>You write</h3>
       <pre class="example-code" data-snippet="ts-requirement-test"></pre>
 
       <p>
-        <strong>This part is TypeScript-only.</strong> The vocabulary loads and validates in all
-        five ports, and the <code>meta verify</code> checks run in the Node <code>meta</code> CLI.
-        The test scaffolding is TypeScript's alone.
+        <strong>The example above is TypeScript.</strong> Since 1.1.0 the vocabulary loads and validates in
+        all five ports, the requirement gate runs in every port's <code>verify</code>, and every port
+        ships a <code>requirement-tests</code> generator. Only the authoring lint is TypeScript-only.
       </p>
 
       <h2>Where it sits</h2>