Hour audit: 2026-09-16T20
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-16T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T20:00:00.000127843+00:00 · last event 2026-09-16T20:59:59.999905942+00:00
VOLUME 126,083,865 rows · 1,398,762,227 bytes (1.30 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 124,260,385 · e: 124,011,841 · g: 119,040,926 · f: 114,462,710 · c: 110,635,198 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 19,024,190 (15.09%) · e: 1,998,854 (1.59%) · g: 281,080 (0.22%) · f: 1,225,398 (0.97%) · c: 103,554,343 (82.13%) (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 126,083,865 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 10c5d8a596a61b8d1d5df801a6d063cea4ce2c2ebe654fbef40d470751d8d0b2
the corpus checksum ledger names this file with the same digest
joined 126,087,137 to merged 126,083,865, minus 3,272 (minus 0.0026%)
boundary drops 3,272 · 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-16T22:01:06Z 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,406,116 146,813,541 0-47 58d270264c6b1df01c3861b7beed7fb2b0dbe5a1ee763da5e9774a4fe70f5e33 book 1,942,356 100,335,927 48-55 05183fcf7eefcf48ccc47bf25af47bf5dd7e9373553a58f711865eb7ba1399af last_trade_price 59,613 3,397,795 56-56 201629a695f69a7ea6790c5ce83759cc1bf31f402b25dd8c70144c88738cd8ce market_resolved 2,413 329,431 57-57 ae1c733db286c4c46bbb0bd9e0dc37203da1bdc9325f70e5d65719417f00fcef new_market 5,949 543,502 58-58 a4e1d07f8d6c55f28b8505613fee406cc04049d22af8a20a55cdaa7fda58f4b9 price_change 111,661,514 1,145,695,728 59-484 d8f02c0c5a0dfe12d9a9129b2a142e3aeb3a2b4874816e46d0058db3937b6823 tick_size_change 5,904 212,503 485-485 b5dd115072b0dbbffe762184212775959852c49f00f8897b61b3b1ed047ec560 EVENT MIX count share price_change 111,661,514 88.56% best_bid_ask 12,406,116 9.84% book 1,942,356 1.54% last_trade_price 59,613 0.05% new_market 5,949 <0.01% tick_size_change 5,904 <0.01% market_resolved 2,413 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,406,403 12,406,116 287 2,719 FULL book 1,942,958 1,942,356 602 172,260 FULL last_trade_price 59,614 59,613 1 316 FULL market_resolved 2,413 2,413 0 102 FULL new_market 5,949 5,949 0 53 FULL price_change 111,663,896 111,661,514 2,382 1,089 FULL tick_size_change 5,904 5,904 0 172 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,979,629 10,298,334 5ms 18ms 271ms 8.4s 0 transport_latency_assumed best_bid_ask e 12,399,906 195,356 42ms 76ms 488ms 24.4s 0 transport_latency_assumed best_bid_ask f 11,402,338 73,843 47ms 78ms 483ms 32.7s 0 transport_latency_assumed best_bid_ask g 11,929,239 6,262 83ms 173ms 1.2s 40.0s 0 transport_latency_assumed best_bid_ask h 12,404,532 1,832,321 19ms 45ms 630ms 57.3s 0 transport_latency_assumed book c 1,332,446 1,158,209 3.3min 2.2d 36.1d 109.9d 0 book_staleness book e 198,612 48,551 297ms 12.1min 22.1d 109.9d 0 book_staleness book f 964,168 473,031 2.7min 1.5d 36.1d 109.9d 0 book_staleness book g 609,207 206,759 2.1min 18.6h 35.8d 109.9d 0 book_staleness book h 180,786 55,806 41ms 7.1min 11.3d 91.4d 0 book_staleness last_trade_price c 51,440 48,010 11ms 69ms 486ms 5.0s 0 transport_latency_assumed last_trade_price e 58,498 823 68ms 1.2s 10.3s 24.2s 0 transport_latency_assumed last_trade_price f 53,270 336 70ms 951ms 9.6s 33.1s 0 transport_latency_assumed last_trade_price g 54,738 103 113ms 1.8s 14.7s 40.5s 0 transport_latency_assumed last_trade_price h 59,534 10,341 27ms 162ms 1.1s 46.4s 0 transport_latency_assumed market_resolved c 1,955 1,854 5ms 193ms 9.8min 10.0min 0 transport_latency_assumed market_resolved e 2,019 20 73ms 199ms 618ms 58.0s 0 transport_latency_assumed market_resolved f 2,179 255 111ms 3.5min 12.3min 14.6min 0 transport_latency_assumed market_resolved g 2,009 8 106ms 347ms 1.6s 5.4min 0 transport_latency_assumed market_resolved h 2,019 276 32ms 78ms 397ms 58.3s 0 transport_latency_assumed new_market c 4,162 2,476 184ms 4.0min 17.0min 1.1h 0 transport_latency_assumed new_market e 3,388 661 242ms 1.3min 17.6min 19.2min 0 transport_latency_assumed new_market f 4,176 923 349ms 9.4min 17.3min 19.2min 0 transport_latency_assumed new_market g 3,339 638 392ms 2.0min 17.3min 1.0h 0 transport_latency_assumed new_market h 3,388 1,251 193ms 1.3min 17.6min 19.2min 0 transport_latency_assumed price_change c 98,260,086 92,040,340 5ms 21ms 284ms 8.4s 0 transport_latency_assumed price_change e 111,343,514 1,753,362 43ms 115ms 2.0s 25.1s 0 transport_latency_assumed price_change f 102,030,943 676,996 47ms 114ms 1.5s 33.1s 0 transport_latency_assumed price_change g 106,436,658 67,310 84ms 268ms 4.2s 44.5s 0 transport_latency_assumed price_change h 111,604,226 17,123,506 19ms 53ms 691ms 57.3s 0 transport_latency_assumed tick_size_change c 5,480 5,120 5ms 16ms 77ms 925ms 0 transport_latency_assumed tick_size_change e 5,904 81 42ms 60ms 234ms 433ms 0 transport_latency_assumed tick_size_change f 5,636 14 46ms 58ms 181ms 3.8s 0 transport_latency_assumed tick_size_change g 5,736 not meas. 82ms 102ms 418ms 3.0s 0 transport_latency_assumed tick_size_change h 5,900 689 19ms 31ms 145ms 1.3s 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-16/20/2026-09-16T20.parquet sha256sum 2026-09-16T20.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.