site: add the video series page (5 videos) + Videos nav link

New /videos.html hosts the introduction plus the four feature videos (getting
started, adopt existing, drift detection, runtime UI). mp4s stream from
metaobjects.com/Cloudflare (Pages rejects large mp4s); posters + English VTT
captions are same-origin. Videos link added to the nav on every page.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SKaSE8U5cwN4ZGFwhJwxSY

Author: dmealing

www/getting-started.html

@@ -37,6 +37,7 @@
     <a href="/" class="brand"><img src="/images/mo-logo-only.png" alt="" class="brand-mark"><span class="brand-name">MetaObjects</span></a>
     <nav>
       <a href="/" class="nav-link">Home</a>
+      <a href="/videos.html" class="nav-link">Videos</a>
       <a href="https://github.com/metaobjectsdev/metaobjects" class="nav-link">GitHub</a>
       <a href="https://github.com/metaobjectsdev/metaobjects/tree/main/spec" class="nav-link nav-cta">Spec</a>
     </nav>

www/index.html

@@ -31,6 +31,7 @@
     <nav>
       <a href="/getting-started.html" class="nav-link">Get started</a>
       <a href="/story.html" class="nav-link">Story</a>
+      <a href="/videos.html" class="nav-link">Videos</a>
       <a href="https://github.com/metaobjectsdev/metaobjects" class="nav-link">GitHub</a>
       <a href="#ai" class="nav-link">For AI</a>
       <a href="https://github.com/metaobjectsdev/metaobjects/tree/main/spec" class="nav-link nav-cta">Spec</a>

www/story.html

@@ -54,6 +54,7 @@
     </a>
     <nav>
       <a href="/getting-started.html" class="nav-link">Get started</a>
+      <a href="/videos.html" class="nav-link">Videos</a>
       <a href="https://github.com/metaobjectsdev/metaobjects" class="nav-link">GitHub</a>
       <a href="/#ai" class="nav-link">For AI</a>
       <a href="https://github.com/metaobjectsdev/metaobjects/tree/main/spec" class="nav-link nav-cta">Spec</a>

www/video/adopt-existing-poster.png

@@ -0,0 +1,126 @@
+WEBVTT
+
+1
+00:00:00.500 --> 00:00:04.335
+Most teams don't start from scratch — they have an app already.
+
+2
+00:00:04.335 --> 00:00:07.926
+Good news: you don't have to rewrite it to use MetaObjects.
+
+3
+00:00:07.926 --> 00:00:09.630
+You adopt it, incrementally.
+
+4
+00:00:09.630 --> 00:00:10.300
+Here's how.
+
+5
+00:00:11.700 --> 00:00:16.466
+This is a real app — real tables, a real database, none of it built by MetaObjects.
+
+6
+00:00:16.466 --> 00:00:22.208
+We're going to point MetaObjects at one table, and get typed code for it, without touching the rest.
+
+7
+00:00:23.608 --> 00:00:26.815
+There's no magic import — and honestly, that's fine.
+
+8
+00:00:26.815 --> 00:00:29.591
+You describe one existing entity in metadata.
+
+9
+00:00:29.591 --> 00:00:39.090
+And you don't write it from scratch: hand your schema to Claude Code, which already knows the workflow from meta init, and it drafts the metadata for you.
+
+10
+00:00:39.090 --> 00:00:44.888
+Adopting an existing app is a judgment call, not a one-click button — so start with one table.
+
+11
+00:00:46.288 --> 00:00:50.407
+Here's that one table described — matching the columns you already have.
+
+12
+00:00:50.407 --> 00:00:55.842
+The source points at your existing customers table, and fullName maps to your full name column.
+
+13
+00:00:55.842 --> 00:01:02.879
+And look at the email field: validators live right on it, as child metadata — a required check and an email-format pattern.
+
+14
+00:01:02.879 --> 00:01:07.227
+That's validation you get to layer on, that the raw database never enforced.
+
+15
+00:01:08.627 --> 00:01:09.603
+Then meta gen.
+
+16
+00:01:09.603 --> 00:01:17.827
+You get a typed entity, queries, and routes for your existing table — generated alongside your app, not instead of it.
+
+17
+00:01:19.227 --> 00:01:26.359
+And the generated code maps your real schema — Drizzle and Zod for your customers table, with fullName wired to full name.
+
+18
+00:01:26.359 --> 00:01:32.672
+And the validators you layered on come through too: the email format check is right there in the Zod schema.
+
+19
+00:01:32.672 --> 00:01:35.069
+Typed, idiomatic, ready to use right now.
+
+20
+00:01:36.469 --> 00:01:40.232
+Run verify against your live database, and it tells you exactly where you stand.
+
+21
+00:01:40.232 --> 00:01:41.550
+Customers matches the model.
+
+22
+00:01:41.550 --> 00:01:45.549
+Orders isn't modeled yet — so that's your next table to adopt, whenever you're ready.
+
+23
+00:01:46.949 --> 00:01:48.605
+This is low-risk by design.
+
+24
+00:01:48.605 --> 00:01:54.373
+The generated code runs with no MetaObjects dependency, so adopting it commits you to nothing.
+
+25
+00:01:54.373 --> 00:02:02.594
+You take one table at a time, the rest of your app is untouched, and you keep your escape hatches for anything metadata can't express.
+
+26
+00:02:03.994 --> 00:02:09.393
+That's adoption: describe one table, generate, adopt — no big rewrite, no magic.
+
+27
+00:02:09.393 --> 00:02:16.345
+Then, table by table, the model becomes the spine, and meta verify keeps it honest as you grow into it.
+
+28
+00:02:17.745 --> 00:02:20.295
+You don't have to start over to start.
+
+29
+00:02:20.295 --> 00:02:23.381
+Run meta init, describe a table, and meta gen.
+
+30
+00:02:23.381 --> 00:02:27.407
+That's the MetaObjects series — more at metaobjects dot dev.
+
+31
+00:02:27.407 --> 00:02:28.749
+Thanks for watching.
+

www/video/adopt-existing.vtt

@@ -0,0 +1,150 @@
+WEBVTT
+
+1
+00:00:00.500 --> 00:00:06.112
+Drift is the silent killer of AI-written code — locally right, globally wrong.
+
+2
+00:00:06.112 --> 00:00:08.990
+MetaObjects turns it into a build error.
+
+3
+00:00:08.990 --> 00:00:10.429
+This is meta verify.
+
+4
+00:00:11.829 --> 00:00:13.123
+Here's one in action.
+
+5
+00:00:13.123 --> 00:00:18.854
+An agent edited a generated file, and one command caught it — exit one, before it could ship.
+
+6
+00:00:18.854 --> 00:00:22.243
+Let me show you how this works across your whole stack.
+
+7
+00:00:23.643 --> 00:00:27.737
+Meta verify checks one thing: does everything still agree with the model?
+
+8
+00:00:27.737 --> 00:00:32.504
+It does it across three surfaces — your code, your prompts, and your database schema.
+
+9
+00:00:32.504 --> 00:00:34.579
+Drift on any of them fails the build.
+
+10
+00:00:35.979 --> 00:00:38.266
+Before we run it, here's that one model.
+
+11
+00:00:38.266 --> 00:00:44.897
+The Task entity carries its validators right on the fields — that drives the code, and its source drives the schema.
+
+12
+00:00:44.897 --> 00:00:49.071
+The prompt has a typed payload and a template — that's the third surface.
+
+13
+00:00:49.071 --> 00:00:56.045
+And look at the references between them: the payload extends a real Task field, and the template points at a real payload.
+
+14
+00:00:56.045 --> 00:01:00.618
+Those are enforced — rename or delete the target, and the model won't even load.
+
+15
+00:01:00.618 --> 00:01:02.905
+So the model can't drift against itself.
+
+16
+00:01:04.305 --> 00:01:05.530
+Surface one: your code.
+
+17
+00:01:05.530 --> 00:01:09.258
+Verify regenerates from the model and compares it to what's committed.
+
+18
+00:01:09.258 --> 00:01:13.944
+The moment an agent hand-edits a generated file, it no longer matches — drift, exit one.
+
+19
+00:01:15.344 --> 00:01:17.013
+Surface two: your prompts.
+
+20
+00:01:17.013 --> 00:01:21.509
+Every variable in a prompt template has to exist on its typed payload.
+
+21
+00:01:21.509 --> 00:01:29.215
+Reference a field that isn't there — say, after a rename — and the build fails, instead of the prompt quietly degrading.
+
+22
+00:01:30.615 --> 00:01:32.230
+Surface three: your schema.
+
+23
+00:01:32.230 --> 00:01:35.221
+Verify diffs the model against your live database.
+
+24
+00:01:35.221 --> 00:01:42.341
+A column that drifted out of band — dropped, renamed, or added by hand — gets caught before it bites you in production.
+
+25
+00:01:43.741 --> 00:01:47.409
+When everything's in sync, one command says so.
+
+26
+00:01:47.409 --> 00:01:51.389
+Code, prompts, and schema all agree with the model.
+
+27
+00:01:51.389 --> 00:01:52.794
+Green means green.
+
+28
+00:01:54.194 --> 00:01:57.928
+Put that one line in your C I, and drift can't merge.
+
+29
+00:01:57.928 --> 00:02:06.452
+A pull request that diverges from the model fails the check — so an agent has to change the model first, then regenerate.
+
+30
+00:02:06.452 --> 00:02:08.988
+The model stays the source of truth.
+
+31
+00:02:10.388 --> 00:02:11.966
+That's the whole idea.
+
+32
+00:02:11.966 --> 00:02:18.637
+AI code is locally coherent and globally divergent — drift you can't see by reading one file.
+
+33
+00:02:18.637 --> 00:02:24.518
+Meta verify checks three surfaces against one model, and any mismatch is exit one.
+
+34
+00:02:24.518 --> 00:02:28.104
+The AI writes the code; the model keeps it honest.
+
+35
+00:02:29.504 --> 00:02:33.399
+Add meta verify to your build, and make drift a compile error.
+
+36
+00:02:33.399 --> 00:02:37.733
+This is part of the MetaObjects series — more at metaobjects dot dev.
+
+37
+00:02:37.733 --> 00:02:38.989
+Thanks for watching.
+