Hour audit: 2026-10-07T01
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-07T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T01:00:00.000130167+00:00 · last event 2026-10-07T01:59:59.999913724+00:00
VOLUME 113,884,623 rows · 1,300,066,503 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 113,596,212 · m: 113,575,882 · h: 113,293,797 · n: 113,266,262 · i: 113,210,024 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 55,143,071 (48.42%) · m: 57,643,656 (50.62%) · h: 709,943 (0.62%) · n: 36,124 (0.03%) · i: 351,829 (0.31%) (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 113,884,623 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 960932b69b6f8e2f26e7f8dcb6f0491d2cf53fb619cb32ecce2a28f3a1510710
the corpus checksum ledger names this file with the same digest
joined 113,886,342 to merged 113,884,623, minus 1,719 (minus 0.0015%)
boundary drops 1,719 · 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-07T03:07:12Z 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,988,154 134,617,115 0-41 80ad093f66701fde1a5e3b1ea7793af005946f53fb23b0f6bd6e8c43510a7670 book 638,467 56,954,209 42-44 9d277681faa2d18e8bb150a8b2ba4b53f4aa4f18f5e443a56784ce867c248ef3 last_trade_price 46,494 2,660,954 45-45 da7d345a8cfa6ebd2370b3783e9446877b719216734689213f8a3083d0049aa2 market_resolved 1,125 162,897 46-46 3871a2844a5afa14740cddc0a10766683f4d00e1dc78c2263cc157d78bb25aa6 new_market 489 53,871 47-47 055016c369ab003d4a7d9aa07e0b3d79ec83a3bcd736200bfdcc5327a241a56d price_change 102,205,962 1,104,177,844 48-437 392e5b7fc3ce0da676f3a013813486c0ce4cacd8253d3a7f5d242e4cd975d98a tick_size_change 3,932 143,091 438-438 e48c3a7539b644a96a3c92cf0be6cef062209ce58571a09ae66db8cc148c4005 EVENT MIX count share price_change 102,205,962 89.75% best_bid_ask 10,988,154 9.65% book 638,467 0.56% last_trade_price 46,494 0.04% tick_size_change 3,932 <0.01% market_resolved 1,125 <0.01% new_market 489 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,988,353 10,988,154 199 75 FULL book 638,491 638,467 24 204,276 FULL last_trade_price 46,494 46,494 0 1 FULL market_resolved 1,125 1,125 0 2 FULL new_market 489 489 0 0 FULL price_change 102,207,458 102,205,962 1,496 41 FULL tick_size_change 3,932 3,932 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,986,936 58,641 18ms 25ms 99ms 18.7s 0 transport_latency_assumed best_bid_ask i 10,985,189 30,933 21ms 28ms 93ms 4.0s 0 transport_latency_assumed best_bid_ask m 10,983,470 5,574,513 4ms 11ms 59ms 7.7s 0 transport_latency_assumed best_bid_ask n 10,987,014 1,991 44ms 53ms 130ms 5.7s 0 transport_latency_assumed best_bid_ask o 10,984,683 5,322,076 4ms 11ms 64ms 7.4s 0 transport_latency_assumed book h 101,465 6,340 22ms 173ms 1.4d 111.6d 0 book_staleness book i 100,597 7,434 24ms 471ms 13.7h 111.6d 0 book_staleness book m 425,653 311,851 8.9min 1.3d 45.5d 130.1d 0 book_staleness book n 101,921 8,024 47ms 481ms 1.6d 111.6d 0 book_staleness book o 441,114 304,818 10.1min 1.3d 45.5d 130.1d 0 book_staleness last_trade_price h 46,339 681 19ms 44ms 276ms 11.0s 0 transport_latency_assumed last_trade_price i 46,187 232 23ms 81ms 868ms 1.9s 0 transport_latency_assumed last_trade_price m 46,189 22,562 6ms 18ms 166ms 1.6s 0 transport_latency_assumed last_trade_price n 46,376 60 47ms 112ms 709ms 5.3s 0 transport_latency_assumed last_trade_price o 46,345 22,959 6ms 23ms 322ms 4.8s 0 transport_latency_assumed market_resolved h 1,015 10 20ms 37.9s 56.7s 59.2s 0 transport_latency_assumed market_resolved i 1,015 130 22ms 38.2s 54.2s 54.9s 0 transport_latency_assumed market_resolved m 1,014 475 5ms 38.4s 54.5s 55.1s 0 transport_latency_assumed market_resolved n 1,015 72 45ms 116ms 54.9s 56.0s 0 transport_latency_assumed market_resolved o 1,014 438 5ms 35.6s 55.5s 55.6s 0 transport_latency_assumed new_market h 340 51 55ms 393ms 12.5s 1.5min 0 transport_latency_assumed new_market i 340 62 56ms 144ms 25.3s 1.6min 0 transport_latency_assumed new_market m 340 158 39ms 8.8s 19.9s 20.6s 0 transport_latency_assumed new_market n 340 45 124ms 10.0s 15.3s 1.6min 0 transport_latency_assumed new_market o 340 173 40ms 8.3s 18.5s 1.5min 0 transport_latency_assumed price_change h 102,153,770 644,216 18ms 27ms 152ms 21.8s 0 transport_latency_assumed price_change i 102,072,764 313,036 21ms 31ms 195ms 5.6s 0 transport_latency_assumed price_change m 102,115,284 51,732,118 4ms 12ms 67ms 8.3s 0 transport_latency_assumed price_change n 102,125,664 25,932 44ms 59ms 240ms 7.3s 0 transport_latency_assumed price_change o 102,118,784 49,490,660 4ms 12ms 77ms 11.5s 0 transport_latency_assumed tick_size_change h 3,932 4 18ms 22ms 58ms 95ms 0 transport_latency_assumed tick_size_change i 3,932 2 21ms 26ms 66ms 491ms 0 transport_latency_assumed tick_size_change m 3,932 1,979 4ms 10ms 29ms 152ms 0 transport_latency_assumed tick_size_change n 3,932 not meas. 44ms 51ms 93ms 122ms 0 transport_latency_assumed tick_size_change o 3,932 1,947 4ms 10ms 37ms 93ms 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/01/2026-10-07T01.parquet sha256sum 2026-10-07T01.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.