Hour audit: 2026-10-01T03
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-01T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T03:00:00.000006233+00:00 · last event 2026-10-01T03:59:59.999794060+00:00
VOLUME 109,322,919 rows · 1,123,582,440 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 101,564,099 · m: 99,383,677 · i: 97,646,660 · g: 95,587,028 · k: 94,836,534 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,909,474 (5.41%) · m: 80,125,874 (73.29%) · i: 1,032,087 (0.94%) · g: 76,470 (0.07%) · k: 22,179,014 (20.29%) (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 109,322,919 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 821485b81825786de76af51591fc9e6f3fcda1c3d13e0c1aca588cbbe98f40d3
the corpus checksum ledger names this file with the same digest
joined 109,324,585 to merged 109,322,919, minus 1,666 (minus 0.0015%)
boundary drops 1,666 · 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-01T06:28:27Z 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,592,544 122,502,869 0-40 27b0055d52142c900e6f31b9e931dd4d2b51e2ef005053fd4b36b61ebbae9217 book 147,010 16,256,653 41-41 a071e0ed616159862bc18e3fe5806d590bbb206ffda723d78c0c3b120b1cb784 last_trade_price 45,382 2,690,584 42-42 6d2663cd125aa416ef20bf0b7f66412ec4faa40c947a96eca6fbbac88bbef24b market_resolved 1,571 232,333 43-43 8ce7d75dc6078dd14fee8c50216078443086f752b6a7368bdb25ab974b2713ba new_market 382 42,228 44-44 105fd5b555859b798186831f190bccaf6fdaff7b564002f0e952fcfca1c16e85 price_change 98,533,778 980,527,860 45-420 b92027fe0da689c6d966138e1edb9753d0997db05db21f904e7a8155d19b9bcc tick_size_change 2,252 84,205 421-421 bbb3ece702da5379379d103ac3292032ed8db5e62f1bf599f948e95c6e7edc66 EVENT MIX count share price_change 98,533,778 90.13% best_bid_ask 10,592,544 9.69% book 147,010 0.13% last_trade_price 45,382 0.04% tick_size_change 2,252 <0.01% market_resolved 1,571 <0.01% new_market 382 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,592,740 10,592,544 196 96 FULL book 147,010 147,010 0 25,854 FULL last_trade_price 45,382 45,382 0 1 FULL market_resolved 1,571 1,571 0 0 FULL new_market 382 382 0 0 FULL price_change 98,535,248 98,533,778 1,470 64,580 FULL tick_size_change 2,252 2,252 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,591,496 416 78ms 96ms 181ms 4.4s 0 transport_latency_assumed best_bid_ask h 10,591,823 213,920 17ms 25ms 82ms 32.7s 0 transport_latency_assumed best_bid_ask i 10,592,081 33,372 27ms 56ms 106ms 5.4s 0 transport_latency_assumed best_bid_ask k 10,591,893 1,842,236 11ms 20ms 99ms 32.4s 0 transport_latency_assumed best_bid_ask m 10,592,332 8,502,600 5ms 19ms 68ms 1.4s 0 transport_latency_assumed book g 91,300 337 84ms 127ms 455ms 5.4s 0 book_staleness book h 126,722 36,955 23ms 8.0h 23.7d 105.7d 0 book_staleness book i 92,790 2,068 28ms 72ms 20.4min 105.7d 0 book_staleness book k 101,639 23,750 14ms 3.0s 4.0d 105.7d 0 book_staleness book m 100,530 83,900 7ms 140ms 2.3d 105.7d 0 book_staleness last_trade_price g 45,367 5 83ms 139ms 401ms 2.2s 0 transport_latency_assumed last_trade_price h 45,366 1,056 18ms 39ms 225ms 6.1s 0 transport_latency_assumed last_trade_price i 45,365 255 28ms 65ms 234ms 1.3s 0 transport_latency_assumed last_trade_price k 45,364 7,500 12ms 25ms 114ms 1.5s 0 transport_latency_assumed last_trade_price m 45,373 36,566 6ms 23ms 112ms 1.1s 0 transport_latency_assumed market_resolved g 1,434 70 80ms 204ms 51.6s 56.2s 0 transport_latency_assumed market_resolved h 1,434 22 19ms 22.7s 54.2s 55.8s 0 transport_latency_assumed market_resolved i 1,434 1 30ms 30.3s 49.4s 52.7s 0 transport_latency_assumed market_resolved k 1,434 247 12ms 20.8s 53.2s 57.8s 0 transport_latency_assumed market_resolved m 1,434 1,231 6ms 28.9s 48.9s 51.7s 0 transport_latency_assumed new_market g 266 56 112ms 11.4s 17.9s 1.3min 0 transport_latency_assumed new_market h 266 60 51ms 11.4s 1.6min 1.8min 0 transport_latency_assumed new_market i 266 31 41ms 437ms 14.2s 1.4min 0 transport_latency_assumed new_market k 266 35 56ms 7.1s 1.2min 1.8min 0 transport_latency_assumed new_market m 266 200 26ms 9.7s 1.3min 1.6min 0 transport_latency_assumed price_change g 84,854,913 75,586 79ms 99ms 236ms 5.1s 0 transport_latency_assumed price_change h 90,796,236 5,657,426 17ms 28ms 108ms 32.8s 0 transport_latency_assumed price_change i 86,912,472 996,358 27ms 59ms 130ms 5.5s 0 transport_latency_assumed price_change k 84,093,686 20,304,778 11ms 22ms 112ms 33.0s 0 transport_latency_assumed price_change m 88,641,490 71,499,630 5ms 21ms 74ms 1.4s 0 transport_latency_assumed tick_size_change g 2,252 not meas. 78ms 94ms 165ms 276ms 0 transport_latency_assumed tick_size_change h 2,252 35 18ms 28ms 42ms 54ms 0 transport_latency_assumed tick_size_change i 2,252 2 26ms 54ms 74ms 126ms 0 transport_latency_assumed tick_size_change k 2,252 468 11ms 23ms 59ms 127ms 0 transport_latency_assumed tick_size_change m 2,252 1,747 5ms 19ms 29ms 133ms 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/03/2026-10-01T03.parquet sha256sum 2026-10-01T03.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.