site(video): captions + posters for the re-cuts; drop the pre-1.0.4 caveat

All five Pages-hosted VTTs and posters match the re-rendered mp4s now on the
Cloudflare site. The getting-started caveat ("Recorded before 1.0.4") is gone
— the cut itself is 1.0.4 now; its description drops forms/hooks/grid (never
generated in the new run) and says "drift fails the build instead of
shipping". The drift-detection heading stops saying "compile error" about the
gate — that phrase is retired positioning.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BHEQGNA9McKNBwDkesNMDC

Author: claude

www/video/adopt-existing-poster.png

@@ -17,110 +17,142 @@ You adopt it, incrementally.
 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.
+00:00:11.700 --> 00:00:14.446
+And the first step isn't even installing anything.
 
 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.
+00:00:14.446 --> 00:00:24.444
+One line to your coding agent runs a fit assessment against your actual repo — read only, propose only — and it comes back with a verdict for your app, including a no when it's a no.
 
 7
-00:00:23.608 --> 00:00:26.815
-There's no magic import — and honestly, that's fine.
+00:00:24.444 --> 00:00:25.598
+Let's say it's a yes.
 
 8
-00:00:26.815 --> 00:00:29.591
-You describe one existing entity in metadata.
+00:00:25.598 --> 00:00:25.982
+Onward.
 
 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.
+00:00:27.382 --> 00:00:32.148
+This is a real app — real tables, a real database, none of it built by MetaObjects.
 
 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.
+00:00:32.148 --> 00:00:37.890
+We're going to point MetaObjects at one table, and get typed code for it, without touching the rest.
 
 11
-00:00:46.288 --> 00:00:50.407
-Here's that one table described — matching the columns you already have.
+00:00:39.290 --> 00:00:42.498
+There's no magic import — and honestly, that's fine.
 
 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.
+00:00:42.498 --> 00:00:45.274
+You describe one existing entity in metadata.
 
 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.
+00:00:45.274 --> 00:00:54.773
+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.
 
 14
-00:01:02.879 --> 00:01:07.227
-That's validation you get to layer on, that the raw database never enforced.
+00:00:54.773 --> 00:01:00.571
+Adopting an existing app is a judgment call, not a one-click button — so start with one table.
 
 15
-00:01:08.627 --> 00:01:09.603
-Then meta gen.
+00:01:01.971 --> 00:01:06.090
+Here's that one table described — matching the columns you already have.
 
 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.
+00:01:06.090 --> 00:01:11.525
+The source points at your existing customers table, and fullName maps to your full name column.
 
 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.
+00:01:11.525 --> 00:01:18.562
+And look at the email field: validators live right on it, as child metadata — a required check and an email-format pattern.
 
 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.
+00:01:18.562 --> 00:01:22.909
+That's validation you get to layer on, that the raw database never enforced.
 
 19
-00:01:32.672 --> 00:01:35.069
-Typed, idiomatic, ready to use right now.
+00:01:24.309 --> 00:01:26.212
+Now — what should this generate?
 
 20
-00:01:36.469 --> 00:01:40.232
-Run verify against your live database, and it tells you exactly where you stand.
+00:01:26.212 --> 00:01:28.114
+MetaObjects doesn't decide that.
 
 21
-00:01:40.232 --> 00:01:41.550
-Customers matches the model.
+00:01:28.114 --> 00:01:33.642
+Claude asks the catalog, and takes what the app needs: entity, queries, routes, and a barrel.
 
 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.
+00:01:33.642 --> 00:01:38.755
+Meta eject copies each one into your repo — plain TypeScript generators, yours to own.
 
 23
-00:01:46.949 --> 00:01:48.605
-This is low-risk by design.
+00:01:40.155 --> 00:01:41.130
+Then meta gen.
 
 24
-00:01:48.605 --> 00:01:54.373
-The generated code runs with no MetaObjects dependency, so adopting it commits you to nothing.
+00:01:41.130 --> 00:01:49.355
+You get a typed entity, queries, and routes for your existing table — generated alongside your app, not instead of it.
 
 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.
+00:01:50.755 --> 00:01:57.886
+And the generated code maps your real schema — Drizzle and Zod for your customers table, with fullName wired to full name.
 
 26
-00:02:03.994 --> 00:02:09.393
-That's adoption: describe one table, generate, adopt — no big rewrite, no magic.
+00:01:57.886 --> 00:02:04.200
+And the validators you layered on come through too: the email format check is right there in the Zod schema.
 
 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.
+00:02:04.200 --> 00:02:06.596
+Typed, idiomatic, ready to use right now.
 
 28
-00:02:17.745 --> 00:02:20.295
-You don't have to start over to start.
+00:02:07.996 --> 00:02:11.760
+Run verify against your live database, and it tells you exactly where you stand.
 
 29
-00:02:20.295 --> 00:02:23.381
-Run meta init, describe a table, and meta gen.
+00:02:11.760 --> 00:02:13.077
+Customers matches the model.
 
 30
-00:02:23.381 --> 00:02:27.407
-That's the MetaObjects series — more at metaobjects dot dev.
+00:02:13.077 --> 00:02:17.076
+Orders isn't modeled yet — so that's your next table to adopt, whenever you're ready.
 
 31
-00:02:27.407 --> 00:02:28.749
+00:02:18.476 --> 00:02:20.004
+This is low-risk by design.
+
+32
+00:02:20.004 --> 00:02:29.223
+The generated entity module imports only Drizzle and Zod; the routes mount through one ordinary open-source package — so adopting it is reversible, table by table.
+
+33
+00:02:29.223 --> 00:02:35.106
+The rest of your app is untouched, and you keep your escape hatches for anything metadata can't express.
+
+34
+00:02:36.506 --> 00:02:44.305
+That's adoption: assess the fit, describe one table, choose your generators, generate, adopt — no big rewrite, no magic.
+
+35
+00:02:44.305 --> 00:02:50.999
+Then, table by table, the model becomes the spine, and meta verify keeps it honest as you grow into it.
+
+36
+00:02:52.399 --> 00:02:55.003
+You don't have to start over to start.
+
+37
+00:02:55.003 --> 00:03:00.347
+Have your agent assess the fit, run meta init, describe a table, and meta gen.
+
+38
+00:03:00.347 --> 00:03:04.185
+That's the MetaObjects series — more at metaobjects.dev.
+
+39
+00:03:04.185 --> 00:03:05.555
 Thanks for watching.