Hour audit: 2026-09-28T14
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-28T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T14:00:00.000136125+00:00 · last event 2026-09-28T14:59:59.999376855+00:00
VOLUME 105,439,973 rows · 1,167,290,035 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 104,961,808 · h: 104,868,733 · i: 104,834,085 · g: 102,825,028 · k: 101,669,800 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 92,640,087 (87.86%) · h: 1,877,826 (1.78%) · i: 2,116,212 (2.01%) · g: 29,980 (0.03%) · k: 8,775,868 (8.32%) (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 105,439,973 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2a84ba994450ea88daeb1f8ddfd2242b3bb8386bfc019a3742f4bb8677e9aab4
the corpus checksum ledger names this file with the same digest
joined 105,441,993 to merged 105,439,973, minus 2,020 (minus 0.0019%)
boundary drops 2,020 · 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-28T17:06:28Z 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 8,897,556 107,474,127 0-33 882296b2c33a88a2a8b44dae8c88543d436098e3b7765ce1261d56c50c0c151c book 556,516 55,705,940 34-36 49cd6b9c3a755dacc19b47de4700e2c4067872fd07c383a69a505e709ccf5a3b last_trade_price 59,668 3,447,776 37-37 fa0e4b1514c283201de90a89083b97c23c002d57c3e974d5bf16fa6d1c29f8d2 market_resolved 947 142,726 38-38 17d951ef0c13ceb8b9f9c9a38aa0188d48e256bf05b0e355b4a37b65fc698dd2 new_market 3,138 330,034 39-39 4828631e65daffbe19f71007fad252e6375d681122193a713b9ffb68e015bb8c price_change 95,919,704 998,896,789 40-405 71c06e7bc55fe32f7eff843e591ec2b813b7d69e9f87e87fecbc1773963df13f tick_size_change 2,444 91,084 406-406 926e8943c31d7a78116fa4720c2f370d0484857c327a36b5d1b185f5fc8becfb EVENT MIX count share price_change 95,919,704 90.97% best_bid_ask 8,897,556 8.44% book 556,516 0.53% last_trade_price 59,668 0.06% new_market 3,138 <0.01% tick_size_change 2,444 <0.01% market_resolved 947 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,897,784 8,897,556 228 421 FULL book 556,532 556,516 16 199,385 FULL last_trade_price 59,668 59,668 0 69 FULL market_resolved 947 947 0 7 FULL new_market 3,138 3,138 0 0 FULL price_change 95,921,480 95,919,704 1,776 444 FULL tick_size_change 2,444 2,444 0 10 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,896,455 7,874,593 6ms 19ms 235ms 5.6s 0 transport_latency_assumed best_bid_ask g 8,862,046 1,111 81ms 137ms 1.8s 43.8s 0 transport_latency_assumed best_bid_ask h 8,894,384 150,425 19ms 37ms 456ms 1.6min 0 transport_latency_assumed best_bid_ask i 8,894,576 191,593 22ms 36ms 286ms 53.5s 0 transport_latency_assumed best_bid_ask k 8,630,430 679,834 13ms 27ms 200ms 49.5s 0 transport_latency_assumed book c 125,084 107,590 8ms 53ms 4.4min 103.2d 0 book_staleness book g 134,149 16,841 121ms 36.4min 16.0d 103.2d 0 book_staleness book h 132,217 8,725 25ms 1.2s 1.4d 103.2d 0 book_staleness book i 137,023 16,352 29ms 9.7s 2.0d 103.2d 0 book_staleness book k 528,765 407,008 29.6min 1.4d 37.0d 121.7d 0 book_staleness last_trade_price c 59,593 52,623 7ms 27ms 368ms 5.3s 0 transport_latency_assumed last_trade_price g 53,933 9 96ms 5.0s 18.0s 43.9s 0 transport_latency_assumed last_trade_price h 59,360 1,023 20ms 111ms 1.4s 52.5s 0 transport_latency_assumed last_trade_price i 59,188 919 24ms 323ms 4.0s 31.2s 0 transport_latency_assumed last_trade_price k 57,494 5,094 14ms 49ms 304ms 9.0s 0 transport_latency_assumed market_resolved c 888 777 6ms 26ms 32.4s 43.7s 0 transport_latency_assumed market_resolved g 888 not meas. 83ms 307ms 53.5s 56.6s 0 transport_latency_assumed market_resolved h 888 18 20ms 68ms 30.9s 42.8s 0 transport_latency_assumed market_resolved i 888 59 23ms 101ms 50.1s 53.0s 0 transport_latency_assumed market_resolved k 881 93 14ms 71ms 4.6min 4.7min 0 transport_latency_assumed new_market c 2,108 868 157ms 1.1min 1.6min 1.8min 0 transport_latency_assumed new_market g 2,108 391 414ms 1.1min 1.6min 1.7min 0 transport_latency_assumed new_market h 2,108 392 220ms 34.8s 1.6min 1.7min 0 transport_latency_assumed new_market i 2,108 671 156ms 36.6s 1.6min 1.8min 0 transport_latency_assumed new_market k 2,108 816 167ms 37.3s 1.6min 3.9min 0 transport_latency_assumed price_change c 95,875,236 84,601,392 6ms 21ms 260ms 7.4s 0 transport_latency_assumed price_change g 93,769,464 11,628 82ms 279ms 11.7s 43.9s 0 transport_latency_assumed price_change h 95,777,332 1,717,213 19ms 47ms 623ms 1.6min 0 transport_latency_assumed price_change i 95,737,858 1,906,586 22ms 56ms 798ms 53.8s 0 transport_latency_assumed price_change k 92,447,714 7,682,885 13ms 32ms 224ms 49.5s 0 transport_latency_assumed tick_size_change c 2,444 2,244 6ms 14ms 193ms 364ms 0 transport_latency_assumed tick_size_change g 2,440 not meas. 80ms 114ms 1.7s 5.3s 0 transport_latency_assumed tick_size_change h 2,444 30 19ms 30ms 281ms 25.8s 0 transport_latency_assumed tick_size_change i 2,444 32 22ms 31ms 268ms 5.5s 0 transport_latency_assumed tick_size_change k 2,408 138 13ms 22ms 234ms 392ms 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/14/2026-09-28T14.parquet sha256sum 2026-09-28T14.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.