Hour audit: 2026-10-03T14
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-03T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T14:00:00.000002775+00:00 · last event 2026-10-03T14:59:59.999931673+00:00
VOLUME 127,534,937 rows · 1,418,288,173 bytes (1.32 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 126,498,349 · h: 126,473,993 · m: 126,455,483 · i: 126,161,941 · g: 115,044,327 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 5,935,692 (4.65%) · h: 1,620,136 (1.27%) · m: 118,116,805 (92.62%) · i: 875,134 (0.69%) · g: 987,170 (0.77%) (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 127,534,937 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cee6952b1b27cf8912f809a17181e09e782db174150fb631c16d23d415dc1749
the corpus checksum ledger names this file with the same digest
joined 127,544,214 to merged 127,534,937, minus 9,277 (minus 0.0073%)
boundary drops 9,277 · 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-03T16:50:42Z 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 11,263,668 138,891,135 0-42 59be61c77619a57673f7a846f734bef4d47f5ded16da25d80ef3e6ef83d60bd3 book 1,119,113 78,056,586 43-47 d603e16fe786895c199e22343f26d0c9b2a78797780e7df70b183e11d088195f last_trade_price 59,405 3,499,680 48-48 888c78fb99e8c1fe1b107d06317540d4f226cab91376003cb4b49124e51b4513 market_resolved 733 103,746 49-49 a8d6f76baa5b40c540c829e2da3d1d281ca3ddbb3d49a07cc2ea327727e19dbf new_market 3,358 333,235 50-50 e3cfe54b591b74c15546261a08cd4cc4cdcbbc9e39d43d66226b74b86da5264b price_change 115,076,564 1,195,513,157 51-489 c3d128243710cb063cd9d8f8219dd1624369a5a8be73f5f045adc50ca3270304 tick_size_change 12,096 440,212 490-490 bae32a9a977419c4d572e7a49d6c2136d5cc73a75e428177f85f49f10ce2a581 EVENT MIX count share price_change 115,076,564 90.23% best_bid_ask 11,263,668 8.83% book 1,119,113 0.88% last_trade_price 59,405 0.05% tick_size_change 12,096 <0.01% new_market 3,358 <0.01% market_resolved 733 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,264,524 11,263,668 856 1,559 FULL book 1,119,391 1,119,113 278 234,807 FULL last_trade_price 59,410 59,405 5 268 FULL market_resolved 733 733 0 1 FULL new_market 3,358 3,358 0 9 FULL price_change 115,084,702 115,076,564 8,138 1,369 FULL tick_size_change 12,096 12,096 0 416 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,215,303 1,396 79ms 104ms 682ms 31.0s 0 transport_latency_assumed best_bid_ask h 11,263,062 134,499 18ms 30ms 590ms 1.9min 0 transport_latency_assumed best_bid_ask i 11,253,383 71,157 21ms 31ms 299ms 50.2s 0 transport_latency_assumed best_bid_ask k 11,262,090 502,851 14ms 28ms 345ms 1.5min 0 transport_latency_assumed best_bid_ask m 11,262,938 10,553,765 5ms 13ms 121ms 7.4s 0 transport_latency_assumed book g 1,086,587 967,197 13.9min 1.6d 42.0d 126.7d 0 book_staleness book h 126,928 4,505 24ms 229ms 7.0h 108.2d 0 book_staleness book i 141,819 14,836 25ms 2.2min 3.0d 108.2d 0 book_staleness book k 140,431 18,698 20ms 1.2min 7.0d 108.2d 0 book_staleness book m 128,966 113,877 8ms 87ms 12.4h 52.6d 0 book_staleness last_trade_price g 53,106 28 83ms 356ms 12.3s 30.8s 0 transport_latency_assumed last_trade_price h 59,322 929 20ms 58ms 1.4s 1.2min 0 transport_latency_assumed last_trade_price i 58,450 521 23ms 60ms 1.6s 14.5s 0 transport_latency_assumed last_trade_price k 59,324 3,956 15ms 42ms 540ms 1.1min 0 transport_latency_assumed last_trade_price m 59,359 53,971 6ms 19ms 201ms 2.4s 0 transport_latency_assumed market_resolved g 628 99 91ms 3.9min 5.4min 6.4min 0 transport_latency_assumed market_resolved h 627 21 21ms 648ms 46.1s 50.7s 0 transport_latency_assumed market_resolved i 627 63 22ms 10.2s 47.3s 52.8s 0 transport_latency_assumed market_resolved k 627 20 16ms 9.5s 50.9s 56.1s 0 transport_latency_assumed market_resolved m 627 530 6ms 7.9s 48.1s 53.6s 0 transport_latency_assumed new_market g 2,573 780 23.2s 5.7min 5.9min 352.7d 0 transport_latency_assumed new_market h 2,163 565 19.6s 36.5s 56.5s 352.7d 0 transport_latency_assumed new_market i 2,172 303 19.1s 40.4s 1.0min 352.7d 0 transport_latency_assumed new_market k 2,172 588 18.4s 38.5s 58.3s 352.7d 0 transport_latency_assumed new_market m 2,172 1,122 21.9s 37.1s 58.9s 352.7d 0 transport_latency_assumed price_change g 103,675,698 17,670 80ms 130ms 1.1s 31.6s 0 transport_latency_assumed price_change h 115,009,795 1,479,386 19ms 34ms 741ms 1.9min 0 transport_latency_assumed price_change i 114,693,422 788,084 21ms 35ms 413ms 50.5s 0 transport_latency_assumed price_change k 115,021,609 5,408,792 14ms 31ms 378ms 1.9min 0 transport_latency_assumed price_change m 114,989,325 107,382,632 5ms 14ms 136ms 7.6s 0 transport_latency_assumed tick_size_change g 10,432 not meas. 79ms 108ms 437ms 1.1s 0 transport_latency_assumed tick_size_change h 12,096 231 19ms 37ms 611ms 41.8s 0 transport_latency_assumed tick_size_change i 12,068 170 21ms 34ms 227ms 25.1s 0 transport_latency_assumed tick_size_change k 12,096 787 14ms 33ms 248ms 49.5s 0 transport_latency_assumed tick_size_change m 12,096 10,908 5ms 18ms 145ms 1.8s 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-03/14/2026-10-03T14.parquet sha256sum 2026-10-03T14.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.