Hour audit: 2026-09-07T20
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-07T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T20:00:00.000039061+00:00 · last event 2026-09-07T20:59:59.999865148+00:00
VOLUME 94,214,318 rows · 954,922,483 bytes (910.69 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 94,188,280 · c: 94,187,183 · f: 94,105,066 · g: 93,967,374 · e: 91,932,693 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,990,904 (5.30%) · c: 88,392,944 (93.82%) · f: 302,924 (0.32%) · g: 32,111 (0.03%) · e: 495,435 (0.53%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 94,214,318 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 16fe6129931549b0b673dafeff38d30b55e789ae861469029749d645f3248a6c
the corpus checksum ledger names this file with the same digest
joined 94,217,688 to merged 94,214,318, minus 3,370 (minus 0.0036%)
boundary drops 3,370 · 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-07T21:55:38Z 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,875,636 116,686,023 0-41 9e3902ac326da8611b2acccbce9023671dd9420b10983ef14ac75e941d7bc7cf book 144,136 14,067,137 42-42 0dac8dc546ec4c9482e684c23db725d0b3ad2d0d0c8b0ed69a1146d4a818cef6 last_trade_price 57,108 3,205,855 43-43 3ddc93adb2e1a8b64a6f5f888e2fbb7c8bd4d442f41787d0f5f1c584ffe9cd3d market_resolved 2,576 413,260 44-44 6c24b1c762dd7857a689da2d2f02e7de677a561fd5cb029c519a40fc8d67435e new_market 4,600 452,092 45-45 fff71f9f24eb8be5fc858fda25b9e50fcd6aeef42bab4f9d712fac3db3b0eb7e price_change 83,125,394 818,845,418 46-363 c8861c3845ce963cc005812c807cc2a52740348e0cd2002a5ca922f62d8bba9f tick_size_change 4,868 175,611 364-364 f5d24d4bf7a652fa6ae4411336919e4807b60216dd595ef97a02bc5fa81f9b6a EVENT MIX count share price_change 83,125,394 88.23% best_bid_ask 10,875,636 11.54% book 144,136 0.15% last_trade_price 57,108 0.06% tick_size_change 4,868 <0.01% new_market 4,600 <0.01% market_resolved 2,576 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,875,920 10,875,636 284 537 FULL book 144,251 144,136 115 8,366 FULL last_trade_price 57,113 57,108 5 47 FULL market_resolved 2,576 2,576 0 23 FULL new_market 4,600 4,600 0 0 FULL price_change 83,128,360 83,125,394 2,966 514 FULL tick_size_change 4,868 4,868 0 24 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,875,237 10,227,312 5ms 11ms 248ms 7.7s 0 transport_latency_assumed best_bid_ask e 10,742,286 61,994 41ms 51ms 357ms 26.0s 0 transport_latency_assumed best_bid_ask f 10,871,601 37,368 45ms 59ms 381ms 18.8s 0 transport_latency_assumed best_bid_ask g 10,867,668 2,504 81ms 130ms 860ms 50.2s 0 transport_latency_assumed best_bid_ask h 10,875,235 546,458 13ms 22ms 637ms 1.0min 0 transport_latency_assumed book c 122,878 111,685 7ms 54ms 3.4s 10.1min 0 book_staleness book e 115,148 8,443 43ms 2.5s 10.0h 82.4d 0 book_staleness book f 123,651 3,073 48ms 730ms 1.7min 82.2d 0 book_staleness book g 131,569 11,801 94ms 4.8s 10.5h 82.4d 0 book_staleness book h 123,388 9,134 17ms 119ms 4.1s 82.3d 0 book_staleness last_trade_price c 57,087 53,174 10ms 51ms 411ms 5.0s 0 transport_latency_assumed last_trade_price e 50,079 215 47ms 192ms 3.7s 26.0s 0 transport_latency_assumed last_trade_price f 56,609 133 52ms 283ms 6.5s 18.8s 0 transport_latency_assumed last_trade_price g 55,984 7 99ms 692ms 10.1s 48.3s 0 transport_latency_assumed last_trade_price h 57,066 3,579 18ms 75ms 776ms 40.3s 0 transport_latency_assumed market_resolved c 2,563 2,385 5ms 20ms 367ms 1.2s 0 transport_latency_assumed market_resolved e 2,540 28 72ms 200ms 740ms 2.0min 0 transport_latency_assumed market_resolved f 2,563 17 80ms 213ms 640ms 1.0min 0 transport_latency_assumed market_resolved g 2,563 not meas. 112ms 419ms 1.1s 3.8s 0 transport_latency_assumed market_resolved h 2,563 146 19ms 57ms 680ms 43.8s 0 transport_latency_assumed new_market c 2,794 1,404 180ms 56.6s 4.1min 27.8d 0 transport_latency_assumed new_market e 2,794 774 201ms 48.5s 3.9min 27.8d 0 transport_latency_assumed new_market f 2,794 525 269ms 52.2s 4.2min 27.8d 0 transport_latency_assumed new_market g 2,794 335 348ms 52.0s 4.1min 27.9d 0 transport_latency_assumed new_market h 2,794 1,562 156ms 1.0min 4.2min 27.8d 0 transport_latency_assumed price_change c 83,121,756 77,992,364 5ms 12ms 259ms 8.9s 0 transport_latency_assumed price_change e 81,015,074 423,948 41ms 63ms 470ms 26.0s 0 transport_latency_assumed price_change f 83,042,980 261,788 45ms 71ms 523ms 18.8s 0 transport_latency_assumed price_change g 82,901,928 17,460 82ms 170ms 1.3s 50.3s 0 transport_latency_assumed price_change h 83,122,366 4,429,834 13ms 24ms 570ms 1.0min 0 transport_latency_assumed tick_size_change c 4,868 4,620 5ms 10ms 475ms 807ms 0 transport_latency_assumed tick_size_change e 4,772 33 41ms 102ms 533ms 676ms 0 transport_latency_assumed tick_size_change f 4,868 20 46ms 85ms 501ms 731ms 0 transport_latency_assumed tick_size_change g 4,868 4 82ms 256ms 919ms 2.0s 0 transport_latency_assumed tick_size_change h 4,868 191 13ms 25ms 691ms 7.8s 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-07/20/2026-09-07T20.parquet sha256sum 2026-09-07T20.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.