Hour audit: 2026-09-15T16
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-15T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T16:00:00.000095204+00:00 · last event 2026-09-15T16:59:59.999767770+00:00
VOLUME 119,754,655 rows · 1,343,919,449 bytes (1.25 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 117,242,735 · e: 117,156,022 · f: 117,112,562 · g: 116,731,598 · c: 85,399,142 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 34,396,489 (28.72%) · e: 3,829,904 (3.20%) · f: 1,708,979 (1.43%) · g: 153,584 (0.13%) · c: 79,665,699 (66.52%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 8d8380d3b7cf9fa31a66e29bd2e75dc2fd237ed842a2debabbae8b008eb2b130
the corpus checksum ledger names this file with the same digest
joined 119,756,537 to merged 119,754,655, minus 1,882 (minus 0.0016%)
boundary drops 1,882 · 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-15T17:59:48Z 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,198,150 145,892,001 0-46 d73f085ee05d33bd39db7637fe2334b8af5096bd0b56b213b361b43b044873a7 book 2,584,615 105,668,471 47-56 be3553c648899dbaa43750660f8c49ad10392c7663132b177cc3762601440a50 last_trade_price 61,642 3,561,685 57-57 60b78fed14c7244e4e3a02027efc68f9394f1b30c1fd22a3bccefd29500d0c4e market_resolved 1,594 190,259 58-58 06246c6d4364ef6f867385675f18ba23f12f4c79804ab8d9c6b8506851d80893 new_market 8,728 693,314 59-59 7322fa30cf84fe06e937c796ab20efe678de0904257820aa2a9e799bfef7a9c6 price_change 104,896,834 1,086,435,911 60-460 ba72d301c5095a5fe855f988111f35eb538ab9bca318505e52176dd7ce2a3add tick_size_change 3,092 114,729 461-461 880466379e5a5bb3acf9ccf13bfd7ab5d460622b5af248ac00d2c2409ea60242 EVENT MIX count share price_change 104,896,834 87.59% best_bid_ask 12,198,150 10.19% book 2,584,615 2.16% last_trade_price 61,642 0.05% new_market 8,728 <0.01% tick_size_change 3,092 <0.01% market_resolved 1,594 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,198,383 12,198,150 233 4,677 FULL book 2,584,689 2,584,615 74 169,267 FULL last_trade_price 61,645 61,642 3 661 FULL market_resolved 1,594 1,594 0 82 FULL new_market 8,728 8,728 0 2 FULL price_change 104,898,406 104,896,834 1,572 1,643 FULL tick_size_change 3,092 3,092 0 238 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,665,416 8,131,187 6ms 16ms 172ms 4.9s 0 transport_latency_assumed best_bid_ask e 12,193,796 414,867 39ms 67ms 329ms 16.3s 0 transport_latency_assumed best_bid_ask f 12,192,169 159,544 43ms 73ms 333ms 17.6s 0 transport_latency_assumed best_bid_ask g 12,183,542 9,364 84ms 178ms 793ms 26.8s 0 transport_latency_assumed best_bid_ask h 12,195,544 3,483,188 18ms 47ms 345ms 56.3s 0 transport_latency_assumed book c 2,501,236 2,466,391 4.2min 3.1d 38.0d 108.8d 0 book_staleness book e 143,052 11,073 45ms 4.3s 4.7h 90.3d 0 book_staleness book f 183,868 21,279 89ms 29.3min 10.1d 108.7d 0 book_staleness book g 229,923 43,713 1.2s 1.0h 24.1d 108.8d 0 book_staleness book h 139,633 42,159 24ms 374ms 13.8min 90.2d 0 book_staleness last_trade_price c 43,528 40,232 12ms 57ms 295ms 5.0s 0 transport_latency_assumed last_trade_price e 61,159 1,433 59ms 633ms 10.7s 16.4s 0 transport_latency_assumed last_trade_price f 60,876 781 62ms 339ms 8.3s 17.4s 0 transport_latency_assumed last_trade_price g 59,237 84 109ms 926ms 15.4s 26.9s 0 transport_latency_assumed last_trade_price h 61,375 19,112 26ms 99ms 642ms 51.4s 0 transport_latency_assumed market_resolved c 1,190 1,165 8ms 6.1min 12.4min 15.1min 0 transport_latency_assumed market_resolved e 1,133 14 57ms 280ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 1,133 12 57ms 237ms 702ms 35.8s 0 transport_latency_assumed market_resolved g 1,133 1 116ms 417ms 1.3s 20.6s 0 transport_latency_assumed market_resolved h 1,133 402 25ms 108ms 56.2s 56.8s 0 transport_latency_assumed new_market c 6,738 5,093 45.8s 11.9min 15.2min 15.6min 0 transport_latency_assumed new_market e 4,214 886 166ms 53.3s 7.6min 11.1min 0 transport_latency_assumed new_market f 4,214 945 148ms 1.1min 8.0min 11.0min 0 transport_latency_assumed new_market g 4,215 501 268ms 1.3min 7.5min 76.0d 0 transport_latency_assumed new_market h 4,214 1,303 121ms 53.1s 7.6min 11.1min 0 transport_latency_assumed price_change c 74,178,890 69,019,734 6ms 21ms 212ms 4.9s 0 transport_latency_assumed price_change e 104,749,576 3,401,497 40ms 107ms 1.9s 16.6s 0 transport_latency_assumed price_change f 104,667,214 1,526,336 44ms 108ms 1.4s 17.8s 0 transport_latency_assumed price_change g 104,250,460 99,912 85ms 261ms 4.3s 28.2s 0 transport_latency_assumed price_change h 104,837,744 30,849,355 19ms 56ms 410ms 56.6s 0 transport_latency_assumed tick_size_change c 2,144 1,897 6ms 39ms 321ms 412ms 0 transport_latency_assumed tick_size_change e 3,092 134 40ms 104ms 399ms 1.4s 0 transport_latency_assumed tick_size_change f 3,088 82 44ms 106ms 468ms 603ms 0 transport_latency_assumed tick_size_change g 3,088 9 85ms 236ms 632ms 1.3s 0 transport_latency_assumed tick_size_change h 3,092 970 19ms 66ms 368ms 1.2s 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-15/16/2026-09-15T16.parquet sha256sum 2026-09-15T16.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.