Hour audit: 2026-10-08T08
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-08T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T08:00:00.000074245+00:00 · last event 2026-10-08T08:59:59.999901894+00:00
VOLUME 106,121,485 rows · 1,170,378,858 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 105,949,231 · o: 105,948,429 · m: 105,937,920 · i: 105,855,165 · n: 104,459,641 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 856,597 (0.81%) · o: 51,203,069 (48.25%) · m: 53,423,569 (50.34%) · i: 563,454 (0.53%) · n: 74,796 (0.07%) (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 106,121,485 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9505701ea4e4e23bf31fae71d77cd80b9f247cadaf337213d75f5502b30a4b97
the corpus checksum ledger names this file with the same digest
joined 106,122,513 to merged 106,121,485, minus 1,028 (minus 0.0010%)
boundary drops 1,028 · 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-08T10:40:24Z 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 11,132,352 137,317,661 0-42 5da408a3bbc78bc9d8383d1e1e6bde4f4ac9216e7cacba321e110d11dfd9dc8a book 200,823 21,044,349 43-43 4c3e8f54150614a86cdb60e53db26c9bbd3f73a3e96fda2c0e3c67caa90c1dff last_trade_price 47,300 2,773,869 44-44 804b72103a46c76c51089b14b47e24ed909a935a3e178f96dbc736489648aa66 market_resolved 475 73,472 45-45 1bb1058a602aa4950ff0a6090bebc1ca7e5d612dd378ef840f4536291fe08ab3 new_market 1,081 106,012 46-46 cc106ad0f8bdbc7b5a011d5a3ab9b3675ac3f887256ef3bf05c59b538d967567 price_change 94,737,454 1,007,777,664 47-408 16e5262d078d5c5c3d48df2ea23ce14dd53755b85191e7fcb34b904dce695394 tick_size_change 2,000 74,830 409-409 d199100ee16f41028b10a350f90af658f6ba101a8954fd1afb37ada936836fd6 EVENT MIX count share price_change 94,737,454 89.27% best_bid_ask 11,132,352 10.49% book 200,823 0.19% last_trade_price 47,300 0.04% tick_size_change 2,000 <0.01% new_market 1,081 <0.01% market_resolved 475 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,132,434 11,132,352 82 145 FULL book 200,915 200,823 92 42,953 FULL last_trade_price 47,302 47,300 2 2 FULL market_resolved 475 475 0 9 FULL new_market 1,081 1,081 0 0 FULL price_change 94,738,306 94,737,454 852 44 FULL tick_size_change 2,000 2,000 0 9 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,129,984 80,084 18ms 30ms 201ms 31.7s 0 transport_latency_assumed best_bid_ask i 11,127,678 54,997 21ms 31ms 149ms 4.1s 0 transport_latency_assumed best_bid_ask m 11,130,046 5,529,530 5ms 14ms 93ms 4.4s 0 transport_latency_assumed best_bid_ask n 11,087,353 2,973 43ms 61ms 303ms 21.9s 0 transport_latency_assumed best_bid_ask o 11,130,184 5,464,768 5ms 14ms 99ms 5.8s 0 transport_latency_assumed book h 115,853 20,695 25ms 13.1min 18.8d 112.9d 0 book_staleness book i 107,958 13,071 25ms 43.5s 3.8d 112.9d 0 book_staleness book m 115,680 67,459 8ms 13.4min 18.8d 112.9d 0 book_staleness book n 123,495 33,414 107ms 1.3h 27.9d 131.4d 0 book_staleness book o 115,722 66,184 8ms 12.7min 18.8d 112.9d 0 book_staleness last_trade_price h 47,145 391 21ms 148ms 684ms 11.9s 0 transport_latency_assumed last_trade_price i 46,844 220 24ms 254ms 1.3s 4.1s 0 transport_latency_assumed last_trade_price m 47,087 23,963 6ms 27ms 191ms 1.5s 0 transport_latency_assumed last_trade_price n 43,865 62 50ms 1.8s 8.9s 21.9s 0 transport_latency_assumed last_trade_price o 47,074 22,664 6ms 27ms 192ms 1.5s 0 transport_latency_assumed market_resolved h 453 20 21ms 74ms 29.1s 56.6s 0 transport_latency_assumed market_resolved i 453 37 24ms 127ms 47.4s 50.2s 0 transport_latency_assumed market_resolved m 453 210 6ms 32ms 48.0s 50.4s 0 transport_latency_assumed market_resolved n 444 3 47ms 202ms 36.6s 41.0s 0 transport_latency_assumed market_resolved o 453 205 6ms 26ms 48.1s 50.7s 0 transport_latency_assumed new_market h 680 148 147ms 14.8s 37.5s 1.3min 0 transport_latency_assumed new_market i 680 174 95ms 24.4s 35.1s 59.7s 0 transport_latency_assumed new_market m 680 416 45ms 20.0s 36.6s 1.6min 0 transport_latency_assumed new_market n 680 82 174ms 17.1s 37.2s 1.9min 0 transport_latency_assumed new_market o 680 261 65ms 14.1s 40.3s 1.7min 0 transport_latency_assumed price_change h 94,653,116 755,258 18ms 38ms 378ms 31.7s 0 transport_latency_assumed price_change i 94,569,552 494,952 21ms 43ms 591ms 4.2s 0 transport_latency_assumed price_change m 94,641,974 47,800,976 5ms 17ms 115ms 4.6s 0 transport_latency_assumed price_change n 93,201,840 38,262 44ms 92ms 3.8s 21.9s 0 transport_latency_assumed price_change o 94,652,316 45,648,006 5ms 17ms 121ms 6.7s 0 transport_latency_assumed tick_size_change h 2,000 1 18ms 27ms 154ms 2.7s 0 transport_latency_assumed tick_size_change i 2,000 3 21ms 34ms 69ms 536ms 0 transport_latency_assumed tick_size_change m 2,000 1,015 5ms 12ms 40ms 132ms 0 transport_latency_assumed tick_size_change n 1,964 not meas. 44ms 56ms 1.6s 1.7s 0 transport_latency_assumed tick_size_change o 2,000 981 5ms 11ms 30ms 51ms 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/08/2026-10-08T08.parquet sha256sum 2026-10-08T08.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.