Hour audit: 2026-09-11T14
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-11T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T14:00:00.000026163+00:00 · last event 2026-09-11T14:59:59.999890512+00:00
VOLUME 120,735,399 rows · 1,325,453,213 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 118,114,929 · h: 118,098,496 · g: 117,920,941 · f: 112,013,727 · c: 87,764,124 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 2,658,843 (2.20%) · h: 34,454,250 (28.54%) · g: 67,638 (0.06%) · f: 621,868 (0.52%) · c: 82,932,800 (68.69%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 0ae649b47fbb3cf17a15d0d8ddc1b3d2c7fa102aa7c8f10fdda8746f6d860eab
the corpus checksum ledger names this file with the same digest
joined 120,739,917 to merged 120,735,399, minus 4,518 (minus 0.0037%)
boundary drops 4,518 · 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-11T16:00:26Z 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 10,519,341 122,905,660 0-40 44dc6012225a1f82c704a4d4803374bee7597308354e71fd711fddbdefb4c877 book 2,719,838 111,182,068 41-51 b0f871e85f4ba950fafbd621b7b36a6d8f1eb32d07043b388a78580e3b737ade last_trade_price 67,594 3,852,662 52-52 9d4f386964ca61828dce24e23b7aa9b15a8d9bbd95c485dad8483cc27c9e9529 market_resolved 1,112 120,618 53-53 4571cb591b6f7a4203da8865d36792b35255563b834d8522b7ece39435c20b76 new_market 1,104 110,954 54-54 7576c25787ee929ae339ef1f4a6bf24f61dec9a1203183a36b296e0cae036554 price_change 107,423,334 1,085,791,732 55-464 e39b701e79ebfa45101cc67e39a7d2be6af978bc73c5dd603977f699768bbbc1 tick_size_change 3,076 114,086 465-465 9b7bd63efa820960735269864cb635ff0bca17e2cfcb89f84cc390cfcbdfa268 EVENT MIX count share price_change 107,423,334 88.97% best_bid_ask 10,519,341 8.71% book 2,719,838 2.25% last_trade_price 67,594 0.06% tick_size_change 3,076 <0.01% market_resolved 1,112 <0.01% new_market 1,104 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,519,525 10,519,341 184 8,456 FULL book 2,721,328 2,719,838 1,490 202,211 FULL last_trade_price 67,596 67,594 2 795 FULL market_resolved 1,112 1,112 0 71 FULL new_market 1,104 1,104 0 2 FULL price_change 107,426,176 107,423,334 2,842 3,916 FULL tick_size_change 3,076 3,076 0 271 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,532,818 7,122,511 6ms 14ms 121ms 7.8s 0 transport_latency_assumed best_bid_ask e 10,516,722 237,333 38ms 50ms 229ms 12.0s 0 transport_latency_assumed best_bid_ask f 9,947,385 38,073 46ms 62ms 263ms 15.8s 0 transport_latency_assumed best_bid_ask g 10,511,107 2,870 78ms 111ms 471ms 18.6s 0 transport_latency_assumed best_bid_ask h 10,515,675 3,118,554 18ms 33ms 168ms 50.6s 0 transport_latency_assumed book c 2,531,057 2,502,349 20.6min 1.3d 30.8d 104.7d 0 book_staleness book e 145,785 5,279 43ms 868ms 5.5h 86.2d 0 book_staleness book f 583,230 149,289 4.6min 23.3h 26.4d 104.7d 0 book_staleness book g 197,349 21,735 142ms 3.5h 8.4d 86.2d 0 book_staleness book h 144,702 41,186 22ms 73ms 58.7min 86.0d 0 book_staleness last_trade_price c 49,715 46,941 11ms 47ms 224ms 5.7s 0 transport_latency_assumed last_trade_price e 67,301 1,200 54ms 380ms 6.0s 12.0s 0 transport_latency_assumed last_trade_price f 63,026 411 60ms 256ms 3.8s 15.8s 0 transport_latency_assumed last_trade_price g 66,006 37 98ms 825ms 10.5s 18.4s 0 transport_latency_assumed last_trade_price h 67,366 19,005 25ms 77ms 402ms 8.6s 0 transport_latency_assumed market_resolved c 836 813 11ms 13.0min 18.8min 18.8min 0 transport_latency_assumed market_resolved e 709 18 39ms 142ms 443ms 834ms 0 transport_latency_assumed market_resolved f 715 30 48ms 199ms 6.7min 6.7min 0 transport_latency_assumed market_resolved g 709 1 85ms 260ms 773ms 1.1s 0 transport_latency_assumed market_resolved h 709 250 19ms 61ms 153ms 325ms 0 transport_latency_assumed new_market c 808 488 167ms 4.0min 13.9min 14.4min 0 transport_latency_assumed new_market e 698 130 187ms 14.5s 39.1s 1.1min 0 transport_latency_assumed new_market f 704 103 208ms 20.2s 6.4min 6.6min 0 transport_latency_assumed new_market g 696 89 309ms 13.5s 30.9s 1.1min 0 transport_latency_assumed new_market h 696 294 147ms 17.9s 33.4s 55.0s 0 transport_latency_assumed price_change c 77,646,754 73,257,680 6ms 16ms 142ms 8.1s 0 transport_latency_assumed price_change e 107,380,638 2,414,806 39ms 60ms 592ms 12.0s 0 transport_latency_assumed price_change f 101,415,735 433,942 46ms 72ms 517ms 15.8s 0 transport_latency_assumed price_change g 107,141,998 42,902 79ms 142ms 1.6s 18.6s 0 transport_latency_assumed price_change h 107,366,272 31,274,004 18ms 36ms 212ms 51.0s 0 transport_latency_assumed tick_size_change c 2,136 2,018 5ms 15ms 142ms 277ms 0 transport_latency_assumed tick_size_change e 3,076 77 39ms 84ms 258ms 963ms 0 transport_latency_assumed tick_size_change f 2,932 20 46ms 66ms 282ms 641ms 0 transport_latency_assumed tick_size_change g 3,076 4 78ms 125ms 646ms 1.3s 0 transport_latency_assumed tick_size_change h 3,076 957 18ms 35ms 242ms 788ms 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-11/14/2026-09-11T14.parquet sha256sum 2026-09-11T14.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.