Hour audit: 2026-09-24T15
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-24T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T15:00:00.000002516+00:00 · last event 2026-09-24T15:59:59.999985719+00:00
VOLUME 126,726,058 rows · 1,393,771,360 bytes (1.30 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 125,361,919 · i: 120,523,866 · g: 119,147,072 · k: 115,757,033 · c: 114,110,213 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 6,465,567 (5.10%) · i: 2,381,688 (1.88%) · g: 109,808 (0.09%) · k: 14,326,016 (11.30%) · c: 103,442,979 (81.63%) (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 126,726,058 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8ca7f374563b1688ebd4245a2139152913313d299fe50dc43ba9d883465a38fb
the corpus checksum ledger names this file with the same digest
joined 126,728,473 to merged 126,726,058, minus 2,415 (minus 0.0019%)
boundary drops 2,415 · 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-24T17:55:20Z 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 11,992,364 142,368,090 0-45 b9c00bb700142fb0b39cf34b3e901e39c63ae48382187800e0f1f73077e6dcec book 1,507,123 85,493,118 46-51 f2a9d1fe9a7c44c9fceaffcc0c11779a9933f4472732f107b56566283ee80e9c last_trade_price 60,746 3,501,558 52-52 44adbaf2c2bcd406cd628e63944e4cb165dfa6cac254afe77c47b947f1aa44aa market_resolved 1,233 160,661 53-53 446cee65f22260a504e421163edb00d410c1f1727b3bebc55dc45280d3be30c7 new_market 955 99,123 54-54 db6ef331061e39c03c41a9f0d5e13a5e94b6a65de22e820194912b2f95a7e998 price_change 113,161,093 1,160,612,957 55-486 1a14389b5fc65328e4f8217f3e3c4fe9ca79f53622b12d44294033155d4b842b tick_size_change 2,544 94,889 487-487 75c692a622360d51a5b07c83e6b4716852a506330cb633bfba018d082619e321 EVENT MIX count share price_change 113,161,093 89.30% best_bid_ask 11,992,364 9.46% book 1,507,123 1.19% last_trade_price 60,746 0.05% tick_size_change 2,544 <0.01% market_resolved 1,233 <0.01% new_market 955 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,992,629 11,992,364 265 1,460 FULL book 1,507,215 1,507,123 92 158,497 FULL last_trade_price 60,746 60,746 0 285 FULL market_resolved 1,233 1,233 0 26 FULL new_market 955 955 0 0 FULL price_change 113,163,151 113,161,093 2,058 446 FULL tick_size_change 2,544 2,544 0 99 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,842,870 9,907,387 5ms 15ms 98ms 2.4s 0 transport_latency_assumed best_bid_ask g 11,452,583 374 81ms 111ms 516ms 27.8s 0 transport_latency_assumed best_bid_ask h 11,990,350 588,855 19ms 48ms 136ms 9.9s 0 transport_latency_assumed best_bid_ask i 11,488,920 212,425 24ms 35ms 123ms 7.0s 0 transport_latency_assumed best_bid_ask k 10,983,272 1,283,323 13ms 22ms 86ms 3.9s 0 transport_latency_assumed book c 969,973 588,813 8.5min 4.3d 42.8d 117.7d 0 book_staleness book g 595,669 105,299 5.2min 3.2d 40.1d 117.7d 0 book_staleness book h 198,446 49,172 58ms 17.6h 24.8d 117.7d 0 book_staleness book i 570,853 127,407 4.5min 2.9d 35.4d 117.7d 0 book_staleness book k 984,967 636,432 7.8min 3.9d 42.8d 117.7d 0 book_staleness last_trade_price c 54,455 48,976 6ms 21ms 173ms 1.2s 0 transport_latency_assumed last_trade_price g 54,664 8 96ms 4.3s 17.7s 27.8s 0 transport_latency_assumed last_trade_price h 60,581 3,129 21ms 73ms 341ms 6.0s 0 transport_latency_assumed last_trade_price i 58,460 1,046 27ms 156ms 844ms 3.4s 0 transport_latency_assumed last_trade_price k 56,336 7,587 14ms 40ms 183ms 1.3s 0 transport_latency_assumed market_resolved c 979 789 6ms 3.5min 5.3min 7.0min 0 transport_latency_assumed market_resolved g 972 18 83ms 26.8s 5.2min 6.2min 0 transport_latency_assumed market_resolved h 983 82 20ms 169ms 42.1s 1.2min 0 transport_latency_assumed market_resolved i 970 83 26ms 23.2s 5.6min 5.6min 0 transport_latency_assumed market_resolved k 1,049 261 15ms 4.5min 9.2min 10.2min 0 transport_latency_assumed new_market c 638 399 58ms 13.0s 5.5min 5.5min 0 transport_latency_assumed new_market g 629 63 290ms 13.2s 1.5min 2.6min 0 transport_latency_assumed new_market h 628 130 100ms 11.4s 1.4min 1.7min 0 transport_latency_assumed new_market i 629 126 83ms 10.7s 1.6min 4.6min 0 transport_latency_assumed new_market k 662 237 62ms 21.9s 3.4min 5.5min 0 transport_latency_assumed price_change c 102,239,030 92,894,525 6ms 17ms 112ms 4.7s 0 transport_latency_assumed price_change g 107,040,191 4,046 82ms 178ms 8.1s 28.0s 0 transport_latency_assumed price_change h 113,108,387 5,824,041 19ms 52ms 181ms 9.9s 0 transport_latency_assumed price_change i 108,401,594 2,040,528 24ms 44ms 269ms 7.9s 0 transport_latency_assumed price_change k 103,728,431 12,397,953 13ms 25ms 103ms 4.4s 0 transport_latency_assumed tick_size_change c 2,268 2,090 6ms 17ms 179ms 289ms 0 transport_latency_assumed tick_size_change g 2,364 not meas. 81ms 102ms 341ms 995ms 0 transport_latency_assumed tick_size_change h 2,544 158 19ms 48ms 280ms 3.3s 0 transport_latency_assumed tick_size_change i 2,440 73 24ms 38ms 219ms 313ms 0 transport_latency_assumed tick_size_change k 2,316 223 13ms 25ms 271ms 380ms 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/15/2026-09-24T15.parquet sha256sum 2026-09-24T15.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.