Hour audit: 2026-09-28T08
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-28T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T08:00:00.000057335+00:00 · last event 2026-09-28T08:59:59.999978359+00:00
VOLUME 105,792,223 rows · 1,119,849,896 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 105,692,311 · h: 105,541,337 · g: 105,088,774 · i: 103,437,686 · c: 103,415,522 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 5,901,169 (5.58%) · h: 862,726 (0.82%) · g: 34,881 (0.03%) · i: 8,713,605 (8.24%) · c: 90,279,842 (85.34%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 9784977a917aa3779317e4211bd5342a421035c3fe8f68343090d238f8ac989f
the corpus checksum ledger names this file with the same digest
joined 105,794,495 to merged 105,792,223, minus 2,272 (minus 0.0021%)
boundary drops 2,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-28T10:39:00Z 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,818,342 113,900,775 0-37 641e2a6634baea710de8298300d7005ac074419b2f9075ffc1c2b10e7958722f book 150,561 15,387,052 38-38 7bc398a93de6c6eff343ce3195457386af2627209ff6b9bff87942e2ff84cc06 last_trade_price 49,788 2,892,401 39-39 c39e7c58fa3c1e2a28dd5fbbe5ff579a0a91f70feffaa3cdb902138f73079b92 market_resolved 766 114,316 40-40 bccf6052fb01b951966a422ead9cbbf3574c14f20e4de2dee4b1805ecc34f32d new_market 1,900 174,518 41-41 9fcb3ddd940cc7c9730b8d24b5cf766b597cad4b43613f4faaba21d66f9b0b82 price_change 95,768,350 986,079,317 42-407 23d6cb5ece0c7d945c6184b90f237bf132606b43e1526472c1f95fc6cdeb5b5c tick_size_change 2,516 94,503 408-408 9f31a7e546d8dbee6a1c44141df29741943027c1f6e91f6fdad8786e1dd0f95d EVENT MIX count share price_change 95,768,350 90.52% best_bid_ask 9,818,342 9.28% book 150,561 0.14% last_trade_price 49,788 0.05% tick_size_change 2,516 <0.01% new_market 1,900 <0.01% market_resolved 766 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,818,536 9,818,342 194 2,287 FULL book 150,565 150,561 4 14,938 FULL last_trade_price 49,790 49,788 2 154 FULL market_resolved 766 766 0 13 FULL new_market 1,900 1,900 0 0 FULL price_change 95,770,422 95,768,350 2,072 4,351 FULL tick_size_change 2,516 2,516 0 39 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,613,572 8,429,011 5ms 14ms 174ms 13.9s 0 transport_latency_assumed best_bid_ask g 9,808,033 1,970 78ms 104ms 685ms 39.7s 0 transport_latency_assumed best_bid_ask h 9,812,961 69,706 19ms 35ms 374ms 2.3min 0 transport_latency_assumed best_bid_ask i 9,576,075 819,255 16ms 24ms 129ms 10.3s 0 transport_latency_assumed best_bid_ask k 9,816,603 498,400 12ms 22ms 133ms 51.6s 0 transport_latency_assumed book c 109,040 94,342 8ms 1.5s 5.6d 102.9d 0 book_staleness book g 108,601 9,777 89ms 11.6s 6.5d 102.9d 0 book_staleness book h 121,735 22,016 28ms 2.5h 9.7d 102.9d 0 book_staleness book i 103,834 9,866 21ms 277ms 14.2h 102.9d 0 book_staleness book k 110,062 14,560 16ms 277ms 3.5d 102.9d 0 book_staleness last_trade_price c 48,463 42,436 7ms 22ms 292ms 11.7s 0 transport_latency_assumed last_trade_price g 48,056 18 86ms 1.5s 12.0s 36.4s 0 transport_latency_assumed last_trade_price h 49,445 431 21ms 124ms 1.1s 38.6s 0 transport_latency_assumed last_trade_price i 49,181 3,335 20ms 151ms 2.7s 10.3s 0 transport_latency_assumed last_trade_price k 49,638 3,568 14ms 43ms 278ms 10.4s 0 transport_latency_assumed market_resolved c 689 564 6ms 13.9s 1.4min 2.5min 0 transport_latency_assumed market_resolved g 694 42 79ms 225ms 732ms 37.1s 0 transport_latency_assumed market_resolved h 694 22 21ms 131ms 52.7s 56.4s 0 transport_latency_assumed market_resolved i 688 120 21ms 275ms 49.0s 2.4min 0 transport_latency_assumed market_resolved k 694 18 14ms 126ms 53.6s 57.3s 0 transport_latency_assumed new_market c 1,100 470 199ms 36.7s 1.1min 1.5min 0 transport_latency_assumed new_market g 1,100 180 388ms 40.1s 1.1min 1.6min 0 transport_latency_assumed new_market h 1,100 318 265ms 38.1s 1.0min 1.6min 0 transport_latency_assumed new_market i 1,100 525 150ms 39.0s 1.0min 1.1min 0 transport_latency_assumed new_market k 1,100 407 240ms 41.5s 1.1min 1.4min 0 transport_latency_assumed price_change c 93,640,194 81,710,988 6ms 17ms 200ms 13.9s 0 transport_latency_assumed price_change g 95,119,774 22,890 78ms 176ms 5.4s 39.8s 0 transport_latency_assumed price_change h 95,552,890 770,232 19ms 46ms 533ms 2.3min 0 transport_latency_assumed price_change i 93,704,392 7,880,149 17ms 33ms 358ms 10.4s 0 transport_latency_assumed price_change k 95,711,698 5,384,091 13ms 26ms 170ms 54.8s 0 transport_latency_assumed tick_size_change c 2,464 2,031 6ms 21ms 118ms 298ms 0 transport_latency_assumed tick_size_change g 2,516 4 78ms 99ms 847ms 3.0s 0 transport_latency_assumed tick_size_change h 2,512 1 19ms 33ms 231ms 2.8s 0 transport_latency_assumed tick_size_change i 2,416 355 16ms 25ms 104ms 753ms 0 transport_latency_assumed tick_size_change k 2,516 125 13ms 21ms 163ms 1.0s 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/08/2026-09-28T08.parquet sha256sum 2026-09-28T08.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.