Hour audit: 2026-09-24T03
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-24T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T03:00:00.000037946+00:00 · last event 2026-09-24T03:59:59.999881929+00:00
VOLUME 117,949,432 rows · 1,240,382,961 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 117,450,213 · c: 117,440,427 · g: 117,377,555 · h: 117,350,089 · k: 112,834,646 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,352,446 (1.15%) · c: 108,840,613 (92.28%) · g: 24,551 (0.02%) · h: 1,734,107 (1.47%) · k: 5,997,715 (5.08%) (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 117,949,432 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8ea0b43cdb8c0fcdab55e5bc6061ef00ac2ce02383f9e72eeddd9000aac52018
the corpus checksum ledger names this file with the same digest
joined 117,952,971 to merged 117,949,432, minus 3,539 (minus 0.0030%)
boundary drops 3,539 · 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-24T08:23:13Z 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,755,708 144,680,067 0-48 27d34e26d0c4c8e8dc98d805f12acd1bb6af3383e92fa8bec4074673a680f0ce book 632,916 55,856,429 49-51 3fff3be4a8c81294a0a77ea1ff8d4ee5c9db73e2afd73b846b61baf7802b6f54 last_trade_price 46,044 2,637,121 52-52 fe361f79d7fdabe7b284be09986bc0c3697f9123345f622ba10c3f242983c0e1 market_resolved 1,180 188,439 53-53 3857320955b7e5900ed8ba915ddab719fb386a8a4cad17d73705a1f17c3a422a new_market 1,038 108,392 54-54 d3d566c42bcef06b556e2039f3d71528ba26f406b086e3392dcb54f9dc0fa9a2 price_change 104,508,854 1,035,438,784 55-453 1fb22629899086d959c76cd07777c8598dab0fe10ba2dd39ad937da45cf633a5 tick_size_change 3,692 131,174 454-454 4becc1234168a0de03d9ab990f80cce51aca2afd5be5cbfde49cd2f0e023e7e0 EVENT MIX count share price_change 104,508,854 88.60% best_bid_ask 12,755,708 10.81% book 632,916 0.54% last_trade_price 46,044 0.04% tick_size_change 3,692 <0.01% market_resolved 1,180 <0.01% new_market 1,038 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,756,005 12,755,708 297 415 FULL book 632,952 632,916 36 192,664 FULL last_trade_price 46,044 46,044 0 58 FULL market_resolved 1,180 1,180 0 0 FULL new_market 1,038 1,038 0 0 FULL price_change 104,512,060 104,508,854 3,206 325 FULL tick_size_change 3,692 3,692 0 26 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,754,176 11,911,912 4ms 11ms 86ms 7.4s 0 transport_latency_assumed best_bid_ask g 12,753,161 569 82ms 103ms 264ms 6.4s 0 transport_latency_assumed best_bid_ask h 12,754,260 166,554 17ms 36ms 131ms 40.2s 0 transport_latency_assumed best_bid_ask i 12,752,870 124,479 20ms 28ms 96ms 4.1s 0 transport_latency_assumed best_bid_ask k 12,214,607 552,194 12ms 20ms 95ms 14.8s 0 transport_latency_assumed book c 166,472 138,371 28ms 1.3d 32.5d 117.2d 0 book_staleness book g 130,994 17,505 96ms 31.9min 18.6d 98.7d 0 book_staleness book h 106,366 9,763 21ms 44.7s 5.5d 98.7d 0 book_staleness book i 186,937 63,307 919ms 1.5d 32.6d 117.2d 0 book_staleness book k 521,264 403,970 7.3min 3.1d 39.6d 117.2d 0 book_staleness last_trade_price c 45,821 41,118 5ms 24ms 194ms 3.1s 0 transport_latency_assumed last_trade_price g 45,784 34 85ms 174ms 591ms 5.7s 0 transport_latency_assumed last_trade_price h 45,859 981 19ms 56ms 299ms 7.8s 0 transport_latency_assumed last_trade_price i 45,864 780 22ms 49ms 239ms 2.1s 0 transport_latency_assumed last_trade_price k 43,698 3,131 13ms 34ms 218ms 13.8s 0 transport_latency_assumed market_resolved c 1,108 991 4ms 19ms 49.6s 55.3s 0 transport_latency_assumed market_resolved g 1,108 1 83ms 330ms 48.3s 55.7s 0 transport_latency_assumed market_resolved h 1,108 18 18ms 123ms 51.4s 51.5s 0 transport_latency_assumed market_resolved i 1,108 88 20ms 151ms 51.3s 51.4s 0 transport_latency_assumed market_resolved k 1,108 82 12ms 40ms 4.4min 4.4min 0 transport_latency_assumed new_market c 698 323 59ms 9.4s 44.8s 2.0min 0 transport_latency_assumed new_market g 698 78 253ms 12.9s 1.7min 2.0min 0 transport_latency_assumed new_market h 698 198 92ms 12.5s 1.6min 2.0min 0 transport_latency_assumed new_market i 698 200 77ms 10.8s 1.6min 2.0min 0 transport_latency_assumed new_market k 698 239 75ms 11.3s 1.7min 2.0min 0 transport_latency_assumed price_change c 104,468,460 96,744,438 5ms 14ms 98ms 7.5s 0 transport_latency_assumed price_change g 104,442,118 6,364 82ms 107ms 316ms 6.7s 0 transport_latency_assumed price_change h 104,438,106 1,556,569 17ms 39ms 150ms 40.2s 0 transport_latency_assumed price_change i 104,459,044 1,163,578 20ms 32ms 117ms 4.1s 0 transport_latency_assumed price_change k 100,049,683 5,037,905 12ms 23ms 110ms 14.8s 0 transport_latency_assumed tick_size_change c 3,692 3,460 5ms 9ms 45ms 85ms 0 transport_latency_assumed tick_size_change g 3,692 not meas. 81ms 97ms 135ms 405ms 0 transport_latency_assumed tick_size_change h 3,692 24 18ms 61ms 92ms 249ms 0 transport_latency_assumed tick_size_change i 3,692 14 20ms 31ms 59ms 220ms 0 transport_latency_assumed tick_size_change k 3,588 194 13ms 19ms 41ms 88ms 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/03/2026-09-24T03.parquet sha256sum 2026-09-24T03.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.