One notebook, whole
What a flip notebook actually looks like
This notebook was built by the flip CLI while this site was built —
the same commands an agent runs while a person directs the work in conversation,
never touching the CLI itself. Every panel below is generated from the
notebook's own files through the flip-render/2 projection: nothing
on this page is hand-authored.
Manifest
Custody & judgment
Sources
What this notebook holds custody of, and the judgment recorded about each piece — independence and basis are a description, never a score; the grade letter is derived from them.
| id | title | grade | independence | basis | freshness | provenance | custody |
|---|
What this notebook asserts
Claims
A claim enters asserted. It cannot call
itself verified until the corroboration bar is met — mechanically,
not by anyone insisting.
| id | claim | status | load-bearing | value | sources | corroboration | verifications |
|---|
Open threads
Questions
An open question without a watching surface is a wish,
not a plan — flip marks it unwatched rather than pretending it is
covered.
| id | question | status | watches |
|---|
Resolved forks
Decisions
The what is recoverable from git history; the why is not. Rejected alternatives are part of the record, not a footnote.
| id | question → decision | rejected alternatives |
|---|
Who did the work
Sessions
One page per working episode, human or agent, stamped in UTC — the reasoning chain is part of the bundle, not reconstructed later from a chat log.
| actor | model | started | goal |
|---|
Standing predictions
Forecasts
A probability and a resolution date attached to an open question — present only when this notebook's profile tracks forecasts.
| question | probability / confidence | resolves by | status |
|---|
Newest first
Log tail
The last lines of the append-only work log — fetched X, ran Y, hit wall Z. Nothing is deleted to keep context small.
What this page is
Nothing above was typed by a person for this site. The notebook it renders was
scaffolded, sourced, graded, claimed, decided, and logged by the real
flip CLI during the site build — the
flipbook page steps through the same notebook one
command at a time; this page shows where all those commands land once the
notebook is whole. The projection itself is versioned: this page reads
flip-render/2, the contract flip export json
--render-version 2 emits, so a future contract bump cannot silently change
what a reader sees here without the build noticing first.