Hour audit: 2026-10-01T11
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-10-01T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T11:00:00.000041865+00:00 · last event 2026-10-01T11:59:59.999923385+00:00
VOLUME 106,383,104 rows · 1,175,932,518 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 106,232,643 · i: 106,041,363 · h: 104,541,460 · m: 103,277,799 · g: 102,820,066 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 10,748,221 (10.10%) · i: 18,315,804 (17.22%) · h: 29,973,155 (28.17%) · m: 44,402,552 (41.74%) · g: 2,943,372 (2.77%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 be608fcddb17bc405177698eafa46fcc4f4cf61c7f166a7469852fc4d8c2544d
the corpus checksum ledger names this file with the same digest
joined 106,387,516 to merged 106,383,104, minus 4,412 (minus 0.0041%)
boundary drops 4,412 · 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-10-01T14:08:02Z 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,150,415 115,339,560 0-34 5f26be7c9ce3f4aa07931fb2714d44ab8c293425becd8ed57e0762bd19886cec book 222,686 24,036,546 35-35 448e8d9772c26e8bc1d2c98fcc2563ad10dae91c3febe9e7ed2f142ff310f30e last_trade_price 52,088 3,021,748 36-36 779f816eb0f28aa61f1ffd73f4a7969dc7ec993bbeef4aa7a4dc2e90b541b6b2 market_resolved 888 134,797 37-37 240efab52cae016168eac1014ae1447d5e9d7542dd56a426f918b5fa7be37382 new_market 1,049 108,757 38-38 b03690e7131ec9b1108880bb0876237f8bc6a4b06a3645ac23a5ebaaed2c0056 price_change 96,953,414 1,031,982,504 39-408 a4c89d8f70c54d39d1a76599380f756b7b4a68b6ad41191f8e8a4525854d7ec1 tick_size_change 2,564 97,138 409-409 dcb4b2f1b94fa4ec12154cd62f389e8cdfb31a6704f59d400f3585a992b88166 EVENT MIX count share price_change 96,953,414 91.14% best_bid_ask 9,150,415 8.60% book 222,686 0.21% last_trade_price 52,088 0.05% tick_size_change 2,564 <0.01% new_market 1,049 <0.01% market_resolved 888 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,150,897 9,150,415 482 131 FULL book 222,700 222,686 14 53,567 FULL last_trade_price 52,088 52,088 0 0 FULL market_resolved 888 888 0 1 FULL new_market 1,049 1,049 0 0 FULL price_change 96,957,330 96,953,414 3,916 13,759 FULL tick_size_change 2,564 2,564 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,147,690 263,059 137ms 301ms 654ms 35.8s 0 transport_latency_assumed best_bid_ask h 9,149,685 2,552,983 64ms 223ms 557ms 45.1s 0 transport_latency_assumed best_bid_ask i 9,149,200 1,626,153 88ms 245ms 567ms 7.9s 0 transport_latency_assumed best_bid_ask k 9,149,166 893,719 98ms 264ms 591ms 3.2s 0 transport_latency_assumed best_bid_ask m 9,147,510 3,814,501 60ms 211ms 533ms 7.7s 0 transport_latency_assumed book g 149,294 44,503 243ms 9.7h 24.0d 124.6d 0 book_staleness book h 110,051 37,850 51ms 392ms 19.1h 106.0d 0 book_staleness book i 133,590 41,351 158ms 3.5h 22.7d 106.0d 0 book_staleness book k 129,449 31,700 150ms 2.0h 21.1d 106.5d 0 book_staleness book m 127,700 67,282 82ms 25.9min 4.3d 124.5d 0 book_staleness last_trade_price g 51,647 889 158ms 436ms 1.2s 35.8s 0 transport_latency_assumed last_trade_price h 52,012 17,417 35ms 273ms 717ms 25.1s 0 transport_latency_assumed last_trade_price i 52,054 6,711 112ms 357ms 890ms 8.0s 0 transport_latency_assumed last_trade_price k 52,036 4,686 112ms 351ms 829ms 3.2s 0 transport_latency_assumed last_trade_price m 51,905 22,385 51ms 274ms 826ms 7.7s 0 transport_latency_assumed market_resolved g 821 36 174ms 466ms 47.9s 48.8s 0 transport_latency_assumed market_resolved h 821 226 82ms 357ms 40.3s 40.4s 0 transport_latency_assumed market_resolved i 820 163 134ms 27.6s 56.1s 57.4s 0 transport_latency_assumed market_resolved k 821 91 117ms 363ms 57.4s 57.7s 0 transport_latency_assumed market_resolved m 821 372 79ms 27.6s 56.7s 57.7s 0 transport_latency_assumed new_market g 705 95 460ms 17.3s 55.2s 1.7min 0 transport_latency_assumed new_market h 705 244 125ms 20.2s 25.3s 1.8min 0 transport_latency_assumed new_market i 705 133 132ms 16.7s 52.2s 1.5min 0 transport_latency_assumed new_market k 705 57 323ms 21.8s 26.3s 1.8min 0 transport_latency_assumed new_market m 705 520 57ms 17.0s 55.2s 1.8min 0 transport_latency_assumed price_change g 93,467,345 2,634,694 142ms 326ms 733ms 35.8s 0 transport_latency_assumed price_change h 95,225,622 27,363,910 62ms 233ms 587ms 45.3s 0 transport_latency_assumed price_change i 96,702,430 16,640,810 93ms 266ms 621ms 8.4s 0 transport_latency_assumed price_change k 96,897,902 9,817,704 100ms 278ms 626ms 3.3s 0 transport_latency_assumed price_change m 93,946,594 40,496,296 59ms 221ms 565ms 7.7s 0 transport_latency_assumed tick_size_change g 2,564 96 152ms 260ms 978ms 1.9s 0 transport_latency_assumed tick_size_change h 2,564 525 88ms 199ms 783ms 5.3s 0 transport_latency_assumed tick_size_change i 2,564 483 101ms 211ms 537ms 666ms 0 transport_latency_assumed tick_size_change k 2,564 264 103ms 206ms 535ms 986ms 0 transport_latency_assumed tick_size_change m 2,564 1,196 67ms 141ms 339ms 825ms 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-10-01/11/2026-10-01T11.parquet sha256sum 2026-10-01T11.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.