Hour audit: 2026-10-03T22
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-03T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T22:00:00.000011316+00:00 · last event 2026-10-03T22:59:59.999959660+00:00
VOLUME 144,511,558 rows · 1,680,896,422 bytes (1.57 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 141,012,735 · h: 140,994,546 · g: 123,124,592 · i: 122,311,127 · k: 103,803,001 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 128,703,181 (89.06%) · h: 3,743,223 (2.59%) · g: 851,312 (0.59%) · i: 2,290,634 (1.59%) · k: 8,923,208 (6.17%) (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 144,511,558 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4c6bc2548cc999e228d09c85bc765b9f1e5ca14e6024fdfea9bbccbdb4ddf392
the corpus checksum ledger names this file with the same digest
joined 144,525,332 to merged 144,511,558, minus 13,774 (minus 0.0095%)
boundary drops 13,774 · 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-04T00:52:36Z 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 12,532,785 153,052,640 0-47 a407188e943e2fdd03dcd92476e5aa7a4470811dd3c30117b011ac03bccb9d07 book 3,755,347 137,124,463 48-62 3ef54b82305f20b2d37cf9336938eb59d00abc9f670282cbbf74f486f97a250a last_trade_price 66,930 3,846,461 63-63 42b2ee4756908f64721e2aee98fb53b71001629a2397fcb94802f33c864fe86f market_resolved 8,442 788,619 64-64 d262f6a33117da44cd5e14693920fcc2c03fa4c452a8ec5ef2a7d6c272c6a808 new_market 7,528 596,472 65-65 650c93eda6a120750553539de410857c8c69e1d91db3f6726d270cc122aa4a1d price_change 128,131,958 1,383,527,982 66-554 8770781aac8dfd3570930f8353824c85c17180e172aa53adc83f83451a33ea67 tick_size_change 8,568 317,723 555-555 80ebecb01ff0e4d190952ae746a7d1711493a6065c1339d4efb44adf026fd2f5 EVENT MIX count share price_change 128,131,958 88.67% best_bid_ask 12,532,785 8.67% book 3,755,347 2.60% last_trade_price 66,930 0.05% tick_size_change 8,568 <0.01% market_resolved 8,442 <0.01% new_market 7,528 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,533,036 12,532,785 251 11,318 FULL book 3,766,284 3,755,347 10,937 193,521 FULL last_trade_price 66,931 66,930 1 966 FULL market_resolved 8,442 8,442 0 1,018 FULL new_market 7,529 7,528 1 83 FULL price_change 128,134,542 128,131,958 2,584 10,226 FULL tick_size_change 8,568 8,568 0 746 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,886,630 3,017 83ms 171ms 1.5s 48.1s 0 transport_latency_assumed best_bid_ask h 12,525,294 309,859 20ms 41ms 995ms 1.1min 0 transport_latency_assumed best_bid_ask i 10,729,228 135,250 23ms 41ms 354ms 59.1s 0 transport_latency_assumed best_bid_ask k 9,008,333 605,855 14ms 33ms 262ms 52.3s 0 transport_latency_assumed best_bid_ask m 12,529,562 11,478,804 5ms 18ms 172ms 8.4s 0 transport_latency_assumed book g 1,643,948 817,104 20.3min 1.9d 42.4d 127.0d 0 book_staleness book h 353,453 99,390 47.4s 1.0d 42.3d 127.0d 0 book_staleness book i 1,565,510 671,963 20.2min 1.9d 42.4d 127.0d 0 book_staleness book k 2,933,764 1,957,835 28.4min 2.1d 44.2d 127.0d 0 book_staleness book m 349,341 209,055 45.0s 1.0d 42.3d 127.0d 0 book_staleness last_trade_price g 57,168 11 91ms 1.4s 13.9s 48.4s 0 transport_latency_assumed last_trade_price h 66,638 2,297 22ms 91ms 1.5s 49.6s 0 transport_latency_assumed last_trade_price i 55,758 1,105 25ms 91ms 2.2s 11.2s 0 transport_latency_assumed last_trade_price k 44,371 3,748 15ms 53ms 407ms 5.8s 0 transport_latency_assumed last_trade_price m 66,728 59,769 7ms 27ms 244ms 7.2s 0 transport_latency_assumed market_resolved g 4,562 1,197 99ms 7.2min 12.4min 12.9min 0 transport_latency_assumed market_resolved h 3,989 91 22ms 20.4s 51.0s 56.8s 0 transport_latency_assumed market_resolved i 4,596 930 30ms 8.2min 11.8min 12.1min 0 transport_latency_assumed market_resolved k 5,885 2,461 51.8s 14.6min 19.0min 19.4min 0 transport_latency_assumed market_resolved m 3,990 3,763 6ms 18.6s 49.9s 1.0min 0 transport_latency_assumed new_market g 3,901 761 415ms 43.0s 8.0min 8.1min 0 transport_latency_assumed new_market h 3,682 1,134 312ms 37.4s 46.6s 1.7min 0 transport_latency_assumed new_market i 4,178 1,593 255ms 4.8min 8.5min 8.8min 0 transport_latency_assumed new_market k 4,562 1,833 172ms 7.1min 13.9min 14.4min 0 transport_latency_assumed new_market m 3,682 2,207 124ms 37.8s 43.0s 1.8min 0 transport_latency_assumed price_change g 110,520,563 29,222 84ms 227ms 3.3s 48.4s 0 transport_latency_assumed price_change h 128,032,926 3,330,160 20ms 48ms 1.2s 1.1min 0 transport_latency_assumed price_change i 109,944,045 1,479,624 23ms 47ms 441ms 59.5s 0 transport_latency_assumed price_change k 91,799,666 6,350,992 14ms 36ms 287ms 52.4s 0 transport_latency_assumed price_change m 128,050,864 116,941,960 5ms 20ms 182ms 9.3s 0 transport_latency_assumed tick_size_change g 7,820 not meas. 83ms 127ms 1.1s 14.6s 0 transport_latency_assumed tick_size_change h 8,564 292 20ms 42ms 463ms 24.1s 0 transport_latency_assumed tick_size_change i 7,812 169 23ms 42ms 228ms 2.6s 0 transport_latency_assumed tick_size_change k 6,420 484 14ms 26ms 85ms 368ms 0 transport_latency_assumed tick_size_change m 8,568 7,623 5ms 22ms 180ms 1.9s 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/22/2026-10-03T22.parquet sha256sum 2026-10-03T22.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.