One Rulebook. Every Substrate. On Camera.
Every video below is produced from a single Effortless Rulebook — the same JSON that drives the story is the thing you can download and read.
Foundations — One Rulebook, Every Substrate
The origin set. Each film takes one idea — a computed name, transitive closure, a famous paradox, plain-English rules, a thin client — and shows it falling out of a single rulebook, in a real substrate, with real output. Standalone episodes rather than a sequence; watch any one on its own.
The Full Name Demo
One computed field — a full name — travels from a rulebook into a real Postgres database and a running app, without anyone writing the code that computes it.
Talismans — Special Solutions
A real production-deployment workflow, modeled once and rendered by the substrate that already knows the rules.
Transitive Closure, Made Obvious
A ~3-minute plain-English explainer for transitive closure, using a live production workflow as the test case — with counter-examples that do the real teaching.
The Witnesses
Two witnesses, one table, and the question of who is allowed to see what.
Causal Architecture
Why two clinicians reading the same chart reach opposite conclusions — and what a rulebook does about it.
Simpson's Paradox
The same data, split two ways, telling two opposite stories — and the rulebook that keeps both honest.
RuleSpeak — Rules You Can Read
A rule written once, rendered as plain English and plain German, from the same single source.
The Thin Client
Describe the business in a rulebook, build, and watch the app compute nothing at all.
The Cast
The reusable cast and media library that every film in this producer shares.
Row-Level Security — Who Sees Which Rows
A five-part course. Bob owns a bike shop; Gemma makes sure it is secure. By the end, every role has its own schema — views trimmed across (only the columns that role may see) and down (only the rows they are allowed) — enforced by the database itself, generated from one rulebook, on more than one engine, editable in a form.
What Is Row-Level Security?
Bob owns a bike shop. Not everyone who works there should see every row — here is what that actually means.
RLS, Generated
The same access rules, declared once in a rulebook and enforced by the database itself.
Under The Covers
What the generator actually emitted, and why the policy lives in the engine rather than the app.
Same Rules, Second Engine
One rulebook, a second database engine, and the identical access behavior falling out of both.
Editing The Rules
Change who sees what in a form, rebuild, and watch every role's schema move with it.