Hour audit: 2026-09-28T00
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-28T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T00:00:00.000015548+00:00 · last event 2026-09-28T00:59:59.999915951+00:00
VOLUME 104,679,306 rows · 1,069,199,781 bytes (1019.67 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 104,633,109 · h: 104,587,555 · g: 104,444,416 · i: 102,747,725 · c: 102,421,262 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 6,225,496 (5.95%) · h: 1,576,521 (1.51%) · g: 6,784 (0.01%) · i: 896,640 (0.86%) · c: 95,973,865 (91.68%) (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 104,679,306 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 297552095667fe4623c648695e2a9f9cb2ceae5253b9b2ceade874fdee99d091
the corpus checksum ledger names this file with the same digest
joined 104,681,009 to merged 104,679,306, minus 1,703 (minus 0.0016%)
boundary drops 1,703 · 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-28T03:07:36Z 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,170,528 134,675,666 0-46 011198e21d814cc7c62025cd7123391f4658b48082e1fd85359f7d2b37b7f530 book 122,405 12,748,056 47-47 65c5767bd0081e091a6ec97f28fa78877ce84396e2097bb6f1a6c9444868567a last_trade_price 48,503 2,835,936 48-48 5148b45d7328a2a63de420f98102acd5194bcffd7e1c2dfdc6c48064078ed8b3 market_resolved 2,498 377,725 49-49 d391160887e21b4c1b10301c526cb558a016694b0c4dd3f482445079c2dae233 new_market 1,428 143,136 50-50 fbf870d74bc8b28b123df0d1097545dd8b7e2a105e3a1b210e1d0ebedea6e055 price_change 92,330,596 917,102,070 51-403 904e463b771e9212a9b79ff239eb46ccb946a3c3dccd8cd6b5f9ae33ca38b0c1 tick_size_change 3,348 122,763 404-404 5f83967220df6807072caa2455e29dde4a7d17e8c5b526b9c407d76ae5cccc9b EVENT MIX count share price_change 92,330,596 88.20% best_bid_ask 12,170,528 11.63% book 122,405 0.12% last_trade_price 48,503 0.05% tick_size_change 3,348 <0.01% market_resolved 2,498 <0.01% new_market 1,428 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,170,740 12,170,528 212 2,027 FULL book 122,407 122,405 2 9,616 FULL last_trade_price 48,504 48,503 1 151 FULL market_resolved 2,498 2,498 0 56 FULL new_market 1,428 1,428 0 0 FULL price_change 92,332,084 92,330,596 1,488 3,645 FULL tick_size_change 3,348 3,348 0 43 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,970,793 11,281,212 5ms 10ms 86ms 5.1s 0 transport_latency_assumed best_bid_ask g 12,166,673 489 81ms 101ms 342ms 19.9s 0 transport_latency_assumed best_bid_ask h 12,169,609 159,195 18ms 23ms 145ms 50.3s 0 transport_latency_assumed best_bid_ask i 11,927,558 94,746 25ms 32ms 87ms 3.4s 0 transport_latency_assumed best_bid_ask k 12,169,300 634,886 12ms 21ms 139ms 59.0s 0 transport_latency_assumed book c 102,272 93,984 6ms 88ms 20.7h 102.6d 0 book_staleness book g 100,436 2,480 84ms 273ms 6.4h 102.6d 0 book_staleness book h 100,966 4,123 21ms 55ms 3.3h 102.6d 0 book_staleness book i 101,993 5,746 29ms 86ms 20.5h 121.1d 0 book_staleness book k 107,606 16,072 16ms 350ms 3.1d 102.6d 0 book_staleness last_trade_price c 46,835 43,072 6ms 15ms 212ms 2.2s 0 transport_latency_assumed last_trade_price g 47,961 2 83ms 199ms 4.1s 19.9s 0 transport_latency_assumed last_trade_price h 48,398 959 19ms 35ms 313ms 21.4s 0 transport_latency_assumed last_trade_price i 47,736 551 27ms 43ms 254ms 3.0s 0 transport_latency_assumed last_trade_price k 48,405 3,919 14ms 30ms 257ms 10.7s 0 transport_latency_assumed market_resolved c 2,329 2,029 5ms 47ms 1.3min 2.4min 0 transport_latency_assumed market_resolved g 2,361 80 81ms 192ms 47.8s 54.0s 0 transport_latency_assumed market_resolved h 2,361 27 18ms 57ms 49.7s 57.5s 0 transport_latency_assumed market_resolved i 2,337 196 27ms 86ms 56.6s 2.3min 0 transport_latency_assumed market_resolved k 2,361 166 13ms 39ms 54.2s 54.8s 0 transport_latency_assumed new_market c 941 570 66ms 33.8s 3.8min 4.4min 0 transport_latency_assumed new_market g 941 97 234ms 36.8s 3.9min 4.3min 0 transport_latency_assumed new_market h 941 286 88ms 33.2s 3.9min 4.4min 0 transport_latency_assumed new_market i 941 269 89ms 36.1s 3.9min 4.8min 0 transport_latency_assumed new_market k 941 206 186ms 38.4s 3.8min 4.1min 0 transport_latency_assumed price_change c 90,294,852 84,550,015 5ms 11ms 108ms 5.7s 0 transport_latency_assumed price_change g 92,122,696 3,636 81ms 109ms 631ms 20.5s 0 transport_latency_assumed price_change h 92,261,932 1,411,845 18ms 26ms 198ms 51.8s 0 transport_latency_assumed price_change i 90,663,876 795,090 26ms 34ms 135ms 3.4s 0 transport_latency_assumed price_change k 92,301,148 5,570,010 13ms 23ms 165ms 59.1s 0 transport_latency_assumed tick_size_change c 3,240 2,983 5ms 12ms 78ms 239ms 0 transport_latency_assumed tick_size_change g 3,348 not meas. 81ms 102ms 360ms 782ms 0 transport_latency_assumed tick_size_change h 3,348 86 18ms 28ms 89ms 285ms 0 transport_latency_assumed tick_size_change i 3,284 42 26ms 33ms 90ms 227ms 0 transport_latency_assumed tick_size_change k 3,348 237 13ms 23ms 164ms 420ms 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-28/00/2026-09-28T00.parquet sha256sum 2026-09-28T00.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.