Hour audit: 2026-09-24T21
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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-24T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T21:00:00.000845874+00:00 · last event 2026-09-24T21:59:59.997539058+00:00
VOLUME 113,049,995 rows · 1,269,282,041 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 111,104,238 · g: 109,926,553 · k: 107,046,453 · i: 106,766,850 · c: 92,229,626 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 6,846,938 (6.06%) · g: 103,386 (0.09%) · k: 21,968,158 (19.43%) · i: 5,952,475 (5.27%) · c: 78,179,038 (69.15%) (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 113,049,995 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cd0f890f7887f22abd871b85be3ca1d448bff681a279ed787170f3d1f8dda859
the corpus checksum ledger names this file with the same digest
joined 113,058,018 to merged 113,049,995, minus 8,023 (minus 0.0071%)
boundary drops 8,023 · 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-24T23:04:02Z as cghik
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 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 12,191,107 149,270,834 0-46 09234222a591837c47edcf3d25c99529700583497dea517913a5a58ba7d02f17 book 2,119,954 93,701,753 47-55 78dceb829e2469ace7e57b1b22d8d166d841c74cf765c303bccb21faa6b7a2af last_trade_price 58,974 3,341,887 56-56 2d07b19e44658f5265c0b9833d4ff50eb1a78b408b255a189f948f71ba21d7e2 market_resolved 2,835 291,794 57-57 251853729a85470443e6c5afb13648d3397117da50fbc8c366ea1123981ec900 new_market 13,485 1,586,706 58-58 3a42bdb71ccc04d08e14e683c0f270eece4f985eb5b9f01b5effcb767309855b price_change 98,660,320 1,019,675,911 59-435 33ac1ebad886d6c3a4a3ac47efba41a4df7ef030aa64df566a875c4925e4b081 tick_size_change 3,320 123,530 436-436 5cfe4c9ab4aa4a7d1c57b1645a2fe404c6f2f4d9393a3866280fb97a8a16c6f4 EVENT MIX count share price_change 98,660,320 87.27% best_bid_ask 12,191,107 10.78% book 2,119,954 1.88% last_trade_price 58,974 0.05% new_market 13,485 0.01% tick_size_change 3,320 <0.01% market_resolved 2,835 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,191,418 12,191,107 311 3,239 FULL book 2,125,503 2,119,954 5,549 187,701 FULL last_trade_price 58,975 58,974 1 449 FULL market_resolved 2,835 2,835 0 39 FULL new_market 13,485 13,485 0 225 FULL price_change 98,662,482 98,660,320 2,162 1,301 FULL tick_size_change 3,320 3,320 0 275 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,958,183 8,469,401 5ms 49ms 330ms 45.2s 0 transport_latency_assumed best_bid_ask g 12,155,994 6,449 86ms 327ms 1.3s 46.5s 0 transport_latency_assumed best_bid_ask h 12,188,295 724,102 19ms 83ms 923ms 50.6s 0 transport_latency_assumed best_bid_ask i 11,643,595 619,505 22ms 49ms 226ms 7.9s 0 transport_latency_assumed best_bid_ask k 11,709,922 2,371,650 13ms 42ms 307ms 58.1s 0 transport_latency_assumed book c 1,803,505 1,677,649 7.7min 5.3d 43.3d 118.0d 0 book_staleness book g 210,873 44,108 4.3s 2.0d 31.3d 110.2d 0 book_staleness book h 218,769 48,754 322ms 2.9h 22.8d 99.9d 0 book_staleness book i 651,239 222,448 4.0min 3.1d 33.4d 118.0d 0 book_staleness book k 606,285 126,995 3.4min 3.1d 33.3d 118.0d 0 book_staleness last_trade_price c 43,788 37,151 6ms 72ms 398ms 3.1s 0 transport_latency_assumed last_trade_price g 47,880 120 214ms 6.3s 23.0s 45.6s 0 transport_latency_assumed last_trade_price h 58,756 4,316 25ms 260ms 1.2s 23.8s 0 transport_latency_assumed last_trade_price i 55,445 2,546 34ms 354ms 1.3s 4.3s 0 transport_latency_assumed last_trade_price k 55,733 14,841 14ms 102ms 403ms 9.2s 0 transport_latency_assumed market_resolved c 2,186 1,846 23.0s 10.1min 12.3min 12.5min 0 transport_latency_assumed market_resolved g 1,739 65 93ms 20.7s 54.3s 57.1s 0 transport_latency_assumed market_resolved h 1,739 188 23ms 22.4s 55.4s 57.1s 0 transport_latency_assumed market_resolved i 1,738 117 24ms 28.9s 3.8min 4.6min 0 transport_latency_assumed market_resolved k 1,726 619 14ms 25.4s 52.0s 3.9min 0 transport_latency_assumed new_market c 11,141 5,512 79ms 3.1min 14.0min 29.5min 0 transport_latency_assumed new_market g 10,619 382 236ms 439ms 1.8min 2.5min 0 transport_latency_assumed new_market h 10,619 1,927 118ms 316ms 1.6min 2.6min 0 transport_latency_assumed new_market i 10,757 2,820 98ms 320ms 7.1min 8.4min 0 transport_latency_assumed new_market k 10,545 2,844 91ms 277ms 5.8min 7.1min 0 transport_latency_assumed price_change c 80,408,519 67,985,346 5ms 55ms 355ms 45.7s 0 transport_latency_assumed price_change g 97,496,128 52,262 90ms 455ms 9.8s 46.5s 0 transport_latency_assumed price_change h 98,622,740 6,067,466 19ms 99ms 946ms 50.9s 0 transport_latency_assumed price_change i 94,400,836 5,104,898 22ms 62ms 335ms 7.9s 0 transport_latency_assumed price_change k 94,658,994 19,450,348 13ms 51ms 325ms 58.1s 0 transport_latency_assumed tick_size_change c 2,304 2,133 5ms 11ms 233ms 446ms 0 transport_latency_assumed tick_size_change g 3,320 not meas. 84ms 280ms 760ms 1.4s 0 transport_latency_assumed tick_size_change h 3,320 185 19ms 53ms 554ms 2.7s 0 transport_latency_assumed tick_size_change i 3,240 141 23ms 61ms 182ms 484ms 0 transport_latency_assumed tick_size_change k 3,248 861 13ms 28ms 308ms 809ms 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-24/21/2026-09-24T21.parquet sha256sum 2026-09-24T21.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.