Hour audit: 2026-09-30T16
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-30T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T16:00:00.000387559+00:00 · last event 2026-09-30T16:59:59.999995148+00:00
VOLUME 113,148,007 rows · 1,226,252,084 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 112,920,295 · k: 112,863,913 · m: 112,826,038 · g: 112,799,265 · i: 112,755,038 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,025,037 (3.56%) · k: 17,000,203 (15.02%) · m: 91,491,600 (80.86%) · g: 98,025 (0.09%) · i: 533,142 (0.47%) (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 113,148,007 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ff297034489a6faaa4adccce7acc8f4fc7013867c1a93d561bbb5d7204654b78
the corpus checksum ledger names this file with the same digest
joined 113,149,952 to merged 113,148,007, minus 1,945 (minus 0.0017%)
boundary drops 1,945 · 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-30T22:05:57Z 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 10,244,806 120,952,986 0-39 eb498935584e601c168056424acd212d9b5065ba66e073351d539c9c3dc170c3 book 465,333 47,411,122 40-41 1ae4a90b0c42faa3776a41f32fec01800f904f9ee77d5ff353ec3686b125e23f last_trade_price 59,503 3,481,269 42-42 9dba33df1a00d733c467931c42132d94cfc5a029f4bacc6c844411675e554c94 market_resolved 1,167 178,647 43-43 46a80519a6a30035632c31997c0669d5abf463b443fb51bd28adb853eed5b392 new_market 1,440 149,279 44-44 273d463dc53990c6f8c9440b5338ae307e94e9bcdc77f3f790173020fdc9afe9 price_change 102,372,402 1,052,663,571 45-435 03c8bb5a633ff6473510cc756ba90edd66d16fcd4811d1454875c6bbef558e63 tick_size_change 3,356 123,980 436-436 563d06790a227f27100a89ab6fe2e1884fec2ca007cee6aa6e9bcf4ca60fa07a EVENT MIX count share price_change 102,372,402 90.48% best_bid_ask 10,244,806 9.05% book 465,333 0.41% last_trade_price 59,503 0.05% tick_size_change 3,356 <0.01% new_market 1,440 <0.01% market_resolved 1,167 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,244,987 10,244,806 181 139 FULL book 465,595 465,333 262 144,640 FULL last_trade_price 59,503 59,503 0 1 FULL market_resolved 1,167 1,167 0 0 FULL new_market 1,440 1,440 0 0 FULL price_change 102,373,904 102,372,402 1,502 76 FULL tick_size_change 3,356 3,356 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,241,438 2,717 79ms 103ms 347ms 16.6s 0 transport_latency_assumed best_bid_ask h 10,242,554 316,874 20ms 46ms 229ms 53.9s 0 transport_latency_assumed best_bid_ask i 10,243,586 43,073 32ms 63ms 160ms 43.2s 0 transport_latency_assumed best_bid_ask k 10,243,673 1,445,893 14ms 34ms 136ms 57.0s 0 transport_latency_assumed best_bid_ask m 10,241,196 8,436,249 5ms 23ms 97ms 4.5s 0 transport_latency_assumed book g 202,688 67,164 202ms 20.4h 27.9d 123.8d 0 book_staleness book h 266,650 125,810 16.9s 1.4d 39.1d 123.7d 0 book_staleness book i 123,272 3,228 36ms 105ms 2.2h 105.3d 0 book_staleness book k 193,442 74,278 31ms 16.9h 25.1d 105.3d 0 book_staleness book m 238,340 194,853 220ms 1.3d 35.9d 123.7d 0 book_staleness last_trade_price g 59,073 47 85ms 311ms 5.4s 9.5s 0 transport_latency_assumed last_trade_price h 59,473 2,717 21ms 59ms 390ms 14.3s 0 transport_latency_assumed last_trade_price i 59,439 322 36ms 86ms 511ms 2.5s 0 transport_latency_assumed last_trade_price k 59,482 8,638 15ms 43ms 165ms 3.6s 0 transport_latency_assumed last_trade_price m 59,242 47,779 6ms 28ms 145ms 4.4s 0 transport_latency_assumed market_resolved g 1,106 1 82ms 410ms 49.1s 50.4s 0 transport_latency_assumed market_resolved h 1,106 26 21ms 22.1s 53.3s 58.3s 0 transport_latency_assumed market_resolved i 1,106 5 36ms 23.9s 52.3s 57.1s 0 transport_latency_assumed market_resolved k 1,106 142 16ms 127ms 52.4s 53.2s 0 transport_latency_assumed market_resolved m 1,106 993 6ms 21.9s 54.0s 56.1s 0 transport_latency_assumed new_market g 942 160 522ms 31.5s 32.9d 152.9d 0 transport_latency_assumed new_market h 942 160 219ms 20.4s 32.8d 152.9d 0 transport_latency_assumed new_market i 942 154 169ms 25.9s 32.9d 152.9d 0 transport_latency_assumed new_market k 942 447 127ms 16.6s 32.9d 152.9d 0 transport_latency_assumed new_market m 942 519 89ms 20.9s 32.9d 152.9d 0 transport_latency_assumed price_change g 102,290,662 27,936 79ms 119ms 990ms 16.6s 0 transport_latency_assumed price_change h 102,346,214 3,579,334 20ms 49ms 261ms 53.9s 0 transport_latency_assumed price_change i 102,323,337 486,344 32ms 67ms 224ms 50.0s 0 transport_latency_assumed price_change k 102,361,912 15,470,418 14ms 35ms 136ms 1.0min 0 transport_latency_assumed price_change m 102,281,856 82,808,370 5ms 25ms 107ms 4.6s 0 transport_latency_assumed tick_size_change g 3,356 not meas. 79ms 98ms 200ms 617ms 0 transport_latency_assumed tick_size_change h 3,356 116 20ms 45ms 188ms 2.9s 0 transport_latency_assumed tick_size_change i 3,356 16 32ms 62ms 125ms 227ms 0 transport_latency_assumed tick_size_change k 3,356 387 14ms 35ms 127ms 255ms 0 transport_latency_assumed tick_size_change m 3,356 2,837 5ms 21ms 84ms 115ms 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/16/2026-09-30T16.parquet sha256sum 2026-09-30T16.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.