Hour audit: 2026-10-07T09
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-07T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T09:00:00.000111254+00:00 · last event 2026-10-07T09:59:59.999978391+00:00
VOLUME 117,320,452 rows · 1,380,497,361 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 116,692,586 · h: 116,646,908 · m: 116,645,818 · i: 116,296,462 · n: 116,255,045 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 55,756,990 (47.53%) · h: 1,187,448 (1.01%) · m: 59,229,041 (50.48%) · i: 778,351 (0.66%) · n: 368,622 (0.31%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 117,320,452 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c982b7b7589a8281f998bd965d999908d566a6d320b07214da924d03b794cd74
the corpus checksum ledger names this file with the same digest
joined 117,321,586 to merged 117,320,452, minus 1,134 (minus 0.0010%)
boundary drops 1,134 · 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-07T11:05:21Z 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 10,305,187 130,963,485 0-39 5034a1dc672a0c743916ae8d87d908a50685a5c34ac6a815b6c822913b2b6169 book 1,083,628 86,958,346 40-44 c3e44d1f2ee2c5a1bbfd17e66d26d2c3b460b289534a4f173b4098e34ea36423 last_trade_price 59,744 3,414,067 45-45 a43588b4b7da1c27e128977c2d011267edb76cdd3975592e2f180726feb1444d market_resolved 617 103,363 46-46 b9272f3a443e877b2116ec7f183bac0d9424fbf181230887ce761739049b5205 new_market 2,362 214,829 47-47 3aef713eb85b29330b7283fcd1c2d5e5a1901e0de20a4f2f6ffea6b8fd773b93 price_change 105,865,986 1,157,396,581 48-451 4673804f9ff2c03c7bff59c132325dcca429bec6c535f84592f01e0b7cc8c54c tick_size_change 2,928 108,532 452-452 36c66b08821734fe26786f584eafe9c7e6a7e180d299c62891f4408a9bc0b603 EVENT MIX count share price_change 105,865,986 90.24% best_bid_ask 10,305,187 8.78% book 1,083,628 0.92% last_trade_price 59,744 0.05% tick_size_change 2,928 <0.01% new_market 2,362 <0.01% market_resolved 617 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,305,259 10,305,187 72 281 FULL book 1,083,658 1,083,628 30 254,740 FULL last_trade_price 59,744 59,744 0 1 FULL market_resolved 617 617 0 2 FULL new_market 2,362 2,362 0 0 FULL price_change 105,867,018 105,865,986 1,032 184 FULL tick_size_change 2,928 2,928 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,300,727 80,862 18ms 32ms 366ms 1.4min 0 transport_latency_assumed best_bid_ask i 10,301,743 62,161 21ms 34ms 197ms 8.0s 0 transport_latency_assumed best_bid_ask m 10,301,809 5,243,204 5ms 16ms 138ms 7.0s 0 transport_latency_assumed best_bid_ask n 10,293,542 4,143 43ms 69ms 463ms 30.9s 0 transport_latency_assumed best_bid_ask o 10,301,465 4,914,817 5ms 16ms 148ms 8.9s 0 transport_latency_assumed book h 487,703 224,435 6.2min 1.5d 45.8d 130.5d 0 book_staleness book i 164,899 21,866 46ms 2.4h 29.9d 112.0d 0 book_staleness book m 509,975 260,138 7.5min 1.5d 45.8d 130.5d 0 book_staleness book n 614,615 314,861 10.8min 1.6d 45.8d 130.5d 0 book_staleness book o 520,828 262,328 7.8min 1.5d 45.8d 130.5d 0 book_staleness last_trade_price h 59,569 545 22ms 190ms 1.3s 52.3s 0 transport_latency_assumed last_trade_price i 59,392 342 27ms 344ms 1.8s 7.9s 0 transport_latency_assumed last_trade_price m 59,460 30,306 7ms 33ms 239ms 2.7s 0 transport_latency_assumed last_trade_price n 57,661 34 61ms 2.3s 14.1s 31.1s 0 transport_latency_assumed last_trade_price o 59,467 28,517 7ms 29ms 246ms 4.2s 0 transport_latency_assumed market_resolved h 616 2 21ms 140ms 19.4s 21.1s 0 transport_latency_assumed market_resolved i 617 29 23ms 130ms 13.9s 14.9s 0 transport_latency_assumed market_resolved m 617 327 6ms 70ms 13.9s 14.9s 0 transport_latency_assumed market_resolved n 616 not meas. 47ms 344ms 32.0s 33.3s 0 transport_latency_assumed market_resolved o 617 259 6ms 40ms 23.4s 24.3s 0 transport_latency_assumed new_market h 1,385 324 213ms 39.7s 45.9s 1.5min 0 transport_latency_assumed new_market i 1,385 571 143ms 39.0s 46.2s 1.6min 0 transport_latency_assumed new_market m 1,385 727 79ms 38.7s 44.3s 1.7min 0 transport_latency_assumed new_market n 1,385 152 265ms 38.6s 46.0s 1.4min 0 transport_latency_assumed new_market o 1,385 588 94ms 38.4s 43.3s 1.7min 0 transport_latency_assumed price_change h 105,793,980 881,276 19ms 42ms 569ms 1.5min 0 transport_latency_assumed price_change i 105,765,498 693,366 22ms 47ms 625ms 8.1s 0 transport_latency_assumed price_change m 105,769,648 53,692,718 5ms 18ms 158ms 7.6s 0 transport_latency_assumed price_change n 105,284,298 49,432 44ms 112ms 3.8s 31.6s 0 transport_latency_assumed price_change o 105,805,896 50,549,194 5ms 19ms 168ms 9.5s 0 transport_latency_assumed tick_size_change h 2,928 4 18ms 29ms 157ms 2.2s 0 transport_latency_assumed tick_size_change i 2,928 16 21ms 37ms 72ms 1.9s 0 transport_latency_assumed tick_size_change m 2,924 1,621 5ms 11ms 48ms 215ms 0 transport_latency_assumed tick_size_change n 2,928 not meas. 43ms 63ms 297ms 545ms 0 transport_latency_assumed tick_size_change o 2,928 1,287 5ms 12ms 113ms 377ms 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-07/09/2026-10-07T09.parquet sha256sum 2026-10-07T09.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.