What the backup costs, and what it holds
You keep a record so someone who did not write it can read it. Two questions follow: what does keeping it online cost, and how much of what this machine holds can that someone recompute?
+The newest backupchain_verified false
Read off the newest backup's manifest. A break in the chain is printed with its named cause, never hidden; the rows that fall outside are counted below.
+What falls outside0 of 4,538 rows carry a licence stamp.
A reader of any record asks first what it leaves out. Here it is, off our own flight tape as committed at 648b0bb0d4.
0 of 4,538 rows carry a licence stamp.
4,538 rows carry none; 1,858 rows sit past the first cut in the file.
Why the rows carry no stamp, every reason with its count:
- 3,642 — no licence in the environment when the row was written (VNA_ENTITLEMENT_CLAIMS absent)
- 896 — this row was taped before C90 — no licence field on the signed row
The cuts, each named in the sidecar and retained, never re-linked:
- seq 2679 at line 2,681, 2026-09-23T14:26:57.429Z — second_writer (C514): row 778ff7e82ffe points at 2bfd8f829da2; the row before it is b715e89030c3.
- seq 1921 at line 3,582, 2026-09-24T17:15:57.564Z — seq_restart (C523): row 9b96bd98ae91 points at c5d449da4e27; the row before it is af88431c5f1e.
The newest rows with no stamp:
- seq 3872 · line 4,538 · turn · 2026-09-30T19:26:54.536Z · 7b6c4260089c · no licence in the environment when the row was written (VNA_ENTITLEMENT_CLAIMS absent)
- seq 3871 · line 4,537 · commit · 2026-09-30T19:26:05.419Z · 7f5ad9999526 · no licence in the environment when the row was written (VNA_ENTITLEMENT_CLAIMS absent)
- seq 3870 · line 4,536 · turn · 2026-09-30T19:24:40.624Z · d1d26159b220 · no licence in the environment when the row was written (VNA_ENTITLEMENT_CLAIMS absent)
- seq 3869 · line 4,535 · commit · 2026-09-30T19:24:32.634Z · ed733b03d9a2 · no licence in the environment when the row was written (VNA_ENTITLEMENT_CLAIMS absent)
- seq 3868 · line 4,534 · turn · 2026-09-30T19:23:49.029Z · bdea2573fd09 · no licence in the environment when the row was written (VNA_ENTITLEMENT_CLAIMS absent)
- seq 3867 · line 4,533 · turn · 2026-09-30T19:20:16.749Z · 6846a9356532 · no licence in the environment when the row was written (VNA_ENTITLEMENT_CLAIMS absent)
Sufficient for: which rows of this tape a wording keyed on a licence stamp and an unbroken chain can read, and where the chain is cut. NOT sufficient for: whether the work on any row, inside or outside, was good; whether the work was good is undecidable (Rice, 1953).
You don’t have to take my word for it: node scripts/vna/outside-the-wording.mjs --snapshot public/backup/outside-the-wording.json recomputes this card from git show 648b0bb0d4:data/vna/flight-tape.ndjson (sha256 a364eeb3d335…), and node scripts/vna/flight-tape.mjs --verify returns the seal.
A row with no stamp, or past a break, is outside what a wording keyed on stamped, chained rows reads.
verify() returns ok false: 2 cuts, each named and sealed in the sidecar (seq 2679 second_writer, seq 1921 seq_restart). It walks past a named cut and verifies each side as its own segment; it never re-links one.
+What it costs, and what can be recomputed$0.0016 a month to hold · 24 backups posted
Left: the bytes each backup posted and the bytes held online so far. Right: per tape, the rows on this machine, the rows online, and the rows the page draws. Each side opens below.
+Left bank — what my record costs to keep$0.0016 a month · $0.0003 per full read
24 backups posted; every one is kept whole under its own sha, so 74.8 MB is held online. At the list rate that is $0.0016 a month to hold, and one full read of the newest archive (3.3 MB) costs $0.0003.
The newest backup carried 28 new flight-tape rows and re-sent the rest: 116,411 bytes on the wire per new row.
Rate: Supabase Storage (the backups bucket — src/lib/backup/receive-env.mjs) — storage $0.0213/GB-month (https://supabase.com/docs/guides/platform/manage-your-usage/storage-size), egress $0.09/GB uncached (https://supabase.com/docs/guides/platform/manage-your-usage/egress), read 2026-10-04. That prices the bytes, not the bill: the Pro plan includes 100 GB of storage and 250 GB of egress.
74.8 MB held online, 24 backups, each kept whole under its own sha.
+Right bank — what share of the record can be recomputedwalk tape: 302,979 rows here, none online
Every row of the flight tape rides, in spec or not; the archive does not filter by spec. The walk tape is the local diary: 302,979 rows on this machine, none online. The page then draws only the newest window of what is online.
- fleet: controller-tick: 12,116 local · 2,000 online · 300 drawn (the newest 300 rows the slider scrubs (C565o))
- fleet: llm-local: 1 local · 1 online · 1 drawn (the newest 300 rows the slider scrubs (C565o))
- fleet: llm-steer-runner: 20 local · 20 online · 20 drawn (the newest 300 rows the slider scrubs (C565o))
- walk-tape: 302,979 local · local only, not online · 0 drawn (not online, so nothing to draw)
- attestations: 2,135 local · 2,060 online · counted, not drawn (read whole for the page's counts, not drawn row by row)
- flight-tape: 7,404 local · 6,907 online · 60 drawn (the newest 60 ticks per chart (C565r); every count reads all of them)
- steer-ab-tokens: 1,946 local · 1,946 online · counted, not drawn (read whole for the page's counts, not drawn row by row)
- token-savings-daily: 82 local · 82 online · counted, not drawn (read whole for the page's counts, not drawn row by row)
Sufficient for: what keeping this record online costs at the store’s list rate, and what share of the local record a third party can recompute from what was posted. NOT sufficient for: the invoice (the plan’s included quota means the bill today is zero), or which rows were in scope — every row rides, in spec or not; whether the work was good is undecidable (Rice, 1953).
You don’t have to take my word for it: node scripts/vna/backup-cost.mjs recomputes every figure here from the archives on disk, and each archive’s sha256 is its name.