Hour audit: 2026-10-08T20
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-08T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T20:00:00.000550766+00:00 · last event 2026-10-08T20:59:59.999952194+00:00
VOLUME 113,152,731 rows · 1,277,326,487 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 112,853,279 · m: 112,790,625 · n: 112,771,806 · i: 112,643,974 · h: 112,522,414 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 54,729,519 (48.37%) · m: 56,914,300 (50.30%) · n: 169,465 (0.15%) · i: 527,440 (0.47%) · h: 812,007 (0.72%) (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 113,152,731 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 de61f6a8cb91d9ddefeef97e931e5104b67b955105beb6e274d53a6737474e22
the corpus checksum ledger names this file with the same digest
joined 113,154,981 to merged 113,152,731, minus 2,250 (minus 0.0020%)
boundary drops 2,250 · 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-08T22:04:04Z as himno
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,611,926 155,234,587 0-48 846aef558759a5330884e462a08cef978798e1b06f5289a7b752da67a926886e book 357,255 36,476,162 49-50 7d71cba561dbe86c1efb02c4fa3c492076f6f25908a86a4dbd6faf6bdb03501f last_trade_price 48,870 2,857,529 51-51 77306f58a621945740fde6b527a7b88ba50e5a418b3a4ddafe7f937d8cc8db2b market_resolved 617 98,073 52-52 c02aed0748bfdc60cb9aaa48a2217af71db4a8bd09f72eb421ddcb179080d99b new_market 815 86,556 53-53 85512f64021b2eec1fcff3532b05c94c5335af9c7c722db450c1beb9f47a4d79 price_change 100,130,940 1,081,196,106 54-435 c4247f1cf701b22f616f8c4e1d2d61ad6457b0b73dfc33a77d6d0ba2783908e0 tick_size_change 2,308 86,677 436-436 a3ff287a9b675203bd7ab67ad5cbdc2e086ea748213e768a251e4187dae72e91 EVENT MIX count share price_change 100,130,940 88.49% best_bid_ask 12,611,926 11.15% book 357,255 0.32% last_trade_price 48,870 0.04% tick_size_change 2,308 <0.01% new_market 815 <0.01% market_resolved 617 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,612,106 12,611,926 180 70 FULL book 357,271 357,255 16 106,933 FULL last_trade_price 48,870 48,870 0 1 FULL market_resolved 617 617 0 0 FULL new_market 815 815 0 0 FULL price_change 100,132,994 100,130,940 2,054 130 FULL tick_size_change 2,308 2,308 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,600,114 78,715 18ms 30ms 189ms 45.6s 0 transport_latency_assumed best_bid_ask i 12,604,681 51,249 21ms 30ms 145ms 7.2s 0 transport_latency_assumed best_bid_ask m 12,607,849 6,362,199 5ms 13ms 81ms 8.3s 0 transport_latency_assumed best_bid_ask n 12,608,899 4,866 44ms 61ms 209ms 12.1s 0 transport_latency_assumed best_bid_ask o 12,609,270 6,114,897 5ms 14ms 83ms 4.0s 0 transport_latency_assumed book h 160,809 56,011 76ms 7.3h 33.3d 131.9d 0 book_staleness book i 126,123 23,764 34ms 1.6h 21.8d 131.9d 0 book_staleness book m 162,571 110,855 15ms 7.6h 31.4d 113.4d 0 book_staleness book n 181,107 77,290 867ms 13.2h 36.0d 131.9d 0 book_staleness book o 152,662 89,335 13ms 5.4h 31.4d 131.9d 0 book_staleness last_trade_price h 48,133 322 21ms 221ms 1.0s 45.3s 0 transport_latency_assumed last_trade_price i 48,332 228 25ms 355ms 2.7s 7.2s 0 transport_latency_assumed last_trade_price m 48,477 25,490 6ms 23ms 193ms 1.2s 0 transport_latency_assumed last_trade_price n 48,322 158 51ms 579ms 4.5s 12.0s 0 transport_latency_assumed last_trade_price o 48,589 22,672 6ms 30ms 216ms 3.6s 0 transport_latency_assumed market_resolved h 594 10 20ms 72ms 40.6s 55.1s 0 transport_latency_assumed market_resolved i 594 43 22ms 112ms 54.0s 57.1s 0 transport_latency_assumed market_resolved m 594 298 5ms 15ms 55.9s 59.1s 0 transport_latency_assumed market_resolved n 594 1 46ms 167ms 30.6s 45.0s 0 transport_latency_assumed market_resolved o 594 265 6ms 21ms 55.1s 58.4s 0 transport_latency_assumed new_market h 520 60 148ms 17.0s 23.3s 1.6min 0 transport_latency_assumed new_market i 520 137 104ms 16.3s 23.9s 1.7min 0 transport_latency_assumed new_market m 520 267 63ms 14.7s 59.8s 1.7min 0 transport_latency_assumed new_market n 520 74 189ms 14.4s 1.1min 1.7min 0 transport_latency_assumed new_market o 520 277 67ms 13.8s 22.1s 1.6min 0 transport_latency_assumed price_change h 99,709,936 676,880 18ms 40ms 579ms 51.0s 0 transport_latency_assumed price_change i 99,861,416 452,012 21ms 44ms 1.0s 7.8s 0 transport_latency_assumed price_change m 99,968,306 50,414,060 5ms 15ms 110ms 8.4s 0 transport_latency_assumed price_change n 99,930,056 87,076 45ms 83ms 1.7s 12.3s 0 transport_latency_assumed price_change o 100,039,336 48,500,912 5ms 16ms 116ms 4.2s 0 transport_latency_assumed tick_size_change h 2,308 9 18ms 30ms 96ms 198ms 0 transport_latency_assumed tick_size_change i 2,308 7 21ms 36ms 119ms 215ms 0 transport_latency_assumed tick_size_change m 2,308 1,131 5ms 13ms 125ms 339ms 0 transport_latency_assumed tick_size_change n 2,308 not meas. 45ms 60ms 181ms 303ms 0 transport_latency_assumed tick_size_change o 2,308 1,161 5ms 14ms 95ms 245ms 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-08/20/2026-10-08T20.parquet sha256sum 2026-10-08T20.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.