styxx shelf — a re-derivation built to run somewhere that is not the box

darkflobi https://fathom-lab.github.io/styxx/ledger/

run 2026-11-08T21:27:15Z → 2026-11-08T21:27:21Z on not the action (a local run), shelf 0.1.0, node v24.13.0, date 2026-11-08. full record: reports/darkflobi/2026-11-08.json (latest).

no check failed

(0 anchors pending, 1 of 15 days with no anchor, 5 lines after the last bitcoin-attested head)

chain

re-derives: 729 published lines (730 file lines), head 0e5a698dece0bb33764c5202a03745a140a6ef66dba7bbcbc3896842795e152f, kinds {"started":22,"send":344,"delivered":349,"anchor":14}, withheld 5 (bridged 5), the ledger's own anchor lines in chain 14 of 14, pinned by a posted head 692 of 729 lines, not pinned because of a withheld line 32, after the last posted head 5.

the row's SNAPSHOTS.jsonl last line names the fetched ledger's sha256.

vectors

10 of 10 answered as the row's vectors file says (pinned runner, pinned verifier).

ok   identity
ok   rewrite-one-field
ok   rewrite-prev
ok   drop-a-line
ok   drop-a-line-withheld
ok   drop-a-line-withheld-wrong-digest
ok   cr-byte
ok   duplicate-key
ok   truncate-last-line
ok   flip-and-rechain
10 of 10 vectors answered as the file says

verifier drift

no: the row's published verify.js and check_ledger.cjs hash to the pinned copies.

anchors — verified 14 of 14, pending 0 of 14, in chain 14 of 14

"verified" means: the fetched text hashes to what the index says, the proof is over those bytes, the text's head and seq are in the fetched chain, and every bitcoin attestation's merkle path ends at the block header that 2 of 2 explorers return (https://blockstream.info/api, https://mempool.space/api). "pending" means the proof holds calendar promises only; the shelf does not ask the calendars for a row's proof, and a proof pending for more than 7 days after its anchor date is a failed check. "explorer unreachable" is an explorer that did not answer, not a header that disagreed; both leave the anchor not verified.

index against the ledger's own anchor lines: 14 of 14 ledger anchor lines are in the index, 14 of 14 index entries have a ledger anchor line.

gaps — 1 of 15 days

window 2026-10-24 .. 2026-11-07 (America/New_York; the end is the day before the run day in America/New_York (2026-11-08)): no anchor for 2026-11-06. a gap is a day with neither an index entry nor a ledger anchor line; printed, not failed.

append-only

extends the previous fetch (2026-11-08: 1233153 bytes, 729 lines) by +0 bytes, +0 lines

no anchor's text, proof or block changed since the previous fetch (14 compared).

lines after the last bitcoin-attested head: 5 of 729 (anchor 2026-11-07 pins seq 729, block 975028, by explorers). those lines are pinned by nothing outside the lab tonight.

the previous fetch is history/darkflobi/latest.json, a record in this repository (see "what this is not").

the shelf's own stamps

--stamp-self not passed: the shelf's own report is not stamped and earlier stamps are not upgraded on this run

fetched

plus 28 anchor files (in the json record).

rerun

git clone https://github.com/fathom-lab/styxx-shelf && cd styxx-shelf && npm ci && node shelf.mjs --row darkflobi --out ./docs --date 2026-11-08 --through 2026-11-07

by hand, inside the clone: 39 commands (every curl and every node line) are listed under commands in the json record. the rerun carries --date and --through so the gap window is the recorded one.

ledgers read by url — 2 rows, 2 of 2 the lab's own; outside ledgers read: 0; v1 rows 0 of 2; withdrawn 0 of 2

who wrote each ledger is the row's written_by. no row names a ledger written outside the lab: the 2 of 2 rows written by the lab (darkflobi, red) show the shelf reading the lab's own ledgers by url, not an outside one. since styxx-ledger f29ae3d (2026-11-09) the census scorer reads condition (c) from the shelf: it fetches the report a section 15 shelf read line names, only from under https://fathom-lab.github.io/styxx-shelf/reports/reads/ (since 94e4181; a report on any other host fails (c) unfetched), and checks it against the registration and the chain. (c) holds for an outside window only after the shelf has read that ledger and its report is kept here.

the register outside_ledgers.json lists the ledgers the shelf reads with shelf_read.cjs, one url each, protocol v0 or v1. the shelf is the lab's: a ledger listed here, whoever wrote it, is read by the lab's shelf, with the lab's copy of the verifier and the lab's code, and the reports below are the lab's. a report says whether the bytes at the url re-derive and where the earliest anchor that holds was looked for; it says nothing about the agent behind a ledger, or whether a line records what happened. rows are appended by the lab in a dated commit and never edited; a row taken off gets withdrawn_at and stays. a v1 row for an outside operator's ledger is added when that operator has published one and asks: how to ask, what the lab does and the url to paste are under get your ledger read; the places an anchor may be posted, under anchor places in the readme.

how old each read is: darkflobi: read 2026-11-09T14:37:14Z, 5 h 38 min before this page was written, 787 lines; the nightly row darkflobi read the same url at 2026-11-08T21:27:15Z and counted 729 lines, 17 h 9 min before this read (+58 lines from the earlier count to the later: the ledger grows, so the two counts are two times, not two answers). red: read 2026-11-09T14:37:15Z, 5 h 38 min before this page was written, 107 lines; read from a shelf checkout with uncommitted changes (its shelf_commit says so).

every read here so far was written when the lab ran node shelf_read.cjs --row <name> by hand on its box; the workflow written for this repository runs it for every register row each night once the operator adds it (not in this repository as of 2026-11-09). every read is kept at reports/reads/<row>/<read_at with each : written ->.json and never rewritten; reports/<row>.json is the latest and is replaced by the next read. the census template's section 15 line (shelf read: <url> sha256 <64 hex> at <read_at>) names the kept copy. the report's fields: outside_report_schema.json. the browser page fetches the ledger from its url and runs the same code (shelf_core.js and the verifiers below); it can read a host that allows a cross-origin read (github pages hosts do).

v1 rows run the kit's verifier as copied from styxx-ledger commit 838a003 (838a003fa4f65d8efdb185c88a951f74ac2366c9, https://github.com/fathom-lab/styxx-ledger), 5 files, none changed (v1/VENDORED.json):

v0 rows run the shelf's pinned tools/verify.js (sha256 6bb1b6c4642d6251153d0a3bc6a30ac3fee9c6529cc0540291dbb38f983eba46), served to the browser as v0/verify.js.