Hour audit: 2026-09-24T13
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-24T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T13:00:00.000452628+00:00 · last event 2026-09-24T13:59:59.999981220+00:00
VOLUME 131,800,107 rows · 1,459,200,348 bytes (1.36 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 130,503,653 · h: 130,503,250 · g: 124,322,715 · k: 121,029,192 · c: 119,810,122 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 2,106,731 (1.60%) · h: 3,388,425 (2.57%) · g: 104,836 (0.08%) · k: 18,911,615 (14.35%) · c: 107,288,500 (81.40%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 131,800,107 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b90427ec406f0794f0e86f8f5aa9a6da091ee261e53b54e6399cae38828d5077
the corpus checksum ledger names this file with the same digest
joined 131,803,465 to merged 131,800,107, minus 3,358 (minus 0.0025%)
boundary drops 3,358 · 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-24T15:56:23Z 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,668,854 150,803,920 0-48 9d4aaae949416468c07fb0999c8bdc6205fd65e3dc41f32ba2396da346bed2e7 book 1,362,784 81,471,452 49-54 1d06e140dfd332ee18ffca1b2a1380ee8dacf8ada4d658cee6d62db5cc1ca5dc last_trade_price 67,089 3,864,297 55-55 40201f752ca14f10987f27fc66cf53ea2ba913dc9cfde9f1b688c57668089fa3 market_resolved 915 128,580 56-56 1498dc1cfb4880f1c153e9c367172df5d7befd7a4b80e7fe7eec6b935b656941 new_market 1,045 110,383 57-57 48fc5f987ac1459a253e30e69f95419e722f012b299b052a6194972e817f7684 price_change 117,696,248 1,221,208,242 58-506 39fd9fcf3b5733acb644373a61f8f7d30df134089587c5b1abaa0a83b396f638 tick_size_change 3,172 114,881 507-507 8708cc34db122c33f651119b2bed6c0540dee17eb885420343338e8c893a7f33 EVENT MIX count share price_change 117,696,248 89.30% best_bid_ask 12,668,854 9.61% book 1,362,784 1.03% last_trade_price 67,089 0.05% tick_size_change 3,172 <0.01% new_market 1,045 <0.01% market_resolved 915 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,669,198 12,668,854 344 1,777 FULL book 1,363,606 1,362,784 822 192,968 FULL last_trade_price 67,089 67,089 0 338 FULL market_resolved 915 915 0 32 FULL new_market 1,045 1,045 0 5 FULL price_change 117,698,440 117,696,248 2,192 810 FULL tick_size_change 3,172 3,172 0 74 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,627,368 10,501,814 6ms 17ms 107ms 4.2s 0 transport_latency_assumed best_bid_ask g 12,178,812 490 81ms 113ms 583ms 49.2s 0 transport_latency_assumed best_bid_ask h 12,666,595 302,872 18ms 50ms 156ms 22.5s 0 transport_latency_assumed best_bid_ask i 12,667,179 188,827 22ms 34ms 124ms 4.1s 0 transport_latency_assumed best_bid_ask k 11,686,589 1,674,851 13ms 23ms 92ms 1.7s 0 transport_latency_assumed book c 919,946 515,531 7.0min 4.1d 42.8d 117.6d 0 book_staleness book g 526,915 99,375 3.9min 2.8d 33.0d 117.6d 0 book_staleness book h 141,402 9,338 24ms 166ms 16.1h 99.1d 0 book_staleness book i 138,694 5,599 25ms 156ms 19.8min 117.6d 0 book_staleness book k 927,655 732,941 6.7min 3.8d 42.7d 117.6d 0 book_staleness last_trade_price c 59,160 52,610 7ms 25ms 165ms 1.4s 0 transport_latency_assumed last_trade_price g 60,119 6 93ms 3.6s 21.4s 48.4s 0 transport_latency_assumed last_trade_price h 66,902 2,126 21ms 87ms 559ms 7.1s 0 transport_latency_assumed last_trade_price i 66,898 1,329 25ms 110ms 738ms 3.6s 0 transport_latency_assumed last_trade_price k 60,717 11,018 14ms 42ms 208ms 1.1s 0 transport_latency_assumed market_resolved c 803 736 6ms 4.3min 5.8min 6.3min 0 transport_latency_assumed market_resolved g 778 not meas. 82ms 297ms 5.5min 6.5min 0 transport_latency_assumed market_resolved h 780 15 20ms 72ms 221ms 9.3s 0 transport_latency_assumed market_resolved i 780 7 23ms 76ms 290ms 25.8s 0 transport_latency_assumed market_resolved k 778 157 14ms 67ms 4.3min 4.3min 0 transport_latency_assumed new_market c 719 352 74ms 13.5s 5.4min 5.5min 0 transport_latency_assumed new_market g 719 71 285ms 12.7s 1.3min 1.4h 0 transport_latency_assumed new_market h 716 147 127ms 10.7s 1.0min 1.4min 0 transport_latency_assumed new_market i 716 174 101ms 16.1s 59.1s 1.8min 0 transport_latency_assumed new_market k 712 301 71ms 14.1s 5.0min 5.1min 0 transport_latency_assumed price_change c 107,199,094 96,214,529 6ms 19ms 121ms 4.2s 0 transport_latency_assumed price_change g 111,552,224 4,894 82ms 172ms 7.9s 49.6s 0 transport_latency_assumed price_change h 117,623,683 3,073,896 19ms 55ms 220ms 23.1s 0 transport_latency_assumed price_change i 117,626,214 1,910,770 22ms 41ms 201ms 4.2s 0 transport_latency_assumed price_change k 108,349,733 16,492,159 13ms 26ms 110ms 1.7s 0 transport_latency_assumed tick_size_change c 3,032 2,928 5ms 9ms 33ms 72ms 0 transport_latency_assumed tick_size_change g 3,148 not meas. 80ms 97ms 228ms 636ms 0 transport_latency_assumed tick_size_change h 3,172 31 19ms 43ms 75ms 463ms 0 transport_latency_assumed tick_size_change i 3,172 25 22ms 30ms 125ms 166ms 0 transport_latency_assumed tick_size_change k 3,008 188 13ms 20ms 51ms 172ms 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/13/2026-09-24T13.parquet sha256sum 2026-09-24T13.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.