Hour audit: 2026-10-02T06
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-02T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T06:00:00.000133148+00:00 · last event 2026-10-02T06:59:59.999956935+00:00
VOLUME 104,743,692 rows · 1,084,117,136 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 104,539,154 · m: 104,240,618 · h: 104,237,553 · g: 104,228,063 · i: 104,227,368 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 2,505,390 (2.39%) · m: 101,674,490 (97.07%) · h: 380,225 (0.36%) · g: 49,093 (0.05%) · i: 134,494 (0.13%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 104,743,692 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 20791a99453e45e791bb371072f7e6e705f403f070c9aa5aec8937c8355bc116
the corpus checksum ledger names this file with the same digest
joined 104,745,525 to merged 104,743,692, minus 1,833 (minus 0.0017%)
boundary drops 1,833 · 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-02T08:43:59Z 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,683,852 110,455,881 0-36 1fdefae555fc82f5d1f2932df1cc4a8e232df4ec1872e6b6e587a83ede6474c5 book 599,983 58,844,261 37-39 79f93ebf8c99252cdf800c7786ca7a4a3e0636ac9bf579d57685b9cbaaa0ea61 last_trade_price 54,162 3,015,801 40-40 601c97bb33c5132610d0646ca444a232a3bf5d7be04def0ab8f26d96a00ca339 market_resolved 623 96,254 41-41 300841f3d662238870c8447e07f08c35b187ee88ca1c7521b255fd7432d3a420 new_market 544 57,151 42-42 25ff3401d8b9204216b45728bf4df8458d4e7649fc68619e58d8e9164a189c94 price_change 94,402,556 910,377,619 43-403 655876bf76d0fffc1456f7f03b3ee07a9b6da787e46a6fa483c851cc9ad2f212 tick_size_change 1,972 73,177 404-404 cb00957276fe773fc8539a2eca8ea6811f061050423215003a451a7c21ffaaa6 EVENT MIX count share price_change 94,402,556 90.13% best_bid_ask 9,683,852 9.25% book 599,983 0.57% last_trade_price 54,162 0.05% tick_size_change 1,972 <0.01% market_resolved 623 <0.01% new_market 544 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,683,967 9,683,852 115 90 FULL book 600,477 599,983 494 220,433 FULL last_trade_price 54,162 54,162 0 2 FULL market_resolved 623 623 0 0 FULL new_market 544 544 0 0 FULL price_change 94,403,780 94,402,556 1,224 107 FULL tick_size_change 1,972 1,972 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,682,146 1,058 71ms 84ms 166ms 14.5s 0 transport_latency_assumed best_bid_ask h 9,683,406 26,212 18ms 31ms 69ms 33.7s 0 transport_latency_assumed best_bid_ask i 9,683,263 10,194 24ms 43ms 63ms 5.1s 0 transport_latency_assumed best_bid_ask k 9,671,336 158,892 13ms 19ms 118ms 20.4s 0 transport_latency_assumed best_bid_ask m 9,683,762 9,487,496 5ms 7ms 30ms 3.5s 0 transport_latency_assumed book g 159,066 38,321 77ms 5.1h 24.8d 106.8d 0 book_staleness book h 119,013 9,335 23ms 98ms 1.2d 106.8d 0 book_staleness book i 116,808 7,656 24ms 67ms 6.0h 125.3d 0 book_staleness book k 575,156 432,690 28.3min 1.1d 40.7d 125.3d 0 book_staleness book m 118,956 111,981 6ms 68ms 3.0d 54.5d 0 book_staleness last_trade_price g 54,053 23 72ms 96ms 383ms 14.5s 0 transport_latency_assumed last_trade_price h 54,144 362 20ms 32ms 160ms 9.0s 0 transport_latency_assumed last_trade_price i 54,149 86 24ms 44ms 263ms 3.8s 0 transport_latency_assumed last_trade_price k 54,070 1,734 13ms 20ms 117ms 3.5s 0 transport_latency_assumed last_trade_price m 54,144 51,957 6ms 9ms 98ms 1.4s 0 transport_latency_assumed market_resolved g 588 not meas. 73ms 204ms 56.1s 58.0s 0 transport_latency_assumed market_resolved h 588 7 19ms 40ms 31.0s 54.8s 0 transport_latency_assumed market_resolved i 588 16 40ms 86ms 49.8s 49.8s 0 transport_latency_assumed market_resolved k 588 38 13ms 28ms 34.8s 57.5s 0 transport_latency_assumed market_resolved m 588 562 5ms 15ms 49.5s 49.6s 0 transport_latency_assumed new_market g 372 27 186ms 12.3s 1.0min 1.5min 0 transport_latency_assumed new_market h 372 107 109ms 17.9s 46.3s 53.0s 0 transport_latency_assumed new_market i 372 72 59ms 14.6s 1.1min 1.2min 0 transport_latency_assumed new_market k 372 70 82ms 18.2s 1.1min 1.5min 0 transport_latency_assumed new_market m 372 268 29ms 14.2s 1.1min 1.3min 0 transport_latency_assumed price_change g 94,329,866 9,664 72ms 87ms 255ms 14.7s 0 transport_latency_assumed price_change h 94,378,058 344,202 18ms 31ms 92ms 34.5s 0 transport_latency_assumed price_change i 94,370,216 116,470 23ms 43ms 90ms 5.6s 0 transport_latency_assumed price_change k 94,235,660 1,911,926 13ms 20ms 118ms 21.7s 0 transport_latency_assumed price_change m 94,380,824 92,020,294 5ms 8ms 41ms 4.8s 0 transport_latency_assumed tick_size_change g 1,972 not meas. 72ms 84ms 129ms 235ms 0 transport_latency_assumed tick_size_change h 1,972 not meas. 18ms 32ms 42ms 65ms 0 transport_latency_assumed tick_size_change i 1,972 not meas. 25ms 42ms 58ms 88ms 0 transport_latency_assumed tick_size_change k 1,972 40 13ms 18ms 116ms 119ms 0 transport_latency_assumed tick_size_change m 1,972 1,932 5ms 7ms 16ms 46ms 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/06/2026-10-02T06.parquet sha256sum 2026-10-02T06.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.