Hour audit: 2026-10-04T02
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-04T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T02:00:00.000055267+00:00 · last event 2026-10-04T02:59:59.999954818+00:00
VOLUME 132,268,424 rows · 1,484,063,027 bytes (1.38 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 130,245,837 · h: 130,217,611 · i: 124,774,554 · k: 113,024,514 · g: 112,768,025 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 121,702,340 (92.01%) · h: 2,157,681 (1.63%) · i: 825,536 (0.62%) · k: 6,238,559 (4.72%) · g: 1,344,308 (1.02%) (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 132,268,424 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 897ac62b3d8f44ed7a46aeddb926ff0afc18afb12cb453fdccd363884027a5e0
the corpus checksum ledger names this file with the same digest
joined 132,282,695 to merged 132,268,424, minus 14,271 (minus 0.0108%)
boundary drops 14,271 · 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-04T04:54:31Z 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 11,318,326 131,765,198 0-43 2f7044155e98924b58a162f2ec44f3ef3083b0e6369d368c4f0082591be05c67 book 2,133,152 100,284,863 44-52 58d7660a6712c26d36cc63c3c351f12e84628ced79b7faabba3328471e9b84c7 last_trade_price 45,620 2,619,582 53-53 2b298e382c2fb09a430a626bb728f9e453a24e25b41c6e7c8bc8493fdfb7a5a8 market_resolved 4,365 483,854 54-54 3ddc26e4f850b127ffb82946903c23ded9c057f8e77bfb6c16f116486a4b0c8b new_market 1,047 85,122 55-55 976b3615f3f2512ce18cd4882f3924d1ed809036e339a96368eac0c2b914cc70 price_change 118,758,906 1,247,065,897 56-509 b0ef9249a51dfec33ff9b54d2607b78186c825eb4eda3148163d7f96661d927f tick_size_change 7,008 249,520 510-510 5e2506fc27127e2af625789a7459e5e9c97e0e79cfc6bf0f6de6f5ec55940f83 EVENT MIX count share price_change 118,758,906 89.79% best_bid_ask 11,318,326 8.56% book 2,133,152 1.61% last_trade_price 45,620 0.03% tick_size_change 7,008 <0.01% market_resolved 4,365 <0.01% new_market 1,047 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,318,588 11,318,326 262 5,162 FULL book 2,143,806 2,133,152 10,654 226,176 FULL last_trade_price 45,620 45,620 0 447 FULL market_resolved 4,368 4,365 3 641 FULL new_market 1,047 1,047 0 0 FULL price_change 118,762,258 118,758,906 3,352 5,020 FULL tick_size_change 7,008 7,008 0 375 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,728,811 502 79ms 96ms 290ms 11.0s 0 transport_latency_assumed best_bid_ask h 11,317,154 172,266 18ms 26ms 125ms 54.8s 0 transport_latency_assumed best_bid_ask i 10,819,936 53,861 21ms 29ms 92ms 6.1s 0 transport_latency_assumed best_bid_ask k 9,750,155 499,307 13ms 23ms 75ms 6.3s 0 transport_latency_assumed best_bid_ask m 11,317,278 10,592,390 5ms 12ms 61ms 3.2s 0 transport_latency_assumed book g 1,494,075 1,335,238 57.8min 2.1d 46.0d 127.2d 0 book_staleness book h 124,588 13,774 23ms 3.0h 26.7d 127.2d 0 book_staleness book i 579,443 153,935 28.1min 2.1d 42.5d 127.2d 0 book_staleness book k 1,537,596 537,552 1.1h 2.1d 45.4d 127.2d 0 book_staleness book m 130,401 92,653 10ms 4.2h 26.7d 108.7d 0 book_staleness last_trade_price g 38,610 58 80ms 185ms 1.0s 6.4s 0 transport_latency_assumed last_trade_price h 45,547 1,665 19ms 33ms 233ms 28.4s 0 transport_latency_assumed last_trade_price i 43,727 470 23ms 40ms 286ms 1.8s 0 transport_latency_assumed last_trade_price k 38,339 3,025 15ms 31ms 205ms 1.8s 0 transport_latency_assumed last_trade_price m 45,524 40,402 6ms 21ms 203ms 1.8s 0 transport_latency_assumed market_resolved g 2,812 461 83ms 9.9min 15.5min 15.8min 0 transport_latency_assumed market_resolved h 2,433 141 20ms 71ms 49.8s 55.5s 0 transport_latency_assumed market_resolved i 2,896 168 24ms 15.8min 23.0min 23.4min 0 transport_latency_assumed market_resolved k 3,283 1,319 20ms 12.1min 17.9min 18.2min 0 transport_latency_assumed market_resolved m 2,433 2,276 6ms 42ms 52.7s 59.2s 0 transport_latency_assumed new_market g 619 119 11.4s 5.2min 10.1min 10.2min 0 transport_latency_assumed new_market h 511 128 257ms 28.7s 50.8s 1.3min 0 transport_latency_assumed new_market i 581 206 332ms 10.6min 17.6min 17.7min 0 transport_latency_assumed new_market k 637 376 86ms 6.8min 7.0min 7.0min 0 transport_latency_assumed new_market m 511 218 79ms 25.9s 41.9s 1.7min 0 transport_latency_assumed price_change g 101,496,778 7,930 79ms 100ms 413ms 14.5s 0 transport_latency_assumed price_change h 118,720,370 1,969,626 18ms 27ms 141ms 54.8s 0 transport_latency_assumed price_change i 113,321,091 616,882 22ms 30ms 122ms 6.5s 0 transport_latency_assumed price_change k 101,688,296 5,196,652 14ms 24ms 84ms 6.3s 0 transport_latency_assumed price_change m 118,742,682 110,967,816 5ms 13ms 67ms 4.4s 0 transport_latency_assumed tick_size_change g 6,320 not meas. 78ms 94ms 574ms 954ms 0 transport_latency_assumed tick_size_change h 7,008 81 18ms 24ms 59ms 294ms 0 transport_latency_assumed tick_size_change i 6,880 14 22ms 29ms 139ms 242ms 0 transport_latency_assumed tick_size_change k 6,208 328 13ms 21ms 44ms 153ms 0 transport_latency_assumed tick_size_change m 7,008 6,585 5ms 11ms 34ms 126ms 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-04/02/2026-10-04T02.parquet sha256sum 2026-10-04T02.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.