Hour audit: 2026-10-02T07
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-02T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T07:00:00.000033335+00:00 · last event 2026-10-02T07:59:59.998154608+00:00
VOLUME 109,214,975 rows · 1,089,000,815 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 109,155,111 · h: 109,153,004 · m: 109,149,719 · g: 109,144,733 · k: 109,133,497 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 100,609 (0.09%) · h: 451,204 (0.41%) · m: 105,685,342 (96.77%) · g: 37,520 (0.03%) · k: 2,940,300 (2.69%) (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 109,214,975 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1be946d4b022c8af787830f741e647d17fd69693f4741c8125aa6c942e02b34b
the corpus checksum ledger names this file with the same digest
joined 109,216,782 to merged 109,214,975, minus 1,807 (minus 0.0017%)
boundary drops 1,807 · 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-02T09:44:34Z 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 10,235,355 116,074,731 0-39 dbbac617faa7eee46038946e7659505503edd0559f77590e06df5372743d99ac book 129,855 14,168,564 40-40 73ad33f408444e2a70929d449332bab52cfda75106f4b60af089f3d4c8d03aa1 last_trade_price 53,468 2,989,292 41-41 dcf7f5aea6f684a5ea0f090ecfe7190b5a697d29f02a6cc3516b2fad03112b0b market_resolved 531 82,729 42-42 3684c010566222c616204d9f05e8920327da6074b6dd0684d08176003cd41680 new_market 726 74,238 43-43 23cb364e5b0ac9ba910e71101b059a70ed29b45dd20823775e34864f9f4d2264 price_change 98,792,176 954,259,354 44-420 feaed7c6769d1344d26740324ef4c89bfdb1241350257ee4743892b890045890 tick_size_change 2,864 105,319 421-421 7dfb01f95f27f87b25c459bf3e1ba6e655abf5a20a2ae069b31365bba2886f35 EVENT MIX count share price_change 98,792,176 90.46% best_bid_ask 10,235,355 9.37% book 129,855 0.12% last_trade_price 53,468 0.05% tick_size_change 2,864 <0.01% new_market 726 <0.01% market_resolved 531 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,235,546 10,235,355 191 90 FULL book 129,857 129,855 2 9,976 FULL last_trade_price 53,470 53,468 2 0 FULL market_resolved 531 531 0 0 FULL new_market 726 726 0 0 FULL price_change 98,793,788 98,792,176 1,612 96 FULL tick_size_change 2,864 2,864 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,233,985 2,082 71ms 87ms 212ms 8.7s 0 transport_latency_assumed best_bid_ask h 10,234,610 40,903 18ms 31ms 120ms 39.8s 0 transport_latency_assumed best_bid_ask i 10,234,576 8,881 30ms 47ms 96ms 19.6s 0 transport_latency_assumed best_bid_ask k 10,234,868 243,455 13ms 21ms 122ms 26.7s 0 transport_latency_assumed best_bid_ask m 10,235,156 9,940,034 5ms 8ms 42ms 5.2s 0 transport_latency_assumed book g 123,249 15,635 77ms 1.5min 4.5d 106.9d 0 book_staleness book h 110,979 4,058 21ms 41ms 5.8h 106.7d 0 book_staleness book i 109,327 1,875 30ms 53ms 6.5min 106.8d 0 book_staleness book k 108,603 3,454 15ms 119ms 2.0s 60.8d 0 book_staleness book m 108,361 104,833 6ms 10ms 511ms 1.2d 0 book_staleness last_trade_price g 53,456 24 74ms 129ms 649ms 8.7s 0 transport_latency_assumed last_trade_price h 53,456 306 19ms 33ms 261ms 18.9s 0 transport_latency_assumed last_trade_price i 53,455 87 30ms 48ms 288ms 4.1s 0 transport_latency_assumed last_trade_price k 53,457 1,139 14ms 118ms 197ms 3.3s 0 transport_latency_assumed last_trade_price m 53,457 51,912 6ms 9ms 71ms 1.1s 0 transport_latency_assumed market_resolved g 504 not meas. 76ms 221ms 43.0s 43.1s 0 transport_latency_assumed market_resolved h 504 1 20ms 55ms 42.9s 43.0s 0 transport_latency_assumed market_resolved i 504 58 41ms 7.4s 50.7s 51.5s 0 transport_latency_assumed market_resolved k 504 31 14ms 34ms 48.5s 48.6s 0 transport_latency_assumed market_resolved m 504 441 5ms 8.3s 51.0s 52.7s 0 transport_latency_assumed new_market g 481 33 294ms 8.9s 47.6s 1.5min 0 transport_latency_assumed new_market h 481 100 169ms 17.9s 30.4s 1.6min 0 transport_latency_assumed new_market i 481 46 114ms 682ms 25.1s 1.3min 0 transport_latency_assumed new_market k 481 127 190ms 24.1s 1.4min 1.7min 0 transport_latency_assumed new_market m 481 420 28ms 8.0s 30.8s 1.6min 0 transport_latency_assumed price_change g 98,730,194 19,746 72ms 90ms 369ms 10.0s 0 transport_latency_assumed price_change h 98,750,110 405,836 18ms 32ms 158ms 41.4s 0 transport_latency_assumed price_change i 98,753,904 89,662 29ms 47ms 158ms 21.2s 0 transport_latency_assumed price_change k 98,732,720 2,692,040 13ms 22ms 128ms 31.1s 0 transport_latency_assumed price_change m 98,748,896 95,584,892 5ms 8ms 43ms 5.2s 0 transport_latency_assumed tick_size_change g 2,864 not meas. 71ms 86ms 119ms 244ms 0 transport_latency_assumed tick_size_change h 2,864 not meas. 18ms 31ms 59ms 3.7s 0 transport_latency_assumed tick_size_change i 2,864 not meas. 31ms 48ms 58ms 2.7s 0 transport_latency_assumed tick_size_change k 2,864 54 13ms 21ms 114ms 132ms 0 transport_latency_assumed tick_size_change m 2,864 2,810 5ms 7ms 19ms 57ms 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/07/2026-10-02T07.parquet sha256sum 2026-10-02T07.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.