Hour audit: 2026-10-01T22
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-01T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T22:00:00.000081936+00:00 · last event 2026-10-01T22:59:59.999994614+00:00
VOLUME 105,488,704 rows · 1,103,220,702 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 104,772,636 · h: 104,752,536 · k: 104,746,400 · g: 104,726,223 · i: 104,676,796 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 102,112,478 (96.80%) · h: 563,144 (0.53%) · k: 2,173,916 (2.06%) · g: 256,423 (0.24%) · i: 382,743 (0.36%) (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,488,704 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 47316521d6bc4bfd91ba4e98b477778d04a440fe22f2fa8510051a5bc394bca4
the corpus checksum ledger names this file with the same digest
joined 105,492,808 to merged 105,488,704, minus 4,104 (minus 0.0039%)
boundary drops 4,104 · 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-02T00:44:44Z 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 9,476,980 109,436,398 0-36 7d25312d4500669305f9d2651b81db7ececac9db4bb951aba19a1f2bb855feff book 1,209,560 86,274,258 37-41 55f463bc030afc2c82f97d92f87e64a5947e593b49d48f2e8b5aba8a49da5f2a last_trade_price 45,862 2,626,200 42-42 b3f8ab78272bba33600bd6c3429a149a81bb8742c6cb7ac5ae59fde33e3b07d3 market_resolved 2,647 404,487 43-43 f4b7ffdf0fba298f9c7fab24b983058b6d16f57b528f5a7317e3d69fa60cd4c7 new_market 511 54,844 44-44 7a457d777d3ca4582406eb1ea5e0f8908eb3d0af5aa837f7a8a2946bcc0ce573 price_change 94,750,180 903,109,552 45-406 56b9aed0993f59c1de9e336778596c7e5510cba64e1e24a6b6cd8c6e07bd6d4b tick_size_change 2,964 108,914 407-407 d42f02b601f8faca4bcbe804e344b5bcc788e39d534584ce026c8fdce57ab296 EVENT MIX count share price_change 94,750,180 89.82% best_bid_ask 9,476,980 8.98% book 1,209,560 1.15% last_trade_price 45,862 0.04% tick_size_change 2,964 <0.01% market_resolved 2,647 <0.01% new_market 511 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,477,128 9,476,980 148 93 FULL book 1,211,670 1,209,560 2,110 193,606 FULL last_trade_price 45,862 45,862 0 2 FULL market_resolved 2,647 2,647 0 0 FULL new_market 511 511 0 0 FULL price_change 94,752,026 94,750,180 1,846 65 FULL tick_size_change 2,964 2,964 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,473,257 1,565 76ms 91ms 202ms 7.1s 0 transport_latency_assumed best_bid_ask h 9,475,028 32,135 18ms 32ms 83ms 48.7s 0 transport_latency_assumed best_bid_ask i 9,474,785 10,769 26ms 43ms 70ms 5.2s 0 transport_latency_assumed best_bid_ask k 9,475,183 171,491 13ms 20ms 117ms 6.6s 0 transport_latency_assumed best_bid_ask m 9,475,420 9,261,020 5ms 8ms 40ms 3.7s 0 transport_latency_assumed book g 511,785 244,734 15.9min 3.0d 40.4d 125.0d 0 book_staleness book h 496,648 181,299 15.6min 3.1d 40.4d 125.0d 0 book_staleness book i 459,750 260,180 10.4min 3.0d 40.4d 125.0d 0 book_staleness book k 501,588 218,061 15.1min 3.0d 40.4d 125.0d 0 book_staleness book m 511,492 305,286 16.6min 2.9d 40.4d 125.0d 0 book_staleness last_trade_price g 45,827 6 77ms 133ms 802ms 4.3s 0 transport_latency_assumed last_trade_price h 45,840 178 20ms 32ms 174ms 8.1s 0 transport_latency_assumed last_trade_price i 45,839 43 40ms 45ms 135ms 1.9s 0 transport_latency_assumed last_trade_price k 45,839 827 14ms 20ms 83ms 1.0s 0 transport_latency_assumed last_trade_price m 45,838 44,808 6ms 9ms 37ms 1.2s 0 transport_latency_assumed market_resolved g 2,514 1 77ms 212ms 44.2s 1.3min 0 transport_latency_assumed market_resolved h 2,514 11 20ms 55ms 50.0s 50.9s 0 transport_latency_assumed market_resolved i 2,514 279 39ms 15.9s 50.0s 54.8s 0 transport_latency_assumed market_resolved k 2,514 168 13ms 25ms 54.3s 56.1s 0 transport_latency_assumed market_resolved m 2,514 2,188 5ms 17.8s 50.8s 56.9s 0 transport_latency_assumed new_market g 340 21 109ms 8.1s 13.8s 1.3min 0 transport_latency_assumed new_market h 340 115 73ms 14.5s 45.3s 1.6min 0 transport_latency_assumed new_market i 340 52 52ms 9.9s 52.2s 1.7min 0 transport_latency_assumed new_market k 340 45 72ms 333ms 47.3s 1.5min 0 transport_latency_assumed new_market m 340 278 27ms 8.6s 12.2s 1.7min 0 transport_latency_assumed price_change g 94,689,536 10,096 76ms 94ms 384ms 8.1s 0 transport_latency_assumed price_change h 94,729,202 349,394 19ms 32ms 146ms 49.1s 0 transport_latency_assumed price_change i 94,690,604 111,384 33ms 43ms 128ms 5.8s 0 transport_latency_assumed price_change k 94,717,976 1,783,224 14ms 21ms 119ms 6.6s 0 transport_latency_assumed price_change m 94,734,068 92,496,082 5ms 8ms 55ms 3.8s 0 transport_latency_assumed tick_size_change g 2,964 not meas. 76ms 97ms 355ms 758ms 0 transport_latency_assumed tick_size_change h 2,964 12 19ms 33ms 254ms 1.0s 0 transport_latency_assumed tick_size_change i 2,964 36 36ms 44ms 213ms 389ms 0 transport_latency_assumed tick_size_change k 2,960 100 13ms 21ms 152ms 314ms 0 transport_latency_assumed tick_size_change m 2,964 2,816 5ms 9ms 233ms 240ms 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/22/2026-10-01T22.parquet sha256sum 2026-10-01T22.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.