Hour audit: 2026-10-04T15
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-10-04T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T15:00:00.000018148+00:00 · last event 2026-10-04T15:59:59.999977890+00:00
VOLUME 113,268,370 rows · 1,276,962,906 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 113,190,118 · o: 113,184,871 · m: 113,183,888 · i: 113,182,956 · n: 113,151,882 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 980,298 (0.87%) · o: 57,610,736 (50.86%) · m: 54,105,451 (47.77%) · i: 495,025 (0.44%) · n: 76,860 (0.07%) (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,268,370 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a7b9e0ad6e1a8dc4ea04365090fb32ff3efd580af827cc7f3e08461352fa062f
the corpus checksum ledger names this file with the same digest
joined 113,270,663 to merged 113,268,370, minus 2,293 (minus 0.0020%)
boundary drops 2,293 · 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-10-04T17:02:46Z as himno
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 9,136,476 115,115,608 0-34 1c9166fa29efb9b09201390a8acf62c236887a32ab2c2213bd32dbb4a8ecd71e book 140,740 15,273,130 35-35 32fa8d1e62e62fdf1212d9103c64b4d0576eadb3d59786e7869e2c7871b763a4 last_trade_price 61,010 3,563,239 36-36 1883fababca92de635e63ba3e4c15584a60852377d17c85662bb28802fb23039 market_resolved 1,192 187,386 37-37 48bbe829f8b6d0d1c4dfc7cc73131a8412045dac1de3421b4be3d7bd1eced4f0 new_market 3,626 337,462 38-38 75cd02d547f3419bf92136e7827d502072303f905789f29f5246a166fea1086b price_change 103,921,814 1,141,064,803 39-435 cdce258f459088b73224fa70251c617fe2e1ba2036d15b81c3f8556e0b6e0fa3 tick_size_change 3,512 129,835 436-436 c59f5c464c51dd9282f64371a7b6a6a048e2f2c48155f98c2c0b2e6d5b438e2b EVENT MIX count share price_change 103,921,814 91.75% best_bid_ask 9,136,476 8.07% book 140,740 0.12% last_trade_price 61,010 0.05% new_market 3,626 <0.01% tick_size_change 3,512 <0.01% market_resolved 1,192 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,136,603 9,136,476 127 222 FULL book 140,740 140,740 0 5,382 FULL last_trade_price 61,010 61,010 0 0 FULL market_resolved 1,192 1,192 0 0 FULL new_market 3,626 3,626 0 0 FULL price_change 103,923,980 103,921,814 2,166 721 FULL tick_size_change 3,512 3,512 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,133,896 71,216 19ms 32ms 385ms 48.3s 0 transport_latency_assumed best_bid_ask i 9,134,292 37,211 23ms 35ms 210ms 11.3s 0 transport_latency_assumed best_bid_ask m 9,135,264 4,419,050 5ms 15ms 120ms 9.1s 0 transport_latency_assumed best_bid_ask n 9,133,881 5,194 47ms 66ms 303ms 13.2s 0 transport_latency_assumed best_bid_ask o 9,134,928 4,603,805 5ms 15ms 127ms 5.6s 0 transport_latency_assumed book h 131,440 7,365 24ms 231ms 3.4h 109.2d 0 book_staleness book i 128,224 3,274 26ms 181ms 14.1min 109.2d 0 book_staleness book m 128,026 64,632 7ms 47ms 6.0min 109.2d 0 book_staleness book n 129,220 3,574 52ms 491ms 1.4h 109.1d 0 book_staleness book o 128,059 61,895 7ms 55ms 14.6min 109.2d 0 book_staleness last_trade_price h 60,918 733 21ms 68ms 788ms 27.4s 0 transport_latency_assumed last_trade_price i 60,876 265 25ms 98ms 948ms 4.0s 0 transport_latency_assumed last_trade_price m 60,888 29,989 6ms 25ms 231ms 1.5s 0 transport_latency_assumed last_trade_price n 60,803 29 52ms 235ms 3.1s 12.5s 0 transport_latency_assumed last_trade_price o 60,777 29,994 6ms 27ms 262ms 2.3s 0 transport_latency_assumed market_resolved h 1,162 136 21ms 12.9s 54.7s 54.7s 0 transport_latency_assumed market_resolved i 1,162 3 25ms 20.6s 48.4s 57.9s 0 transport_latency_assumed market_resolved m 1,162 479 7ms 15.2s 50.6s 50.7s 0 transport_latency_assumed market_resolved n 1,162 not meas. 49ms 21.7s 49.3s 58.2s 0 transport_latency_assumed market_resolved o 1,162 574 6ms 14.8s 49.7s 49.8s 0 transport_latency_assumed new_market h 2,177 493 156ms 37.3s 1.8min 2.2min 0 transport_latency_assumed new_market i 2,177 462 130ms 40.3s 1.9min 2.3min 0 transport_latency_assumed new_market m 2,177 1,141 66ms 42.5s 1.9min 2.3min 0 transport_latency_assumed new_market n 2,177 367 184ms 49.5s 1.8min 2.2min 0 transport_latency_assumed new_market o 2,177 1,163 66ms 36.7s 1.7min 2.2min 0 transport_latency_assumed price_change h 103,857,013 900,316 19ms 37ms 510ms 54.6s 0 transport_latency_assumed price_change i 103,852,713 453,764 23ms 41ms 352ms 11.7s 0 transport_latency_assumed price_change m 103,852,859 49,588,519 5ms 17ms 133ms 9.2s 0 transport_latency_assumed price_change n 103,821,127 67,692 47ms 81ms 727ms 13.6s 0 transport_latency_assumed price_change o 103,854,256 52,911,523 5ms 17ms 144ms 6.3s 0 transport_latency_assumed tick_size_change h 3,512 39 19ms 35ms 143ms 6.2s 0 transport_latency_assumed tick_size_change i 3,512 46 23ms 40ms 119ms 197ms 0 transport_latency_assumed tick_size_change m 3,512 1,641 5ms 18ms 102ms 508ms 0 transport_latency_assumed tick_size_change n 3,512 4 47ms 69ms 177ms 383ms 0 transport_latency_assumed tick_size_change o 3,512 1,782 5ms 19ms 126ms 1.0s 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-10-04/15/2026-10-04T15.parquet sha256sum 2026-10-04T15.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.