Hour audit: 2026-10-04T16
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-04T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T16:00:00.000005602+00:00 · last event 2026-10-04T16:59:59.999709188+00:00
VOLUME 110,157,913 rows · 1,247,434,032 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 109,537,642 · h: 109,270,444 · o: 109,113,675 · m: 109,092,846 · n: 109,037,544 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 581,322 (0.53%) · h: 957,761 (0.87%) · o: 57,246,818 (51.97%) · m: 51,270,949 (46.54%) · n: 101,063 (0.09%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 3183704be04a8fda47860723871fcb256ab1dbc5f54d6bc92af5d6253e3c8a3d
the corpus checksum ledger names this file with the same digest
joined 110,161,067 to merged 110,157,913, minus 3,154 (minus 0.0029%)
boundary drops 3,154 · 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-04T18:01:47Z 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 7,991,668 103,534,014 0-30 892407ef0ee5aeb18e1964ef1e34e367e8f764760be95b1f518ac2613e3f2e39 book 149,324 16,067,212 31-31 31bd8071589c47351c95edf60b72f84048270e41a8f800d06ccb990dfc1db358 last_trade_price 63,798 3,751,729 32-32 615bb0296be649fdeee5aaf7382398fab5742c405da6bc8bd1d7c9e20a321972 market_resolved 1,946 316,839 33-33 4636630280998e1d3b23bf622ce8e8a9d72e5b920d2ccc382e2ab5e69fd8c46f new_market 4,853 478,542 34-34 42aa8ccc541ebbaff94b5d61eb87a43f0904dfb279e95228a8060bf7cb9bdfc8 price_change 101,941,784 1,121,861,079 35-423 b2cdf323de24c3a0951b162893c538d496f9d36b90285f9951951a5b33c95b8e tick_size_change 4,540 168,529 424-424 383551197b8a0aa4dd6bcffa43b508080fc065c1deb0cccede226463e1315aae EVENT MIX count share price_change 101,941,784 92.54% best_bid_ask 7,991,668 7.25% book 149,324 0.14% last_trade_price 63,798 0.06% new_market 4,853 <0.01% tick_size_change 4,540 <0.01% market_resolved 1,946 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,991,944 7,991,668 276 1,582 FULL book 149,328 149,324 4 6,061 FULL last_trade_price 63,800 63,798 2 99 FULL market_resolved 1,946 1,946 0 34 FULL new_market 4,853 4,853 0 0 FULL price_change 101,944,656 101,941,784 2,872 2,230 FULL tick_size_change 4,540 4,540 0 38 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 7,908,167 64,496 18ms 35ms 718ms 1.5min 0 transport_latency_assumed best_bid_ask i 7,955,953 40,281 21ms 37ms 338ms 19.3s 0 transport_latency_assumed best_bid_ask m 7,931,873 3,757,126 5ms 16ms 180ms 9.3s 0 transport_latency_assumed best_bid_ask n 7,937,810 6,352 47ms 77ms 499ms 21.1s 0 transport_latency_assumed best_bid_ask o 7,913,214 4,123,413 5ms 17ms 204ms 8.7s 0 transport_latency_assumed book h 137,916 7,536 24ms 516ms 4.0h 109.2d 0 book_staleness book i 135,491 5,098 25ms 344ms 20.1min 109.2d 0 book_staleness book m 133,040 62,279 8ms 58ms 16.4s 127.8d 0 book_staleness book n 134,648 3,844 52ms 712ms 1.0h 109.2d 0 book_staleness book o 135,308 70,567 7ms 65ms 28.2min 109.2d 0 book_staleness last_trade_price h 63,245 574 20ms 84ms 1.4s 1.2min 0 transport_latency_assumed last_trade_price i 63,531 311 24ms 127ms 1.9s 11.6s 0 transport_latency_assumed last_trade_price m 62,741 28,794 6ms 24ms 249ms 7.1s 0 transport_latency_assumed last_trade_price n 62,881 66 52ms 259ms 5.9s 20.4s 0 transport_latency_assumed last_trade_price o 63,374 34,053 6ms 24ms 270ms 2.7s 0 transport_latency_assumed market_resolved h 1,899 41 22ms 267ms 39.6s 2.1min 0 transport_latency_assumed market_resolved i 1,900 24 24ms 218ms 42.8s 2.5min 0 transport_latency_assumed market_resolved m 1,899 889 6ms 56ms 44.3s 2.4min 0 transport_latency_assumed market_resolved n 1,900 6 50ms 360ms 45.5s 2.5min 0 transport_latency_assumed market_resolved o 1,900 986 6ms 98ms 45.2s 2.2min 0 transport_latency_assumed new_market h 3,137 881 18.6s 46.0s 1.1min 1.7min 0 transport_latency_assumed new_market i 3,137 1,221 19.3s 46.1s 1.1min 1.4min 0 transport_latency_assumed new_market m 3,137 1,076 19.6s 44.8s 1.0min 1.4min 0 transport_latency_assumed new_market n 3,137 437 19.1s 45.3s 1.1min 1.7min 0 transport_latency_assumed new_market o 3,137 1,238 19.7s 45.2s 1.0min 1.9min 0 transport_latency_assumed price_change h 101,151,580 884,202 19ms 42ms 840ms 1.6min 0 transport_latency_assumed price_change i 101,373,106 534,376 21ms 47ms 521ms 20.1s 0 transport_latency_assumed price_change m 100,955,644 47,418,724 5ms 17ms 206ms 9.6s 0 transport_latency_assumed price_change n 100,892,672 90,350 48ms 98ms 1.3s 21.2s 0 transport_latency_assumed price_change o 100,992,230 53,014,132 5ms 18ms 227ms 9.5s 0 transport_latency_assumed tick_size_change h 4,500 31 18ms 34ms 489ms 9.0s 0 transport_latency_assumed tick_size_change i 4,524 11 21ms 35ms 415ms 7.1s 0 transport_latency_assumed tick_size_change m 4,512 2,061 5ms 14ms 182ms 330ms 0 transport_latency_assumed tick_size_change n 4,496 8 47ms 72ms 393ms 740ms 0 transport_latency_assumed tick_size_change o 4,512 2,429 5ms 16ms 278ms 1.8s 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/16/2026-10-04T16.parquet sha256sum 2026-10-04T16.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.