Hour audit: 2026-10-01T13
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-01T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T13:00:00.000487374+00:00 · last event 2026-10-01T13:59:59.999870173+00:00
VOLUME 125,841,135 rows · 1,429,845,179 bytes (1.33 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 124,769,000 · h: 124,059,499 · m: 123,916,824 · k: 118,641,159 · g: 117,742,730 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 4,587,654 (3.65%) · h: 10,355,250 (8.23%) · m: 90,774,158 (72.13%) · k: 19,214,160 (15.27%) · g: 909,913 (0.72%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 14fd98f23054d6b5721a74c11852a98f9b1f9333a39a3546728e1a5658b623dd
the corpus checksum ledger names this file with the same digest
joined 125,848,380 to merged 125,841,135, minus 7,245 (minus 0.0058%)
boundary drops 7,245 · 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-01T16:11:51Z 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,654,170 130,049,163 0-40 84b99a3dbc7320d42ae35479cc0e7557f2eb21fc38a76900a2ea5fa9c398f330 book 1,589,941 102,097,974 41-47 7eccd7bd879d527342844046d35617201efe19791898b1dcd8a64e5ba35d2d4f last_trade_price 70,532 3,984,893 48-48 ccd20c27661d6919b5979260b64dc5bc40fd951953242bce6ee74e69b5a46f1d market_resolved 909 123,203 49-49 44f3115db6124a5019f1787aebeca06d488d349578c23f91998ba8b214bb1e64 new_market 2,025 190,373 50-50 c136260607bbce502fd5e0213e13c7f991ae66acd8882775755b324adb25f20c price_change 113,520,946 1,191,867,351 51-484 79d3c0e5d3f339eb67029052f164d664252b3485d2a8c6789f5613fbf837d031 tick_size_change 2,612 96,649 485-485 f65993b94273bd1297bbc220684f7cb068e0e159c5886ad582a11f5d58c8f058 EVENT MIX count share price_change 113,520,946 90.21% best_bid_ask 10,654,170 8.47% book 1,589,941 1.26% last_trade_price 70,532 0.06% tick_size_change 2,612 <0.01% new_market 2,025 <0.01% market_resolved 909 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,654,358 10,654,170 188 1,227 FULL book 1,595,531 1,589,941 5,590 138,937 FULL last_trade_price 70,532 70,532 0 192 FULL market_resolved 920 909 11 18 FULL new_market 2,025 2,025 0 0 FULL price_change 113,522,402 113,520,946 1,456 3,143 FULL tick_size_change 2,612 2,612 0 33 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,109,589 37,617 80ms 179ms 584ms 17.6s 0 transport_latency_assumed best_bid_ask h 10,649,590 872,261 21ms 104ms 551ms 54.5s 0 transport_latency_assumed best_bid_ask i 10,648,630 365,359 38ms 131ms 486ms 17.2s 0 transport_latency_assumed best_bid_ask k 10,043,409 1,518,418 17ms 123ms 473ms 7.8s 0 transport_latency_assumed best_bid_ask m 10,651,308 7,860,515 7ms 77ms 421ms 3.4s 0 transport_latency_assumed book g 916,383 356,979 41.6min 3.1d 40.0d 124.6d 0 book_staleness book h 440,674 171,657 3.1min 2.4d 40.0d 124.6d 0 book_staleness book i 703,088 292,400 20.1min 2.9d 40.0d 124.6d 0 book_staleness book k 916,988 473,665 43.0min 3.1d 40.0d 124.6d 0 book_staleness book m 494,213 295,240 6.0min 2.6d 40.0d 124.6d 0 book_staleness last_trade_price g 66,808 243 85ms 224ms 1.0s 17.6s 0 transport_latency_assumed last_trade_price h 70,475 5,580 23ms 132ms 711ms 43.8s 0 transport_latency_assumed last_trade_price i 70,483 1,810 40ms 137ms 721ms 4.9s 0 transport_latency_assumed last_trade_price k 66,143 9,582 17ms 118ms 504ms 7.4s 0 transport_latency_assumed last_trade_price m 70,509 53,317 8ms 71ms 533ms 3.3s 0 transport_latency_assumed market_resolved g 768 57 97ms 40.9s 5.4min 5.4min 0 transport_latency_assumed market_resolved h 757 60 30ms 22.5s 31.6s 55.5s 0 transport_latency_assumed market_resolved i 756 143 47ms 15.0s 49.2s 54.2s 0 transport_latency_assumed market_resolved k 812 169 28ms 54.0s 6.9min 6.9min 0 transport_latency_assumed market_resolved m 757 480 8ms 16.3s 51.0s 56.4s 0 transport_latency_assumed new_market g 1,227 167 334ms 39.8s 4.8min 4.9min 0 transport_latency_assumed new_market h 1,227 386 212ms 29.5s 41.8s 1.4min 0 transport_latency_assumed new_market i 1,227 328 164ms 29.0s 38.5s 1.2min 0 transport_latency_assumed new_market k 1,227 425 133ms 15.5s 41.2s 1.3min 0 transport_latency_assumed new_market m 1,227 719 81ms 20.9s 40.9s 1.6min 0 transport_latency_assumed price_change g 106,645,403 514,838 81ms 196ms 710ms 17.6s 0 transport_latency_assumed price_change h 112,894,168 9,305,052 21ms 121ms 648ms 54.7s 0 transport_latency_assumed price_change i 113,342,208 3,927,460 39ms 145ms 561ms 17.2s 0 transport_latency_assumed price_change k 107,610,036 17,211,508 17ms 125ms 507ms 7.9s 0 transport_latency_assumed price_change m 112,696,198 82,562,088 7ms 87ms 477ms 3.4s 0 transport_latency_assumed tick_size_change g 2,552 12 81ms 295ms 655ms 713ms 0 transport_latency_assumed tick_size_change h 2,608 254 21ms 127ms 531ms 5.3s 0 transport_latency_assumed tick_size_change i 2,608 154 33ms 179ms 546ms 2.7s 0 transport_latency_assumed tick_size_change k 2,544 393 17ms 183ms 478ms 709ms 0 transport_latency_assumed tick_size_change m 2,612 1,799 7ms 164ms 476ms 747ms 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/13/2026-10-01T13.parquet sha256sum 2026-10-01T13.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.