Hour audit: 2026-09-30T06
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-30T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T06:00:00.002877520+00:00 · last event 2026-09-30T06:59:59.999982663+00:00
VOLUME 101,713,596 rows · 1,030,854,992 bytes (983.10 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 101,578,239 · m: 101,467,851 · h: 101,348,040 · g: 101,214,046 · i: 101,160,169 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 3,411,330 (3.35%) · m: 96,859,440 (95.23%) · h: 880,750 (0.87%) · g: 28,363 (0.03%) · i: 533,713 (0.52%) (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 101,713,596 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 190cf941d0a88acb1e497fade93155f7e0f42e1968230d3f0104060c0e2e67d7
the corpus checksum ledger names this file with the same digest
joined 101,715,148 to merged 101,713,596, minus 1,552 (minus 0.0015%)
boundary drops 1,552 · 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-30T16:24:27Z as ghikm
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,539,744 109,157,547 0-36 63f7bcade0bb1d6e642cf65c1c664092b0af1293e2a20d9934ac1f5bca9ba50e book 161,184 16,047,080 37-37 b98a99df61bfeead02fb8cc468d493409588d731ec5b063819a1362f06ec8b1d last_trade_price 50,473 2,881,102 38-38 2aa6f8f2e975fd0e89e4c6983dac29069b7d479bd6358a8efb88d39415e96841 market_resolved 732 114,922 39-39 e92f097dfc3ad748405ae6aea13ea609983b3d6b4512a5468ad5344b2a149725 new_market 687 77,397 40-40 cfac052226437ed078a15630a4f3d1af694a465d096a726304b0e339fa972dd0 price_change 91,958,312 901,324,351 41-391 4be7125af4d12ab6670897a419181060840e8e2f47b8f81cfa67888a3bff0b39 tick_size_change 2,464 91,487 392-392 eabe8525989bc48dcd5ed873feaf117cca02c9b06290da4fc57852178c048bc5 EVENT MIX count share price_change 91,958,312 90.41% best_bid_ask 9,539,744 9.38% book 161,184 0.16% last_trade_price 50,473 0.05% tick_size_change 2,464 <0.01% market_resolved 732 <0.01% new_market 687 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,539,865 9,539,744 121 118 FULL book 161,200 161,184 16 16,086 FULL last_trade_price 50,474 50,473 1 0 FULL market_resolved 732 732 0 0 FULL new_market 687 687 0 0 FULL price_change 91,959,726 91,958,312 1,414 72 FULL tick_size_change 2,464 2,464 0 9 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,532,489 480 77ms 101ms 363ms 28.8s 0 transport_latency_assumed best_bid_ask h 9,531,443 69,006 18ms 27ms 137ms 1.0min 0 transport_latency_assumed best_bid_ask i 9,523,301 33,569 22ms 31ms 120ms 4.6s 0 transport_latency_assumed best_bid_ask k 9,537,808 289,245 13ms 23ms 115ms 11.1s 0 transport_latency_assumed best_bid_ask m 9,532,463 9,147,444 4ms 9ms 60ms 6.3s 0 transport_latency_assumed book g 119,456 20,674 89ms 1.1h 10.7d 123.3d 0 book_staleness book h 110,540 11,252 23ms 354ms 1.4d 104.9d 0 book_staleness book i 108,532 9,718 28ms 130ms 1.1d 104.7d 0 book_staleness book k 113,459 14,481 17ms 5.8s 3.1d 104.8d 0 book_staleness book m 111,262 105,059 6ms 107ms 23.6h 52.7d 0 book_staleness last_trade_price g 48,734 15 83ms 512ms 7.6s 28.9s 0 transport_latency_assumed last_trade_price h 49,761 613 20ms 71ms 398ms 51.1s 0 transport_latency_assumed last_trade_price i 49,476 618 24ms 54ms 222ms 2.0s 0 transport_latency_assumed last_trade_price k 50,244 2,159 14ms 46ms 231ms 7.7s 0 transport_latency_assumed last_trade_price m 50,107 47,068 5ms 14ms 132ms 3.3s 0 transport_latency_assumed market_resolved g 704 not meas. 84ms 34.9s 45.1s 45.3s 0 transport_latency_assumed market_resolved h 704 1 21ms 37.3s 46.3s 47.0s 0 transport_latency_assumed market_resolved i 704 29 25ms 14.5s 42.8s 43.6s 0 transport_latency_assumed market_resolved k 704 14 17ms 35.8s 44.7s 45.8s 0 transport_latency_assumed market_resolved m 704 688 5ms 34.3s 43.5s 43.9s 0 transport_latency_assumed new_market g 502 36 230ms 9.3s 30.9s 1.5min 0 transport_latency_assumed new_market h 502 118 92ms 16.4s 1.0min 1.8min 0 transport_latency_assumed new_market i 502 48 96ms 13.5s 56.4s 1.5min 0 transport_latency_assumed new_market k 502 107 125ms 13.7s 32.9s 1.7min 0 transport_latency_assumed new_market m 502 378 49ms 15.6s 52.3s 59.6s 0 transport_latency_assumed price_change g 91,509,697 7,158 77ms 137ms 1.8s 28.9s 0 transport_latency_assumed price_change h 91,652,626 799,725 18ms 34ms 212ms 1.0min 0 transport_latency_assumed price_change i 91,475,190 489,731 23ms 35ms 150ms 6.2s 0 transport_latency_assumed price_change k 91,873,058 3,105,241 13ms 27ms 148ms 34.3s 0 transport_latency_assumed price_change m 91,770,385 87,556,457 4ms 10ms 81ms 7.2s 0 transport_latency_assumed tick_size_change g 2,464 not meas. 77ms 98ms 480ms 3.6s 0 transport_latency_assumed tick_size_change h 2,464 35 18ms 36ms 99ms 794ms 0 transport_latency_assumed tick_size_change i 2,464 not meas. 23ms 36ms 109ms 1.0s 0 transport_latency_assumed tick_size_change k 2,464 83 13ms 33ms 125ms 339ms 0 transport_latency_assumed tick_size_change m 2,428 2,346 4ms 8ms 30ms 41ms 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-30/06/2026-09-30T06.parquet sha256sum 2026-09-30T06.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.