The flipbook
How a notebook comes together
Sixteen frames, seventeen real commands. Each one shows what was run, which files it changed, and the record that resulted. The story is a question that starts with somebody else's evidence and ends with a claim that earned the right to call itself verified.
Every frame on this page was produced by running the flip CLI against a scratch notebook when the site was built — no screenshots, no hand-written output. The research subject is invented: a fictional baking club and a kitchen log, chosen so that no frame could be mistaken for a real finding.
— · step 1 of 16
Loading the frames…
This page is driven by data generated at build time. If it does not load, the commands are all listed in the repository's quickstart.
The notebook on disk
What was recorded
What the sixteen frames are meant to show
Not that flip is easy to use — that the rules are enforced. The frame worth pausing on is the refusal. A claim backed by one secondary source asks to be marked verified and the CLI declines, with an exit code, because the profile says a notebook headed for publication needs two independent judged sources or a grade-A primary. Nothing about that is advisory.
The second thing worth noticing is how little of it is flip's doing. What you are left with at frame sixteen is a directory of markdown files that any editor can open, plus two append-only ledgers. The discipline lives in the format; the CLI is just the thing that keeps you honest while you write it.