Hour audit: 2026-10-03T21
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-03T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T21:00:00.000184010+00:00 · last event 2026-10-03T21:59:59.999955602+00:00
VOLUME 143,795,200 rows · 1,671,481,103 bytes (1.56 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 140,993,427 · m: 140,972,676 · g: 128,930,251 · i: 122,786,110 · k: 113,189,656 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,981,890 (2.07%) · m: 129,797,211 (90.27%) · g: 583,182 (0.41%) · i: 2,149,027 (1.49%) · k: 8,283,890 (5.76%) (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 143,795,200 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 dc314a9c3fe80936c668cdb1adf0273255c24270fcdaba6fb6e705f6647f9893
the corpus checksum ledger names this file with the same digest
joined 143,801,847 to merged 143,795,200, minus 6,647 (minus 0.0046%)
boundary drops 6,647 · 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-03T23:54:06Z 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,653,835 151,904,638 0-48 798ee83df0e061900011356cfe37b5611da2bfc4ed1e0085b2e3ace42e91b368 book 3,143,177 127,844,336 49-60 a19f8cfe627257117f024ee2b904bf10555bbb18e268080d01c949ebd2f870d3 last_trade_price 55,134 3,218,084 61-61 b42fee6880f4aea1ecbf94c481dd779b00098b4619375d5fc3dcf2c38775bbf6 market_resolved 5,184 540,259 62-62 0d78e99d5ebbd8da61ca531bfd3cd0304823099484330faa690b61c68ab8f80c new_market 2,944 256,552 63-63 51d4958dcc333ec436950200081d779e33abb89b627a7b8f741048f580dfd78c price_change 127,927,802 1,385,826,304 64-552 7a1b86a5f9d1e7254888e820b5d4f967d9e36e8037dc288a8a22248696469105 tick_size_change 7,124 255,193 553-553 35512ea1a2094b5f08248b6553c2cfbd6b4e997600a97c3d1a9d0924661a4a07 EVENT MIX count share price_change 127,927,802 88.97% best_bid_ask 12,653,835 8.80% book 3,143,177 2.19% last_trade_price 55,134 0.04% tick_size_change 7,124 <0.01% market_resolved 5,184 <0.01% new_market 2,944 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,654,049 12,653,835 214 8,495 FULL book 3,147,429 3,143,177 4,252 163,061 FULL last_trade_price 55,135 55,134 1 791 FULL market_resolved 5,184 5,184 0 723 FULL new_market 2,944 2,944 0 7 FULL price_change 127,929,982 127,927,802 2,180 6,057 FULL tick_size_change 7,124 7,124 0 589 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 11,490,246 1,914 82ms 110ms 542ms 25.9s 0 transport_latency_assumed best_bid_ask h 12,649,579 247,136 18ms 30ms 368ms 57.8s 0 transport_latency_assumed best_bid_ask i 10,883,228 118,479 20ms 31ms 217ms 10.4s 0 transport_latency_assumed best_bid_ask k 10,018,704 592,301 14ms 26ms 108ms 6.2s 0 transport_latency_assumed best_bid_ask m 12,651,157 11,694,005 5ms 14ms 108ms 8.9s 0 transport_latency_assumed book g 1,233,041 558,895 21.9min 1.9d 42.3d 127.0d 0 book_staleness book h 405,751 99,066 2.8min 1.7d 42.3d 127.0d 0 book_staleness book i 1,564,580 701,731 30.3min 1.9d 42.3d 127.0d 0 book_staleness book k 2,417,620 1,593,754 31.8min 2.1d 42.4d 127.0d 0 book_staleness book m 385,212 189,731 2.5min 1.6d 42.3d 127.0d 0 book_staleness last_trade_price g 49,784 46 88ms 473ms 6.7s 26.3s 0 transport_latency_assumed last_trade_price h 55,024 1,803 20ms 55ms 665ms 34.5s 0 transport_latency_assumed last_trade_price i 47,010 767 22ms 62ms 588ms 4.7s 0 transport_latency_assumed last_trade_price k 41,894 3,160 15ms 37ms 299ms 1.9s 0 transport_latency_assumed last_trade_price m 54,942 49,358 6ms 23ms 205ms 2.6s 0 transport_latency_assumed market_resolved g 3,125 353 88ms 5.3min 11.7min 12.2min 0 transport_latency_assumed market_resolved h 2,882 39 20ms 128ms 44.0s 44.4s 0 transport_latency_assumed market_resolved i 3,458 1,003 25ms 8.3min 10.7min 11.3min 0 transport_latency_assumed market_resolved k 3,441 1,077 18ms 7.7min 9.0min 9.4min 0 transport_latency_assumed market_resolved m 2,882 2,712 6ms 139ms 52.7s 55.0s 0 transport_latency_assumed new_market g 1,677 244 333ms 31.1s 6.9min 7.0min 0 transport_latency_assumed new_market h 1,617 471 163ms 34.7s 44.3s 1.6min 0 transport_latency_assumed new_market i 1,775 490 178ms 41.7s 5.3min 8.7min 0 transport_latency_assumed new_market k 1,760 773 74ms 4.4min 8.1min 8.1min 0 transport_latency_assumed new_market m 1,617 966 56ms 34.5s 55.8s 1.6min 0 transport_latency_assumed price_change g 116,145,990 21,730 82ms 129ms 1.0s 26.6s 0 transport_latency_assumed price_change h 127,871,454 2,633,236 19ms 33ms 509ms 57.9s 0 transport_latency_assumed price_change i 110,279,675 1,326,492 20ms 35ms 317ms 14.2s 0 transport_latency_assumed price_change k 100,700,601 6,092,411 14ms 27ms 131ms 7.0s 0 transport_latency_assumed price_change m 127,869,746 117,853,933 5ms 15ms 134ms 9.3s 0 transport_latency_assumed tick_size_change g 6,388 not meas. 82ms 99ms 474ms 1.1s 0 transport_latency_assumed tick_size_change h 7,120 139 18ms 28ms 333ms 4.2s 0 transport_latency_assumed tick_size_change i 6,384 65 20ms 30ms 304ms 584ms 0 transport_latency_assumed tick_size_change k 5,636 414 14ms 26ms 120ms 289ms 0 transport_latency_assumed tick_size_change m 7,120 6,506 5ms 15ms 129ms 299ms 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/21/2026-10-03T21.parquet sha256sum 2026-10-03T21.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.