Hour audit: 2026-10-07T17
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-07T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T17:00:00.000062161+00:00 · last event 2026-10-07T17:59:59.999917923+00:00
VOLUME 119,896,742 rows · 1,348,339,270 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 119,814,752 · m: 119,798,178 · h: 119,712,313 · i: 119,547,515 · n: 119,108,026 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 60,121,890 (50.14%) · m: 57,886,039 (48.28%) · h: 1,133,626 (0.95%) · i: 699,721 (0.58%) · n: 55,466 (0.05%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 ed03f30ccfa8c85015e57504c31ce7450aac3f9e5e3b46952feb25a47fefbc46
the corpus checksum ledger names this file with the same digest
joined 119,903,358 to merged 119,896,742, minus 6,616 (minus 0.0055%)
boundary drops 6,616 · 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-07T19:05:54Z 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,020,590 127,358,909 0-38 d376cde106654c9ccf0e0ba257b2f01d9505cdd519a32d48f750687c2c9e5629 book 165,052 18,310,193 39-39 fc1c865a5fd97c6acb6c653ce90bc06fa5b87b416b935e6d3683ee9a037c4c31 last_trade_price 61,910 3,526,387 40-40 5a892d70f1b457e2dcba6fa87495365b4317ca7d1723db2a8cc05bfdf6200c54 market_resolved 679 112,617 41-41 0e5ce2525acb2c6e92db84a361cc2af87ec59365084a63950b9480507e5d16e5 new_market 1,273 132,403 42-42 bc26e4424f4d0a347f8b28e110ebcde172f8af8ea8718bf17f1e65848139d4c2 price_change 109,644,590 1,197,432,112 43-461 c525b683a844189746ce7d5ea5c36aebaf3ae50834fe567f6142c83a658cc07e tick_size_change 2,648 98,422 462-462 ff7b747a0afdcdc6c6f718a711f7e706519a34a785e194351a2d154a3184a61d EVENT MIX count share price_change 109,644,590 91.45% best_bid_ask 10,020,590 8.36% book 165,052 0.14% last_trade_price 61,910 0.05% tick_size_change 2,648 <0.01% new_market 1,273 <0.01% market_resolved 679 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,020,728 10,020,590 138 56 FULL book 165,134 165,052 82 15,817 FULL last_trade_price 61,910 61,910 0 2 FULL market_resolved 679 679 0 0 FULL new_market 1,273 1,273 0 0 FULL price_change 109,650,986 109,644,590 6,396 72 FULL tick_size_change 2,648 2,648 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,018,107 89,229 19ms 34ms 257ms 49.4s 0 transport_latency_assumed best_bid_ask i 10,010,138 56,185 22ms 37ms 206ms 9.7s 0 transport_latency_assumed best_bid_ask m 10,019,364 4,816,381 5ms 17ms 110ms 8.3s 0 transport_latency_assumed best_bid_ask n 10,010,123 3,572 45ms 70ms 450ms 24.4s 0 transport_latency_assumed best_bid_ask o 10,019,180 5,055,223 5ms 17ms 116ms 6.5s 0 transport_latency_assumed book h 129,746 5,954 27ms 502ms 9.1h 112.3d 0 book_staleness book i 143,420 22,035 36ms 4.0min 11.7d 112.3d 0 book_staleness book m 127,915 62,543 8ms 45ms 1.1h 112.2d 0 book_staleness book n 129,398 10,418 73ms 9.5s 1.6d 112.3d 0 book_staleness book o 127,045 64,102 8ms 46ms 20.0min 68.4d 0 book_staleness last_trade_price h 61,551 667 23ms 242ms 2.1s 5.3s 0 transport_latency_assumed last_trade_price i 60,512 296 29ms 592ms 4.1s 9.7s 0 transport_latency_assumed last_trade_price m 61,720 30,305 7ms 30ms 185ms 2.4s 0 transport_latency_assumed last_trade_price n 58,846 26 75ms 3.3s 13.9s 24.3s 0 transport_latency_assumed last_trade_price o 61,711 30,616 7ms 32ms 221ms 1.4s 0 transport_latency_assumed market_resolved h 673 4 22ms 25.7s 47.5s 49.9s 0 transport_latency_assumed market_resolved i 673 2 26ms 19.5s 41.3s 43.9s 0 transport_latency_assumed market_resolved m 673 306 7ms 19.5s 41.2s 43.8s 0 transport_latency_assumed market_resolved n 673 6 49ms 33.9s 54.5s 58.4s 0 transport_latency_assumed market_resolved o 673 361 7ms 19.5s 41.2s 43.8s 0 transport_latency_assumed new_market h 841 116 297ms 41.2s 50.3s 1.8min 0 transport_latency_assumed new_market i 841 258 118ms 37.9s 43.6s 1.5min 0 transport_latency_assumed new_market m 841 405 73ms 40.0s 48.2s 1.8min 0 transport_latency_assumed new_market n 841 138 282ms 40.1s 47.1s 1.8min 0 transport_latency_assumed new_market o 841 356 89ms 40.7s 49.5s 1.7min 0 transport_latency_assumed price_change h 109,498,747 1,037,628 19ms 45ms 580ms 1.0min 0 transport_latency_assumed price_change i 109,329,283 620,930 22ms 55ms 1.1s 9.7s 0 transport_latency_assumed price_change m 109,585,017 52,974,884 5ms 19ms 130ms 8.3s 0 transport_latency_assumed price_change n 108,905,497 41,302 46ms 131ms 5.5s 24.4s 0 transport_latency_assumed price_change o 109,602,654 54,969,846 5ms 20ms 136ms 6.7s 0 transport_latency_assumed tick_size_change h 2,648 28 19ms 37ms 188ms 376ms 0 transport_latency_assumed tick_size_change i 2,648 15 22ms 46ms 148ms 501ms 0 transport_latency_assumed tick_size_change m 2,648 1,215 5ms 20ms 106ms 267ms 0 transport_latency_assumed tick_size_change n 2,648 4 45ms 62ms 203ms 432ms 0 transport_latency_assumed tick_size_change o 2,648 1,386 5ms 17ms 141ms 247ms 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/17/2026-10-07T17.parquet sha256sum 2026-10-07T17.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.