Hour audit: 2026-10-02T16
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-02T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T16:00:00.000006202+00:00 · last event 2026-10-02T16:59:59.999825505+00:00
VOLUME 123,518,086 rows · 1,404,886,150 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 122,943,211 · m: 122,938,414 · k: 122,905,009 · i: 122,866,166 · g: 115,451,226 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,235,087 (3.43%) · m: 104,466,767 (84.58%) · k: 11,439,057 (9.26%) · i: 2,855,272 (2.31%) · g: 521,903 (0.42%) (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 123,518,086 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c38186233ce56c0171e594b4a8de2d91c7448de373199590e4331a4f9ca46b47
the corpus checksum ledger names this file with the same digest
joined 123,521,443 to merged 123,518,086, minus 3,357 (minus 0.0027%)
boundary drops 3,357 · 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-02T18:47:52Z as ghikm
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,423,941 118,078,979 0-35 249195384dcedf9640e067d6b58208c43419f5d4e394a86fb75e3ba4a3395edf book 771,065 72,465,854 36-38 7a0af60e0440777825d8dc8ec860e954e1f2f4d26482c34878783ac2e0ad96a0 last_trade_price 67,856 3,898,862 39-39 d38885e523690649ec9fbfefac19b332fa69d64a2c7c1cbe9199cfa6decfe930 market_resolved 1,065 166,782 40-40 cf950f8b2af1b37899c2d82042a9ae32b8e14501327b15c0c7a9249796651ad6 new_market 2,271 219,010 41-41 332c3b51e69231aa43b306dcedb9be1eac1656f81f7fa4e6673c344a8cf0a163 price_change 113,248,964 1,208,542,840 42-474 85eacc67ad77b269f1cd5a382a8606c4ff9ffe6aa127da4aecb5a0a5b605c162 tick_size_change 2,924 107,318 475-475 847592f0c4d91cb98f666392cdc598a7a3923a245f654fe4a37b7c622c1bec3d EVENT MIX count share price_change 113,248,964 91.69% best_bid_ask 9,423,941 7.63% book 771,065 0.62% last_trade_price 67,856 0.05% tick_size_change 2,924 <0.01% new_market 2,271 <0.01% market_resolved 1,065 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,424,083 9,423,941 142 895 FULL book 771,605 771,065 540 232,474 FULL last_trade_price 67,857 67,856 1 129 FULL market_resolved 1,065 1,065 0 29 FULL new_market 2,271 2,271 0 0 FULL price_change 113,251,638 113,248,964 2,674 582 FULL tick_size_change 2,924 2,924 0 16 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 8,957,713 3,760 81ms 165ms 1.5s 38.3s 0 transport_latency_assumed best_bid_ask h 9,420,687 315,192 19ms 58ms 512ms 52.0s 0 transport_latency_assumed best_bid_ask i 9,422,612 203,714 22ms 54ms 323ms 6.8s 0 transport_latency_assumed best_bid_ask k 9,422,352 829,112 15ms 49ms 304ms 56.8s 0 transport_latency_assumed best_bid_ask m 9,422,943 8,072,163 6ms 31ms 236ms 5.8s 0 transport_latency_assumed book g 648,273 469,986 16.5min 21.7h 41.1d 125.7d 0 book_staleness book h 262,256 77,490 495ms 15.2h 37.9d 125.8d 0 book_staleness book i 145,306 9,126 28ms 585ms 15.4h 107.3d 0 book_staleness book k 215,243 53,883 45ms 11.3h 27.1d 125.7d 0 book_staleness book m 231,764 160,580 34ms 15.1h 29.9d 125.7d 0 book_staleness last_trade_price g 60,007 41 100ms 2.5s 20.2s 38.4s 0 transport_latency_assumed last_trade_price h 67,815 2,255 23ms 222ms 1.5s 45.0s 0 transport_latency_assumed last_trade_price i 67,841 1,806 26ms 240ms 1.7s 3.8s 0 transport_latency_assumed last_trade_price k 67,833 6,747 17ms 111ms 671ms 55.9s 0 transport_latency_assumed last_trade_price m 67,838 57,007 7ms 55ms 448ms 4.2s 0 transport_latency_assumed market_resolved g 1,002 14 92ms 22.8s 5.3min 6.1min 0 transport_latency_assumed market_resolved h 1,021 22 22ms 299ms 46.4s 46.5s 0 transport_latency_assumed market_resolved i 1,021 6 25ms 401ms 52.4s 56.5s 0 transport_latency_assumed market_resolved k 1,021 105 18ms 152ms 48.4s 48.5s 0 transport_latency_assumed market_resolved m 1,021 918 6ms 19.9s 52.0s 54.8s 0 transport_latency_assumed new_market g 1,365 308 330ms 31.8s 5.8min 5.9min 0 transport_latency_assumed new_market h 1,358 350 173ms 23.5s 1.0min 1.5min 0 transport_latency_assumed new_market i 1,358 341 106ms 12.5s 35.8s 1.8min 0 transport_latency_assumed new_market k 1,358 325 173ms 28.2s 44.2s 1.8min 0 transport_latency_assumed new_market m 1,358 947 59ms 22.0s 1.2min 1.6min 0 transport_latency_assumed price_change g 105,780,006 47,794 83ms 306ms 12.0s 38.5s 0 transport_latency_assumed price_change h 113,187,150 3,839,714 20ms 88ms 919ms 52.5s 0 transport_latency_assumed price_change i 113,225,104 2,640,232 22ms 83ms 741ms 8.7s 0 transport_latency_assumed price_change k 113,194,278 10,548,672 15ms 63ms 389ms 56.8s 0 transport_latency_assumed price_change m 113,210,566 96,172,552 6ms 37ms 281ms 6.2s 0 transport_latency_assumed tick_size_change g 2,860 not meas. 80ms 99ms 252ms 1.5s 0 transport_latency_assumed tick_size_change h 2,924 64 20ms 38ms 157ms 2.8s 0 transport_latency_assumed tick_size_change i 2,924 47 22ms 46ms 167ms 1.8s 0 transport_latency_assumed tick_size_change k 2,924 213 15ms 41ms 146ms 1.1s 0 transport_latency_assumed tick_size_change m 2,924 2,600 6ms 18ms 484ms 533ms 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-02/16/2026-10-02T16.parquet sha256sum 2026-10-02T16.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.