Hour audit: 2026-10-04T20
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-04T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T20:00:00.000014436+00:00 · last event 2026-10-04T20:59:59.999924802+00:00
VOLUME 127,243,296 rows · 1,508,144,611 bytes (1.40 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 126,338,407 · i: 126,321,604 · h: 126,311,649 · o: 120,466,996 · n: 118,918,524 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 69,101,010 (54.31%) · i: 893,174 (0.70%) · h: 1,207,457 (0.95%) · o: 55,592,463 (43.69%) · n: 449,192 (0.35%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 df5113590169e1f0589acf4e83f4849e59a3786f32c446a4ba541e3ef30dded7
the corpus checksum ledger names this file with the same digest
joined 127,253,885 to merged 127,243,296, minus 10,589 (minus 0.0083%)
boundary drops 10,589 · 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-04T22:04:50Z 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,741,764 136,497,475 0-40 2f1f5b5b0406f68c6af2f5c8ad3b02106d29011683e76351fdb308a4b956ecc6 book 905,442 76,262,501 41-44 2279aff55ead4152199da09ee7eda2fcd83d06aafea66abe32f4851dd4fef7a2 last_trade_price 72,374 4,158,076 45-45 8ca013b8f83cacc2df93571e2ca2a681081ac4a392f04c95bac5b3d79deb8ef8 market_resolved 5,437 734,256 46-46 23994542342570a0a4de511d979bd18313ba40f53f7e52324891402949275e8f new_market 6,746 720,199 47-47 3e5e1580c1336d559565940484a3dbf41094428a0166fe18379f70f442846668 price_change 115,496,201 1,287,765,881 48-488 344c8ea142c43d125ac2cef13e6fa89a1a67f0f5461b2a2d7c59820695bb67af tick_size_change 15,332 558,858 489-489 8bcf643b1857d22051516d585ef0717fc1ae6f9e28085392a2bbd7e38ee1e603 EVENT MIX count share price_change 115,496,201 90.77% best_bid_ask 10,741,764 8.44% book 905,442 0.71% last_trade_price 72,374 0.06% tick_size_change 15,332 0.01% new_market 6,746 <0.01% market_resolved 5,437 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,742,436 10,741,764 672 1,947 FULL book 905,502 905,442 60 236,715 FULL last_trade_price 72,377 72,374 3 190 FULL market_resolved 5,437 5,437 0 49 FULL new_market 6,746 6,746 0 0 FULL price_change 115,506,055 115,496,201 9,854 2,510 FULL tick_size_change 15,332 15,332 0 116 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,737,994 96,546 20ms 48ms 1.6s 2.0min 0 transport_latency_assumed best_bid_ask i 10,738,841 71,631 22ms 44ms 421ms 44.4s 0 transport_latency_assumed best_bid_ask m 10,739,415 5,877,899 5ms 18ms 225ms 7.2s 0 transport_latency_assumed best_bid_ask n 10,085,764 16,407 48ms 105ms 674ms 40.7s 0 transport_latency_assumed best_bid_ask o 10,200,785 4,679,281 6ms 19ms 264ms 13.4s 0 transport_latency_assumed book h 159,863 6,464 27ms 2.0s 6.0h 109.4d 0 book_staleness book i 156,632 5,396 26ms 992ms 2.7h 109.3d 0 book_staleness book m 160,506 85,523 9ms 477ms 8.0h 109.4d 0 book_staleness book n 657,903 233,352 8.8min 23.6h 43.3d 127.9d 0 book_staleness book o 658,377 574,707 5.9min 22.6h 43.3d 127.9d 0 book_staleness last_trade_price h 72,080 950 22ms 199ms 3.9s 1.5min 0 transport_latency_assumed last_trade_price i 72,008 549 25ms 205ms 5.6s 18.7s 0 transport_latency_assumed last_trade_price m 72,072 39,314 7ms 32ms 321ms 4.8s 0 transport_latency_assumed last_trade_price n 66,439 190 57ms 659ms 8.9s 38.7s 0 transport_latency_assumed last_trade_price o 67,898 31,371 7ms 31ms 330ms 6.8s 0 transport_latency_assumed market_resolved h 4,559 27 22ms 21.3s 51.3s 1.0min 0 transport_latency_assumed market_resolved i 4,559 20 24ms 18.8s 50.9s 57.0s 0 transport_latency_assumed market_resolved m 4,559 2,779 7ms 18.7s 52.3s 55.7s 0 transport_latency_assumed market_resolved n 4,823 549 52ms 4.1min 9.3min 12.4min 0 transport_latency_assumed market_resolved o 4,637 2,062 7ms 35.1s 7.3min 9.9min 0 transport_latency_assumed new_market h 4,634 659 19.7s 55.1s 1.2min 1.7min 0 transport_latency_assumed new_market i 4,634 970 20.8s 55.0s 1.3min 1.8min 0 transport_latency_assumed new_market m 4,634 2,012 19.5s 53.1s 1.2min 1.6min 0 transport_latency_assumed new_market n 4,651 902 21.2s 56.7s 1.3min 9.2min 0 transport_latency_assumed new_market o 5,420 2,203 24.1s 7.2min 9.1min 9.7min 0 transport_latency_assumed price_change h 115,317,187 1,102,723 20ms 66ms 2.6s 2.0min 0 transport_latency_assumed price_change i 115,329,598 814,517 22ms 56ms 717ms 46.8s 0 transport_latency_assumed price_change m 115,341,889 63,085,197 6ms 20ms 236ms 7.2s 0 transport_latency_assumed price_change n 108,083,784 197,778 49ms 151ms 2.4s 41.0s 0 transport_latency_assumed price_change o 109,514,839 50,295,986 6ms 22ms 274ms 14.1s 0 transport_latency_assumed tick_size_change h 15,332 88 19ms 36ms 743ms 1.4min 0 transport_latency_assumed tick_size_change i 15,332 91 22ms 37ms 404ms 6.0s 0 transport_latency_assumed tick_size_change m 15,332 8,286 5ms 14ms 203ms 1.4s 0 transport_latency_assumed tick_size_change n 15,160 14 48ms 81ms 563ms 10.2s 0 transport_latency_assumed tick_size_change o 15,040 6,853 5ms 17ms 261ms 6.3s 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/20/2026-10-04T20.parquet sha256sum 2026-10-04T20.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.