Hour audit: 2026-09-10T06
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-10T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T06:00:00.000043751+00:00 · last event 2026-09-10T06:59:59.999981513+00:00
VOLUME 98,901,752 rows · 1,028,177,886 bytes (980.55 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 98,345,033 · e: 98,339,457 · f: 98,317,348 · h: 98,316,878 · g: 98,000,154 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 94,485,879 (95.54%) · e: 611,265 (0.62%) · f: 368,864 (0.37%) · h: 3,378,794 (3.42%) · g: 56,950 (0.06%) (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 98,901,752 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ba6ab8aa2b44c21cebdda3e942d1ec6e6272e65acd0edc7a835dc081fa262458
the corpus checksum ledger names this file with the same digest
joined 98,902,684 to merged 98,901,752, minus 932 (minus 0.0009%)
boundary drops 932 · 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-10T07:56:09Z as cefgh
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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,292,582 94,508,193 0-31 641fd3d5536a3dba100879fcfc026208f52fb4b462f9863bead6c7a8e3ae0cc6 book 958,276 74,545,838 32-35 090cc6b6fb4bb6ac390a659848f68eb51c9cc48f77f4cf19b576abbf606fa0e3 last_trade_price 56,739 3,212,234 36-36 474470c0a022a642b117f7024f2f5501a28f75f61eaccc32f9515a9b7a53956d market_resolved 552 92,400 37-37 6a2ada7ecb0fe802d66b5d8c32ee97c9b8fdb222eb281fa53437b19d1f9b0bf2 new_market 1,859 186,235 38-38 c5c0b8364f32223e8b4ff746d46361038674eac5030b8650f44b4c8c47579593 price_change 89,589,812 854,433,666 39-380 bdb8d3a048382ab4c18692b2af85d6d95958c5b5d8b20dd3a655fa9df811bf36 tick_size_change 1,932 71,749 381-381 a22fad4a7a6ab4b6037d7a7f460b11bf0b657c47ad23db910960a26e4fa47a84 EVENT MIX count share price_change 89,589,812 90.58% best_bid_ask 8,292,582 8.38% book 958,276 0.97% last_trade_price 56,739 0.06% tick_size_change 1,932 <0.01% new_market 1,859 <0.01% market_resolved 552 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,292,668 8,292,582 86 468 FULL book 958,282 958,276 6 186,145 FULL last_trade_price 56,739 56,739 0 0 FULL market_resolved 552 552 0 1 FULL new_market 1,859 1,859 0 0 FULL price_change 89,590,652 89,589,812 840 112 FULL tick_size_change 1,932 1,932 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,289,469 7,986,941 5ms 10ms 118ms 6.7s 0 transport_latency_assumed best_bid_ask e 8,286,284 31,953 39ms 45ms 185ms 9.5s 0 transport_latency_assumed best_bid_ask f 8,285,510 13,228 45ms 52ms 198ms 9.3s 0 transport_latency_assumed best_bid_ask g 8,284,281 1,522 76ms 108ms 409ms 22.6s 0 transport_latency_assumed best_bid_ask h 8,288,346 258,938 17ms 25ms 184ms 44.2s 0 transport_latency_assumed book c 429,200 313,129 3.1min 18.1h 28.2d 103.3d 0 book_staleness book e 480,594 212,608 4.2min 18.6h 28.5d 103.4d 0 book_staleness book f 449,168 201,425 3.8min 18.3h 28.5d 103.3d 0 book_staleness book g 170,879 41,311 93ms 2.5h 8.3d 103.3d 0 book_staleness book h 423,386 189,803 2.9min 17.2h 25.6d 103.4d 0 book_staleness last_trade_price c 56,662 54,331 10ms 41ms 218ms 5.0s 0 transport_latency_assumed last_trade_price e 56,407 334 47ms 152ms 3.5s 9.5s 0 transport_latency_assumed last_trade_price f 56,136 154 52ms 132ms 5.7s 9.3s 0 transport_latency_assumed last_trade_price g 55,652 15 91ms 235ms 10.7s 22.6s 0 transport_latency_assumed last_trade_price h 56,669 1,905 23ms 79ms 475ms 11.3s 0 transport_latency_assumed market_resolved c 552 530 5ms 10ms 215ms 468ms 0 transport_latency_assumed market_resolved e 552 2 41ms 191ms 433ms 805ms 0 transport_latency_assumed market_resolved f 552 2 47ms 193ms 461ms 731ms 0 transport_latency_assumed market_resolved g 552 not meas. 88ms 349ms 811ms 1.4s 0 transport_latency_assumed market_resolved h 551 18 18ms 59ms 337ms 581ms 0 transport_latency_assumed new_market c 1,234 681 102ms 20.4s 42.8s 1.2min 0 transport_latency_assumed new_market e 1,234 249 169ms 20.4s 45.9s 1.2min 0 transport_latency_assumed new_market f 1,234 286 176ms 22.2s 43.6s 51.8s 0 transport_latency_assumed new_market g 1,234 156 279ms 21.0s 55.0s 1.3min 0 transport_latency_assumed new_market h 1,234 487 157ms 19.7s 42.6s 1.2min 0 transport_latency_assumed price_change c 89,565,984 86,128,382 5ms 10ms 137ms 9.5s 0 transport_latency_assumed price_change e 89,512,454 366,119 40ms 47ms 230ms 9.5s 0 transport_latency_assumed price_change f 89,522,816 153,769 45ms 55ms 244ms 9.3s 0 transport_latency_assumed price_change g 89,485,624 13,946 76ms 115ms 499ms 22.7s 0 transport_latency_assumed price_change h 89,544,760 2,927,596 17ms 27ms 221ms 45.0s 0 transport_latency_assumed tick_size_change c 1,932 1,885 5ms 7ms 26ms 133ms 0 transport_latency_assumed tick_size_change e 1,932 not meas. 40ms 49ms 119ms 215ms 0 transport_latency_assumed tick_size_change f 1,932 not meas. 45ms 50ms 139ms 195ms 0 transport_latency_assumed tick_size_change g 1,932 not meas. 76ms 93ms 280ms 541ms 0 transport_latency_assumed tick_size_change h 1,932 47 17ms 25ms 107ms 837ms 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-10/06/2026-09-10T06.parquet sha256sum 2026-09-10T06.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.