Hour audit: 2026-09-06T21
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-06T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T21:00:00.000114543+00:00 · last event 2026-09-06T21:59:59.999755307+00:00
VOLUME 117,081,069 rows · 1,242,962,636 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 115,253,075 · g: 115,209,076 · h: 115,065,878 · e: 115,065,188 · c: 94,331,000 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 614,685 (0.53%) · g: 64,257 (0.05%) · h: 23,367,049 (19.96%) · e: 2,781,720 (2.38%) · c: 90,253,358 (77.09%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 87fd32b597ac64fca354fbd25056f512bf49065b376ff0f7a5e739d63fa2cfc1
the corpus checksum ledger names this file with the same digest
joined 117,083,805 to merged 117,081,069, minus 2,736 (minus 0.0023%)
boundary drops 2,736 · 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-07T02:17:25Z 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,123,665 135,867,539 0-46 d15911aaf026d177f75967d34e7a4cc4238d26d2d1aef9947584f76511143aae book 1,937,602 79,854,553 47-54 e41522348ef7d67266c2a6ad434f320f03cf5feb0efca2e4cf7ad212cdd09a88 last_trade_price 56,018 3,163,201 55-55 7490b481efcb91d06c7ffa639ebe3d55244a02b1a81fad78b469838af670ad29 market_resolved 5,929 623,008 56-56 503dcbfa9eb3bb074ea6027c0a2270589988e0d11eb89946bc07e75a4ef63df3 new_market 4,713 377,532 57-57 6272c43c1137c84efb8e7b380591e822c12dcaa4ee479b5832c3b16d40de7225 price_change 102,948,174 1,021,562,446 58-450 093cafb647f60c7d8b73b276b1d8af66b7136b0c767a8c5c8a3a57b2812136d2 tick_size_change 4,968 181,797 451-451 e38902c99391122bd384beb73bfa97f268a11177563b31b62f7ae5e5764edf16 EVENT MIX count share price_change 102,948,174 87.93% best_bid_ask 12,123,665 10.35% book 1,937,602 1.65% last_trade_price 56,018 0.05% market_resolved 5,929 <0.01% tick_size_change 4,968 <0.01% new_market 4,713 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,123,940 12,123,665 275 4,902 FULL book 1,937,798 1,937,602 196 174,371 FULL last_trade_price 56,019 56,018 1 416 FULL market_resolved 5,929 5,929 0 246 FULL new_market 4,713 4,713 0 0 FULL price_change 102,950,438 102,948,174 2,264 2,779 FULL tick_size_change 4,968 4,968 0 207 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,721,807 9,306,111 5ms 11ms 183ms 8.1s 0 transport_latency_assumed best_bid_ask e 12,119,552 280,283 37ms 48ms 292ms 9.4s 0 transport_latency_assumed best_bid_ask f 12,119,560 55,993 46ms 60ms 304ms 8.3s 0 transport_latency_assumed best_bid_ask g 12,117,065 4,800 82ms 118ms 696ms 25.6s 0 transport_latency_assumed best_bid_ask h 12,120,359 2,476,478 17ms 32ms 327ms 1.0min 0 transport_latency_assumed book c 1,887,605 1,880,531 7.9min 1.0d 35.4d 100.0d 0 book_staleness book e 119,729 7,643 40ms 327ms 8.0s 34.0d 0 book_staleness book f 140,114 11,211 51ms 1.6min 4.2d 100.0d 0 book_staleness book g 143,420 12,246 93ms 3.9min 4.9d 100.0d 0 book_staleness book h 119,790 25,971 22ms 144ms 4.2s 81.4d 0 book_staleness last_trade_price c 43,080 41,058 10ms 43ms 302ms 5.0s 0 transport_latency_assumed last_trade_price e 55,998 2,179 44ms 215ms 6.4s 9.4s 0 transport_latency_assumed last_trade_price f 55,991 323 54ms 264ms 4.6s 8.4s 0 transport_latency_assumed last_trade_price g 55,681 74 95ms 475ms 11.8s 24.8s 0 transport_latency_assumed last_trade_price h 55,890 12,384 23ms 99ms 714ms 13.3s 0 transport_latency_assumed market_resolved c 5,135 5,051 9ms 13.6min 18.7min 19.2min 0 transport_latency_assumed market_resolved e 3,665 104 83ms 194ms 553ms 1.0min 0 transport_latency_assumed market_resolved f 3,665 23 85ms 199ms 456ms 1.0s 0 transport_latency_assumed market_resolved g 3,665 3 110ms 348ms 863ms 2.5s 0 transport_latency_assumed market_resolved h 3,665 748 35ms 83ms 312ms 48.3s 0 transport_latency_assumed new_market c 3,700 2,735 279ms 13.3min 50.1min 3.7h 0 transport_latency_assumed new_market e 2,337 430 187ms 18.4s 26.3s 2.9h 0 transport_latency_assumed new_market f 2,337 423 172ms 18.2s 26.3s 45.4min 0 transport_latency_assumed new_market g 2,337 375 291ms 19.1s 27.1s 32.4s 0 transport_latency_assumed new_market h 2,337 750 156ms 18.3s 28.9s 36.3min 0 transport_latency_assumed price_change c 82,665,533 79,013,954 5ms 12ms 194ms 8.1s 0 transport_latency_assumed price_change e 102,758,939 2,491,023 38ms 55ms 351ms 9.4s 0 transport_latency_assumed price_change f 102,926,440 546,680 47ms 67ms 360ms 8.3s 0 transport_latency_assumed price_change g 102,881,940 46,755 83ms 137ms 826ms 25.6s 0 transport_latency_assumed price_change h 102,758,869 20,849,762 17ms 36ms 354ms 1.0min 0 transport_latency_assumed tick_size_change c 4,140 3,918 5ms 11ms 393ms 3.9s 0 transport_latency_assumed tick_size_change e 4,968 58 38ms 76ms 337ms 779ms 0 transport_latency_assumed tick_size_change f 4,968 32 46ms 126ms 491ms 786ms 0 transport_latency_assumed tick_size_change g 4,968 4 83ms 217ms 834ms 1.5s 0 transport_latency_assumed tick_size_change h 4,968 956 17ms 34ms 322ms 6.5s 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/21/2026-09-06T21.parquet sha256sum 2026-09-06T21.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.