Hour audit: 2026-09-06T02
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-06T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T02:00:00.055451928+00:00 · last event 2026-09-06T02:59:59.999999038+00:00
VOLUME 133,035,053 rows · 1,384,102,521 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 130,797,828 · f: 126,242,681 · h: 125,859,066 · g: 125,632,520 · c: 107,447,313 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,558,755 (1.17%) · f: 4,169,860 (3.13%) · h: 115,363 (0.09%) · g: 125,630,130 (94.43%) · c: 1,560,945 (1.17%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 133,035,053 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8e901bdd859275719dc86417e175772c7697fa8346f28ed916ac1de800811d2a
the corpus checksum ledger names this file with the same digest
joined 133,037,465 to merged 133,035,053, minus 2,412 (minus 0.0018%)
boundary drops 2,412 · 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-06T05:51:59Z 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 12,957,195 138,805,448 0-49 ee0594fd513698d749255ccc1049e45334e90721a62f81fce95750c72abbe0a3 book 2,264,892 91,980,358 50-58 8501260694f3283b4c50d390e17c46b4c524c950ffd68c091f7a6dffa4ad69b9 last_trade_price 52,336 2,965,134 59-59 4dadfd79e1b6a9e51a612029a84b2d539d2f755ca21db10be7b8e5c5e9e62ef7 market_resolved 5,089 573,337 60-60 20aec6c7374a0a4250374f46843690881e1f527f9145425341f5d94a400a3d06 new_market 1,105 108,099 61-61 52e808ecb303c948ba4a9ef1125fd85be657c690279280d695a212fd82b59542 price_change 117,746,938 1,147,894,875 62-511 3ba17d7d695984cc400e53bb87784ec6aae813a1d7d7e030c1fb5c0f13759b5b tick_size_change 7,498 264,133 512-512 fd510fd3f26fa45bb93745331bc7be073f0d0fdd07a78a06343c3bac825d4da8 EVENT MIX count share price_change 117,746,938 88.51% best_bid_ask 12,957,195 9.74% book 2,264,892 1.70% last_trade_price 52,336 0.04% tick_size_change 7,498 <0.01% market_resolved 5,089 <0.01% new_market 1,105 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,957,446 12,957,195 251 3,150 FULL book 2,264,930 2,264,892 38 179,153 FULL last_trade_price 52,337 52,336 1 553 FULL market_resolved 5,089 5,089 0 425 FULL new_market 1,105 1,105 0 20 FULL price_change 117,749,060 117,746,938 2,122 2,356 FULL tick_size_change 7,498 7,498 0 678 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,449,949 309 4ms 8ms 70ms 3.3s 0 transport_latency_assumed best_bid_ask e 12,956,171 155,054 39ms 45ms 132ms 2.6s 0 transport_latency_assumed best_bid_ask f 12,496,668 381,440 48ms 56ms 157ms 4.1s 0 transport_latency_assumed best_bid_ask g 12,420,144 12,419,893 82ms 101ms 313ms 14.0s 0 transport_latency_assumed best_bid_ask h 12,445,748 499 18ms 42ms 118ms 22.8s 0 transport_latency_assumed book c 1,903,862 1,556,237 26.9min 13.1h 34.6d 99.2d 0 book_staleness book e 108,854 1,686 41ms 83ms 2.1s 80.5d 0 book_staleness book f 467,108 118,038 3.2min 11.4h 33.3d 99.2d 0 book_staleness book g 478,762 478,746 3.6min 11.4h 33.2d 99.2d 0 book_staleness book h 469,588 110,185 3.3min 11.4h 33.3d 99.2d 0 book_staleness last_trade_price c 42,061 4 10ms 41ms 227ms 5.0s 0 transport_latency_assumed last_trade_price e 52,260 702 45ms 85ms 495ms 5.1s 0 transport_latency_assumed last_trade_price f 50,037 2,579 54ms 99ms 541ms 5.0s 0 transport_latency_assumed last_trade_price g 49,044 49,043 92ms 161ms 1.1s 14.1s 0 transport_latency_assumed last_trade_price h 50,074 8 24ms 72ms 310ms 9.2s 0 transport_latency_assumed market_resolved c 4,208 1,322 5ms 9.0min 15.3min 15.7min 0 transport_latency_assumed market_resolved e 3,437 58 41ms 119ms 349ms 46.1s 0 transport_latency_assumed market_resolved f 3,377 196 50ms 132ms 5.4min 5.6min 0 transport_latency_assumed market_resolved g 3,471 3,471 88ms 297ms 5.1min 5.4min 0 transport_latency_assumed market_resolved h 3,299 42 29ms 70ms 1.8min 6.7min 0 transport_latency_assumed new_market c 690 81 85ms 6.7min 2.4h 4.7h 0 transport_latency_assumed new_market e 648 72 130ms 19.3s 40.0s 45.8min 0 transport_latency_assumed new_market f 664 190 122ms 21.8s 1.7h 3.7h 0 transport_latency_assumed new_market g 649 649 229ms 19.4s 41.2s 3.1h 0 transport_latency_assumed new_market h 684 113 135ms 33.0s 45.8min 3.7h 0 transport_latency_assumed price_change c 95,040,879 2,992 5ms 9ms 76ms 3.3s 0 transport_latency_assumed price_change e 117,668,960 1,401,183 39ms 47ms 156ms 2.8s 0 transport_latency_assumed price_change f 113,217,625 3,667,073 48ms 58ms 175ms 4.1s 0 transport_latency_assumed price_change g 112,673,296 112,671,174 83ms 104ms 351ms 14.1s 0 transport_latency_assumed price_change h 112,882,627 4,516 18ms 45ms 127ms 23.3s 0 transport_latency_assumed tick_size_change c 5,664 not meas. 5ms 7ms 36ms 192ms 0 transport_latency_assumed tick_size_change e 7,498 not meas. 38ms 43ms 85ms 224ms 0 transport_latency_assumed tick_size_change f 7,202 344 48ms 53ms 106ms 359ms 0 transport_latency_assumed tick_size_change g 7,154 7,154 82ms 103ms 233ms 363ms 0 transport_latency_assumed tick_size_change h 7,046 not meas. 18ms 35ms 71ms 1.4s 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-06/02/2026-09-06T02.parquet sha256sum 2026-09-06T02.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.