Hour audit: 2026-09-28T06
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-28T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T06:00:00.000008024+00:00 · last event 2026-09-28T06:59:59.999873877+00:00
VOLUME 93,704,373 rows · 952,433,803 bytes (908.31 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 93,607,746 · h: 93,576,949 · g: 93,460,390 · i: 92,633,462 · c: 92,596,087 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 6,315,640 (6.74%) · h: 1,103,417 (1.18%) · g: 16,890 (0.02%) · i: 1,101,420 (1.18%) · c: 85,167,006 (90.89%) (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 93,704,373 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 69bc0f0f7be7f486c01439bc4a4fb8023875bda67680c51850be0852da026bb7
the corpus checksum ledger names this file with the same digest
joined 93,706,616 to merged 93,704,373, minus 2,243 (minus 0.0024%)
boundary drops 2,243 · 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-28T08:37:14Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 9,762,538 108,693,386 0-37 47f9520b9cb3d53765a1176e5e47579cde96db64b98f4d9a508a847c92acd6c9 book 127,008 13,140,434 38-38 744173a57248c76e5ff1518b2b3ba19e8e04c5db49213e0bf5142585472393f1 last_trade_price 45,008 2,584,466 39-39 ac7c7e8899cbf8c56f18d8e06cb06c67d479c8307017a34eeab7cf2a9489747b market_resolved 820 125,232 40-40 ca68ac43d553f5b8c6782921f0d5d6f23fafbd8a5b926e6544cd94295a953a44 new_market 2,279 241,673 41-41 6f2eae28b07b6f892aee6edca84fd5cf2afc05272b1db8a2aa73f5471090cfae price_change 83,764,836 826,508,469 42-361 b78b6efb6ba903da8a4572448ad04a22669be305a473b9f2e9e80e735457e18a tick_size_change 1,884 69,350 362-362 2f775fbfadcbc696bfeb77a8123e168a8f9aef461127e557f76ae9fc19463160 EVENT MIX count share price_change 83,764,836 89.39% best_bid_ask 9,762,538 10.42% book 127,008 0.14% last_trade_price 45,008 0.05% new_market 2,279 <0.01% tick_size_change 1,884 <0.01% market_resolved 820 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,762,794 9,762,538 256 621 FULL book 127,008 127,008 0 12,558 FULL last_trade_price 45,009 45,008 1 51 FULL market_resolved 820 820 0 11 FULL new_market 2,279 2,279 0 0 FULL price_change 83,766,822 83,764,836 1,986 864 FULL tick_size_change 1,884 1,884 0 10 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,687,868 8,985,813 5ms 11ms 185ms 18.9s 0 transport_latency_assumed best_bid_ask g 9,757,752 737 77ms 100ms 606ms 34.0s 0 transport_latency_assumed best_bid_ask h 9,759,566 104,561 19ms 36ms 505ms 1.2min 0 transport_latency_assumed best_bid_ask i 9,645,602 105,546 29ms 35ms 138ms 4.0s 0 transport_latency_assumed best_bid_ask k 9,760,098 565,881 12ms 19ms 205ms 28.0s 0 transport_latency_assumed book c 99,782 89,080 7ms 987ms 3.4d 102.8d 0 book_staleness book g 98,259 6,894 83ms 1.8s 1.1d 102.8d 0 book_staleness book h 103,658 12,389 26ms 10.6s 7.6d 121.4d 0 book_staleness book i 93,942 3,629 31ms 96ms 17.5min 102.8d 0 book_staleness book k 100,692 15,016 16ms 683ms 1.5d 102.8d 0 book_staleness last_trade_price c 44,207 39,781 6ms 25ms 387ms 4.8s 0 transport_latency_assumed last_trade_price g 44,358 8 82ms 261ms 7.0s 33.8s 0 transport_latency_assumed last_trade_price h 44,819 550 21ms 97ms 882ms 47.1s 0 transport_latency_assumed last_trade_price i 44,786 773 31ms 64ms 352ms 2.4s 0 transport_latency_assumed last_trade_price k 44,704 3,896 14ms 36ms 323ms 14.0s 0 transport_latency_assumed market_resolved c 764 607 5ms 24.6s 52.2s 56.0s 0 transport_latency_assumed market_resolved g 767 26 83ms 35.0s 45.0s 48.9s 0 transport_latency_assumed market_resolved h 767 5 23ms 27.0s 53.5s 57.1s 0 transport_latency_assumed market_resolved i 758 135 32ms 24.8s 53.4s 1.5min 0 transport_latency_assumed market_resolved k 767 47 13ms 28.3s 57.7s 57.8s 0 transport_latency_assumed new_market c 1,625 919 284ms 1.2min 1.6min 1.7min 0 transport_latency_assumed new_market g 1,625 227 516ms 1.2min 1.6min 1.8min 0 transport_latency_assumed new_market h 1,625 262 356ms 1.2min 1.6min 1.8min 0 transport_latency_assumed new_market i 1,625 481 171ms 1.3min 1.6min 1.7min 0 transport_latency_assumed new_market k 1,625 390 344ms 1.2min 1.6min 1.8min 0 transport_latency_assumed price_change c 82,759,977 76,049,058 5ms 14ms 220ms 18.9s 0 transport_latency_assumed price_change g 83,555,745 8,998 77ms 122ms 1.1s 34.3s 0 transport_latency_assumed price_change h 83,664,630 985,630 19ms 46ms 564ms 1.7min 0 transport_latency_assumed price_change i 82,844,889 990,848 29ms 40ms 218ms 6.2s 0 transport_latency_assumed price_change k 83,697,976 5,730,302 12ms 23ms 232ms 28.4s 0 transport_latency_assumed tick_size_change c 1,864 1,748 5ms 13ms 74ms 149ms 0 transport_latency_assumed tick_size_change g 1,884 not meas. 76ms 92ms 208ms 813ms 0 transport_latency_assumed tick_size_change h 1,884 20 19ms 37ms 212ms 10.3s 0 transport_latency_assumed tick_size_change i 1,860 8 29ms 37ms 70ms 105ms 0 transport_latency_assumed tick_size_change k 1,884 108 12ms 18ms 75ms 369ms 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-28/06/2026-09-28T06.parquet sha256sum 2026-09-28T06.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.