Hour audit: 2026-09-20T01
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: f. 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-20T01 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-20T01:00:00.000085441+00:00 · last event 2026-09-20T01:59:59.999786226+00:00
VOLUME 144,499,155 rows · 1,583,448,367 bytes (1.47 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured e: 137,075,576 · h: 136,736,417 · c: 125,974,338 · g: 115,621,528 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 4,210,582 (2.91%) · h: 20,379,276 (14.10%) · c: 118,354,399 (81.91%) · g: 1,554,898 (1.08%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 6148e55a582f82d315245efca613bdcc3b56d6ac6c1d0d87f68bdb18c4503494
the corpus checksum ledger names this file with the same digest
joined 144,516,406 to merged 144,499,155, minus 17,251 (minus 0.0119%)
boundary drops 17,251 · 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-20T07:34:49Z as cegh
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 17,738,398 197,603,563 0-67 d8ad4683da8837cd9a20a46e68796f1f515a8c6a700d804eff6e3cae45f1baf8 book 2,498,288 104,119,036 68-77 1c6deb9cbdca5addc927d4a7a4636463bcdc33e48ea85d2772a015cc780be32f last_trade_price 57,892 3,396,688 78-78 9e0a16d7b68880b7eecb2650d3902b03442658948de7bcb3328b10591b448242 market_resolved 5,473 674,639 79-79 26cb80e569662f1df879e6436401ac1a49a1d28e6bda1eec55ce583882721654 new_market 1,160 114,544 80-80 94a6d98e43c11dc7d156795d079f5bee67d3a43ba1a78e8811c0014c6a7a37d6 price_change 124,187,004 1,275,503,922 81-554 37a5b624e407181543f1b5b97448d17642e1c683701c9a67e2f284ce2d7617d8 tick_size_change 10,940 399,061 555-555 194d7dfe0391a0d6c49e1a826c9b07ad5b627b37b32518c28b0bb821ff01e0ca EVENT MIX count share price_change 124,187,004 85.94% best_bid_ask 17,738,398 12.28% book 2,498,288 1.73% last_trade_price 57,892 0.04% tick_size_change 10,940 <0.01% market_resolved 5,473 <0.01% new_market 1,160 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 17,738,883 17,738,398 485 87,601 PARTIAL book 2,511,306 2,498,288 13,018 188,293 PARTIAL last_trade_price 57,900 57,892 8 4,530 PARTIAL market_resolved 5,473 5,473 0 4,089 PARTIAL new_market 1,160 1,160 0 724 PARTIAL price_change 124,190,744 124,187,004 3,740 146,092 PARTIAL tick_size_change 10,940 10,940 0 2,735 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 15,617,131 14,791,838 5ms 14ms 98ms 2.7s 0 transport_latency_assumed best_bid_ask e 17,025,961 500,606 41ms 52ms 157ms 10.1s 0 transport_latency_assumed best_bid_ask g 14,240,468 6,583 80ms 99ms 301ms 10.0s 0 transport_latency_assumed best_bid_ask h 16,976,939 2,439,371 17ms 36ms 123ms 24.8s 0 transport_latency_assumed book c 1,308,978 746,840 5.5min 1.4d 39.3d 113.1d 0 book_staleness book e 546,218 76,741 2.9min 1.1d 38.3d 113.1d 0 book_staleness book g 1,952,199 1,493,546 6.8min 1.4d 39.3d 113.2d 0 book_staleness book h 527,478 181,161 2.7min 21.8h 38.2d 113.1d 0 book_staleness last_trade_price c 50,853 47,032 6ms 23ms 199ms 1.1s 0 transport_latency_assumed last_trade_price e 54,821 1,973 43ms 102ms 848ms 10.1s 0 transport_latency_assumed last_trade_price g 44,718 55 84ms 213ms 2.4s 9.7s 0 transport_latency_assumed last_trade_price h 55,039 8,832 18ms 49ms 269ms 6.7s 0 transport_latency_assumed market_resolved c 4,316 4,155 5ms 4.8min 10.5min 10.8min 0 transport_latency_assumed market_resolved e 3,850 70 44ms 121ms 400ms 2.5min 0 transport_latency_assumed market_resolved g 4,377 689 120ms 9.8min 17.5min 17.9min 0 transport_latency_assumed market_resolved h 3,957 559 25ms 63ms 5.6min 5.9min 0 transport_latency_assumed new_market c 772 546 69ms 4.1min 1.4h 6.6h 0 transport_latency_assumed new_market e 723 155 143ms 21.3s 51.4s 3.8h 0 transport_latency_assumed new_market g 851 141 288ms 10.9min 3.8h 6.7h 0 transport_latency_assumed new_market h 726 318 91ms 16.2s 56.7s 4.9h 0 transport_latency_assumed price_change c 108,982,628 102,755,100 5ms 16ms 110ms 3.1s 0 transport_latency_assumed price_change e 119,433,575 3,630,604 41ms 57ms 215ms 10.5s 0 transport_latency_assumed price_change g 99,370,687 53,876 81ms 106ms 433ms 10.5s 0 transport_latency_assumed price_change h 119,161,798 17,747,424 18ms 39ms 147ms 26.4s 0 transport_latency_assumed tick_size_change c 9,660 8,888 5ms 21ms 124ms 656ms 0 transport_latency_assumed tick_size_change e 10,428 433 41ms 57ms 155ms 397ms 0 transport_latency_assumed tick_size_change g 8,228 8 81ms 104ms 310ms 1.0s 0 transport_latency_assumed tick_size_change h 10,480 1,611 18ms 41ms 170ms 2.3s 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-20/01/2026-09-20T01.parquet sha256sum 2026-09-20T01.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.