Hour audit: 2026-09-21T00
back to the files for this hour · how the archive is audited
Every number on this page is a stored measurement read from this hour's own records: its
manifest.json, its witness
statistics sidecar, and the corpus attestation. Nothing here is computed from the served
bytes at the time you load the page, so no line below claims the bytes are correct. The
digest and the one command that checks them are printed instead.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: g. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-21T00 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T00:00:00.000017917+00:00 · last event 2026-09-21T00:59:59.999795742+00:00
VOLUME 114,525,428 rows · 1,177,222,574 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 114,450,513 · f: 114,432,249 · e: 114,404,165 · h: 113,295,616 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 108,546,029 (94.78%) · f: 249,095 (0.22%) · e: 383,717 (0.34%) · h: 5,346,587 (4.67%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 114,525,428 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 17346b648c305c9071fe00e471964088ba04e956f115ea031166db4748d542b6
the corpus checksum ledger names this file with the same digest
joined 114,526,519 to merged 114,525,428, minus 1,091 (minus 0.0010%)
boundary drops 1,091 · guard cache
SIDECARS none: this hour's manifest has no v31 key. The v3.1 sidecars are optional, and hours before them have none
MARKETS not measured (the per-hour market census runs on the capture host and its output is not published per hour)
HISTORY merged 2026-09-21T05:08:34Z as cefh
layout union-event-sorted-v1
re-merges not measured (the merge ledger records the merge that produced this file, not the history of attempts)
supersessions not measured (supersession is recorded per corpus in the storage registry, not in the hour manifest)
CHECKS 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.The words in this report
Each line in the CHECKS block states what was found, not what was
hoped for: a check that passes is named for the thing that is true, and a check that does
not is renamed to the thing that is wrong. So FINDING never sits beside a
sentence asserting the opposite of the one below it.
The report above is fixed-width text, so nothing in it can be clicked. The same terms are linked here instead. Its verdict is a statement about minutes and nothing else. The row it reports comes from this hour's own manifest and its witness-statistics sidecar, and the completeness line comes from the corpus attestation. The gap between the joined and merged counts is deduplication, not loss, and the boundary drops are the duplicates discarded at the seam with the hour before. Where the history line names a supersession, this hour was rebuilt to a better state after it was first published. The precision is the timestamp resolution these files carry.
Detail
The same records, per product. A product holding no rows renders its zero rather than
being dropped: dropped and empty are indistinguishable to a reader, and only one of them is
a defect. A cell reading not meas. is one nothing published, which is a third
thing again and never a zero.
The class column is the merger's own verdict for that product, and it is
keyed to CONTRIBUTION rather than presence. FULL means every machine expected to
be capturing this hour delivered rows for that product; PARTIAL means some did
and some did not; SINGLE-BY-DESIGN means only one machine was ever expected, and
SINGLE-BY-DEFECT means several were and one delivered. So PARTIAL
here is a statement about the fleet, not about the product being damaged or truncated: the
rows that are present are whole.
PRODUCT rows bytes row groups sha256 best_bid_ask 11,765,572 132,640,454 0-44 985728923b262ec134774ea932bbd4fafefebc7a4abb700b52c2bd2bdb2bebec book 168,708 17,513,376 45-45 27a2d1cb3d6b3bcc4fbfd29e67d461c2ea13896949dd91ac1d3cdb72dbe9788a last_trade_price 62,720 3,556,390 46-46 b6e42601dd268f3cde2015cc9cb561a2e6e63dee9063ccd05ec04ece865cc8b6 market_resolved 2,309 376,294 47-47 9e5b016d110bdafdade3463d4b91f4acce2fc4a75aa92e2054b14591acafa382 new_market 1,649 187,706 48-48 a8bef8ee92351784046a591e107c5a96064167b59c5c2ef546ffca3893791896 price_change 102,520,394 1,021,498,991 49-440 885b4b258ab709dd48da5a1f36371135395c036def298f474370444f21a54801 tick_size_change 4,076 147,316 441-441 e8e7cebfb21e8622570ffb8bace3a1e41497cec6c78aaf8158333ba6c1a25e92 EVENT MIX count share price_change 102,520,394 89.52% best_bid_ask 11,765,572 10.27% book 168,708 0.15% last_trade_price 62,720 0.05% tick_size_change 4,076 <0.01% market_resolved 2,309 <0.01% new_market 1,649 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,765,662 11,765,572 90 74,066 PARTIAL book 168,710 168,708 2 22,571 PARTIAL last_trade_price 62,720 62,720 0 4,047 PARTIAL market_resolved 2,310 2,309 1 2,302 PARTIAL new_market 1,649 1,649 0 1,288 PARTIAL price_change 102,521,392 102,520,394 998 119,381 PARTIAL tick_size_change 4,076 4,076 0 1,019 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,764,736 11,225,528 5ms 12ms 89ms 5.1s 0 transport_latency_assumed best_bid_ask e 11,763,887 31,538 40ms 50ms 161ms 13.0s 0 transport_latency_assumed best_bid_ask f 11,763,848 14,831 46ms 57ms 171ms 17.1s 0 transport_latency_assumed best_bid_ask h 11,703,544 493,675 18ms 34ms 142ms 38.8s 0 transport_latency_assumed book c 140,042 130,844 6ms 497ms 5.3d 95.6d 0 book_staleness book e 134,350 7,697 43ms 255ms 9.7h 95.6d 0 book_staleness book f 134,541 7,755 49ms 208ms 10.7h 95.6d 0 book_staleness book h 140,559 22,412 21ms 5.5s 10.6d 95.6d 0 book_staleness last_trade_price c 62,612 58,430 5ms 19ms 175ms 1.3s 0 transport_latency_assumed last_trade_price e 62,537 292 42ms 102ms 1.2s 13.0s 0 transport_latency_assumed last_trade_price f 62,483 189 48ms 103ms 709ms 17.1s 0 transport_latency_assumed last_trade_price h 61,920 3,809 19ms 49ms 223ms 7.4s 0 transport_latency_assumed market_resolved c 2,301 2,112 5ms 18ms 53.9s 57.9s 0 transport_latency_assumed market_resolved e 2,275 4 41ms 120ms 55.6s 59.2s 0 transport_latency_assumed market_resolved f 2,275 2 47ms 127ms 55.9s 59.3s 0 transport_latency_assumed market_resolved h 2,297 191 18ms 72ms 50.4s 1.4min 0 transport_latency_assumed new_market c 1,288 960 12.3s 4.9h 10.1h 21.8h 0 transport_latency_assumed new_market e 1,288 152 11.1s 4.9h 10.1h 21.8h 0 transport_latency_assumed new_market f 1,288 204 11.5s 4.9h 10.1h 21.8h 0 transport_latency_assumed new_market h 1,288 333 13.4s 4.9h 10.1h 21.8h 0 transport_latency_assumed price_change c 102,475,458 97,124,243 5ms 14ms 113ms 6.2s 0 transport_latency_assumed price_change e 102,435,752 344,018 41ms 56ms 290ms 13.0s 0 transport_latency_assumed price_change f 102,463,738 226,114 47ms 63ms 259ms 17.3s 0 transport_latency_assumed price_change h 101,381,960 4,826,019 18ms 37ms 161ms 39.1s 0 transport_latency_assumed tick_size_change c 4,076 3,912 5ms 9ms 65ms 245ms 0 transport_latency_assumed tick_size_change e 4,076 16 40ms 46ms 123ms 319ms 0 transport_latency_assumed tick_size_change f 4,076 not meas. 46ms 56ms 147ms 487ms 0 transport_latency_assumed tick_size_change h 4,048 148 18ms 26ms 83ms 257ms 0 transport_latency_assumed
Captured and supplied are different numbers
Captured is how many rows each machine's own feed carried. Redundant capture means these OVERLAP, heavily and on purpose, so they do not partition the file and their sum is larger than it. Two machines each capturing nearly every event is the archive working, not double counting.
Supplied is how many rows of the merged file actually came from that machine. This one does partition: it sums to the file's row count exactly. But it is decided by the merge's tie-break, so a machine can capture almost everything and supply almost nothing. Read alone, either number tells a false story about the fleet, which is why both are printed and neither is called "the witness share".
What the skew columns mean
Arrival skew is the receipt timestamp minus the venue timestamp, in milliseconds. For six of the seven products the sidecar interprets it as transport latency, and marks that interpretation assumed: it rests on the venue timestamp being emit time, which we cannot verify from outside.
book is not latency and must not be read as latency. Its
venue timestamp is the last time the book changed, so the sidecar interprets it as book
staleness and warns in its own note that large values mean a quiet book rather than slow
transport. Its maximum runs to weeks for that reason. This is why the table above gives a
row per product per machine and never one figure for the hour: percentiles do not average,
and these seven do not measure the same quantity.
Check it yourself
The digest above is a claim. This is how you refuse to take our word for it:
curl -O https://archive.pendulumflow.com/v3/2026-09-21/00/2026-09-21T00.parquet sha256sum 2026-09-21T00.parquet # compare with the sha256 line in the report above
A range digest certifies bytes. That those bytes are the product the manifest names comes from the manifest, which is why both are published and both are checkable.