Hour audit: 2026-10-01T08
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-01T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T08:00:00.000153134+00:00 · last event 2026-10-01T08:59:59.999991616+00:00
VOLUME 105,714,617 rows · 1,146,372,177 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 105,366,179 · i: 105,056,182 · h: 100,398,127 · m: 98,168,733 · g: 94,864,531 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 29,106,888 (27.53%) · i: 3,467,942 (3.28%) · h: 12,502,250 (11.83%) · m: 60,426,901 (57.16%) · g: 210,636 (0.20%) (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 105,714,617 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 15ea96036a3b5995c67e94a06aa2565b02f330a7c09caf14fe7a7ca947425994
the corpus checksum ledger names this file with the same digest
joined 105,716,426 to merged 105,714,617, minus 1,809 (minus 0.0017%)
boundary drops 1,809 · 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-01T11:06:50Z 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,890,676 129,833,464 0-41 f180059d769b80a1753f7c65a6c3cf8e2964207db2c0a0abfbcf9f3306fb3ea8 book 523,126 50,812,158 42-43 89d92bc0262f8f58144adb6aa90304747c38c4d501297f14fb539a8034669891 last_trade_price 51,223 2,922,779 44-44 179fe79a8900b1c20ffcd87028909721043bae97beb513298f07b82d7a9aad8f market_resolved 804 125,342 45-45 a5ee3693856777ef9d8a929f5b168ff821c5389f8e98f553f5bbb75a14638c7f new_market 456 48,112 46-46 9d3ee59bd8717149f799e91e89ff3f97313d0a3150705eb705b253ce6980c253 price_change 94,246,164 961,343,090 47-406 c6027bfeb1c907327bc4ca69427b19c0a2ed83ff30ae949eba7dc4920312f4a5 tick_size_change 2,168 82,117 407-407 40afd4ee6e67a2c2aef972295b2e3b010df3b3c5c0e0f1c7dfe5eb2d1bc75c60 EVENT MIX count share price_change 94,246,164 89.15% best_bid_ask 10,890,676 10.30% book 523,126 0.49% last_trade_price 51,223 0.05% tick_size_change 2,168 <0.01% market_resolved 804 <0.01% new_market 456 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,890,893 10,890,676 217 81 FULL book 523,130 523,126 4 171,802 FULL last_trade_price 51,223 51,223 0 2 FULL market_resolved 804 804 0 0 FULL new_market 456 456 0 0 FULL price_change 94,247,752 94,246,164 1,588 30,022 FULL tick_size_change 2,168 2,168 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,887,928 6,755 83ms 187ms 543ms 5.9s 0 transport_latency_assumed best_bid_ask h 10,888,846 987,917 18ms 66ms 351ms 47.2s 0 transport_latency_assumed best_bid_ask i 10,889,205 254,344 22ms 118ms 431ms 3.5s 0 transport_latency_assumed best_bid_ask k 10,889,097 2,472,762 15ms 92ms 410ms 1.0min 0 transport_latency_assumed best_bid_ask m 10,889,555 7,168,898 5ms 108ms 440ms 2.4s 0 transport_latency_assumed book g 220,725 87,190 11.2s 1.4d 39.8d 124.4d 0 book_staleness book h 239,525 108,542 38.0s 1.8d 39.8d 124.4d 0 book_staleness book i 208,072 74,134 1.2s 1.2d 36.6d 124.4d 0 book_staleness book k 227,083 113,027 20.3s 1.7d 39.8d 124.4d 0 book_staleness book m 208,595 140,233 1.2s 1.3d 25.8d 124.4d 0 book_staleness last_trade_price g 51,215 22 92ms 263ms 780ms 3.3s 0 transport_latency_assumed last_trade_price h 51,209 5,482 18ms 31ms 245ms 38.8s 0 transport_latency_assumed last_trade_price i 51,208 1,081 24ms 178ms 633ms 3.1s 0 transport_latency_assumed last_trade_price k 51,134 12,562 16ms 117ms 892ms 12.2s 0 transport_latency_assumed last_trade_price m 51,206 32,076 7ms 169ms 562ms 2.2s 0 transport_latency_assumed market_resolved g 768 9 92ms 488ms 36.2s 42.2s 0 transport_latency_assumed market_resolved h 768 101 19ms 159ms 39.1s 43.9s 0 transport_latency_assumed market_resolved i 768 5 45ms 9.9s 52.1s 56.1s 0 transport_latency_assumed market_resolved k 768 131 19ms 177ms 48.0s 53.3s 0 transport_latency_assumed market_resolved m 768 558 6ms 9.6s 55.9s 56.5s 0 transport_latency_assumed new_market g 305 40 110ms 542ms 12.1s 1.3min 0 transport_latency_assumed new_market h 305 44 50ms 14.6s 16.7s 1.2min 0 transport_latency_assumed new_market i 305 54 76ms 14.2s 1.2min 1.4min 0 transport_latency_assumed new_market k 305 85 55ms 13.9s 1.3min 1.8min 0 transport_latency_assumed new_market m 305 233 42ms 11.7s 1.4min 1.7min 0 transport_latency_assumed price_change g 83,701,422 116,620 87ms 217ms 686ms 6.2s 0 transport_latency_assumed price_change h 89,215,306 11,399,964 18ms 62ms 350ms 47.5s 0 transport_latency_assumed price_change i 93,904,456 3,138,310 22ms 138ms 504ms 5.0s 0 transport_latency_assumed price_change k 94,195,624 26,507,878 15ms 106ms 467ms 1.0min 0 transport_latency_assumed price_change m 87,016,136 53,083,392 6ms 133ms 485ms 2.4s 0 transport_latency_assumed tick_size_change g 2,168 not meas. 92ms 255ms 469ms 969ms 0 transport_latency_assumed tick_size_change h 2,168 200 18ms 71ms 297ms 747ms 0 transport_latency_assumed tick_size_change i 2,168 14 23ms 139ms 370ms 969ms 0 transport_latency_assumed tick_size_change k 2,168 443 15ms 83ms 383ms 561ms 0 transport_latency_assumed tick_size_change m 2,168 1,511 5ms 103ms 541ms 1.2s 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/08/2026-10-01T08.parquet sha256sum 2026-10-01T08.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.