Hour audit: 2026-09-27T00
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-27T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T00:00:00.000000222+00:00 · last event 2026-09-27T00:59:59.999976578+00:00
VOLUME 142,214,687 rows · 1,590,706,418 bytes (1.48 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 130,624,798 · h: 130,523,265 · k: 125,470,700 · c: 107,247,017 · g: 16,618,594 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 2,344,039 (1.65%) · h: 8,334,286 (5.86%) · k: 32,426,548 (22.80%) · c: 99,006,325 (69.62%) · g: 103,489 (0.07%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 142,214,687 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 856166326fadd1f8703a271bb2b6f859f8995fc16dfaa950c6af8101c9cd33d1
the corpus checksum ledger names this file with the same digest
joined 142,218,928 to merged 142,214,687, minus 4,241 (minus 0.0030%)
boundary drops 4,241 · 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-28T09:07:29Z 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 15,973,396 179,966,939 0-60 6535330f715b7b6dc4a5105f32d9589f37c014af2fbc2a7e8e155b7175e4f96f book 3,339,964 116,131,065 61-73 de754ef801279aeaafed76e38ab34f25745363f0fed8d1cb88c6bea1f66b770a last_trade_price 52,001 2,991,267 74-74 d8d8e52d64bf159396a492d127c4ca9797a3b39af479bd8bcf57e0a879906cda market_resolved 5,195 493,846 75-75 69bdf51a1d066192609df90fd5ad2c83e062194f761e6862deef2c0fb5799f8c new_market 1,052 85,404 76-76 7a1d79d551714d2af32518f441bc26653a4e5c9b4d0770140eb810f94d1bde7d price_change 122,837,331 1,289,213,274 77-545 73e6105d038722313e7b1c8a879f4a66b20998817c551a883170ffae805f6349 tick_size_change 5,748 210,655 546-546 6a55b55881a6554e128e1f7e4b3836e433399e77a0ddc7a5755782ceca7bbc87 EVENT MIX count share price_change 122,837,331 86.37% best_bid_ask 15,973,396 11.23% book 3,339,964 2.35% last_trade_price 52,001 0.04% tick_size_change 5,748 <0.01% market_resolved 5,195 <0.01% new_market 1,052 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,973,428 15,973,396 32 28,833 FULL book 3,343,724 3,339,964 3,760 2,654 FULL last_trade_price 52,001 52,001 0 2,706 FULL market_resolved 5,214 5,195 19 2,183 FULL new_market 1,052 1,052 0 462 FULL price_change 122,837,761 122,837,331 430 30,339 FULL tick_size_change 5,748 5,748 0 1,252 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,075,007 11,229,781 5ms 12ms 79ms 1.7s 0 transport_latency_assumed best_bid_ask g 1,833,162 47 80ms 96ms 291ms 2.0s 0 transport_latency_assumed best_bid_ask h 14,896,338 907,077 18ms 55ms 127ms 15.6s 0 transport_latency_assumed best_bid_ask i 14,950,190 246,777 20ms 27ms 85ms 4.0s 0 transport_latency_assumed best_bid_ask k 14,266,620 3,589,714 12ms 18ms 69ms 1.1s 0 transport_latency_assumed book c 2,754,651 2,033,761 1.5h 5.7d 45.4d 120.1d 0 book_staleness book g 428,690 102,951 1.6h 5.4d 45.4d 120.1d 0 book_staleness book h 928,929 186,240 1.0h 5.2d 42.5d 120.1d 0 book_staleness book i 930,996 119,508 1.0h 5.2d 42.5d 120.1d 0 book_staleness book k 1,340,456 897,504 1.2h 5.2d 45.2d 120.1d 0 book_staleness last_trade_price c 38,371 34,905 6ms 17ms 137ms 1.7s 0 transport_latency_assumed last_trade_price g 8,321 not meas. 78ms 112ms 376ms 1.8s 0 transport_latency_assumed last_trade_price h 48,477 3,760 20ms 60ms 248ms 2.8s 0 transport_latency_assumed last_trade_price i 47,141 1,152 21ms 34ms 175ms 2.7s 0 transport_latency_assumed last_trade_price k 46,588 12,184 13ms 24ms 147ms 1.7s 0 transport_latency_assumed market_resolved c 3,853 3,217 29.0s 10.5min 13.3min 13.6min 0 transport_latency_assumed market_resolved g 786 not meas. 81ms 483ms 54.6s 54.8s 0 transport_latency_assumed market_resolved h 2,985 431 19ms 2.1min 6.9min 9.0min 0 transport_latency_assumed market_resolved i 2,998 384 21ms 38.3s 11.0min 11.2min 0 transport_latency_assumed market_resolved k 3,243 1,163 13ms 7.3min 18.0min 18.3min 0 transport_latency_assumed new_market c 724 334 91ms 6.4min 7.2min 7.3min 0 transport_latency_assumed new_market g 53 7 278ms 1.7min 1.8min 1.8min 0 transport_latency_assumed new_market h 541 109 141ms 53.2s 6.5min 7.1min 0 transport_latency_assumed new_market i 691 147 155ms 6.1min 6.3min 149.2d 0 transport_latency_assumed new_market k 884 455 87ms 13.1min 13.4min 13.4min 0 transport_latency_assumed price_change c 92,370,011 85,700,055 5ms 12ms 87ms 1.9s 0 transport_latency_assumed price_change g 14,346,514 484 80ms 100ms 337ms 2.0s 0 transport_latency_assumed price_change h 114,640,667 7,236,221 18ms 56ms 145ms 15.8s 0 transport_latency_assumed price_change i 114,687,506 1,976,053 20ms 28ms 101ms 4.0s 0 transport_latency_assumed price_change k 109,807,681 27,924,518 12ms 19ms 77ms 1.1s 0 transport_latency_assumed tick_size_change c 4,400 4,272 5ms 7ms 26ms 105ms 0 transport_latency_assumed tick_size_change g 1,068 not meas. 80ms 159ms 262ms 280ms 0 transport_latency_assumed tick_size_change h 5,328 448 18ms 55ms 82ms 309ms 0 transport_latency_assumed tick_size_change i 5,276 18 20ms 24ms 63ms 185ms 0 transport_latency_assumed tick_size_change k 5,228 1,010 12ms 15ms 36ms 81ms 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-27/00/2026-09-27T00.parquet sha256sum 2026-09-27T00.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.