Hour audit: 2026-10-07T06
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-07T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T06:00:00.000073951+00:00 · last event 2026-10-07T06:59:59.999890027+00:00
VOLUME 99,161,331 rows · 1,136,565,822 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 98,926,336 · o: 98,500,124 · m: 98,482,996 · h: 98,458,016 · n: 98,313,813 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 890,775 (0.90%) · o: 47,829,222 (48.23%) · m: 49,762,510 (50.18%) · h: 593,507 (0.60%) · n: 85,317 (0.09%) (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 99,161,331 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 832baabf7e7e50e9c8370fb2275c7f45f083a6eeaa2a5b57b4a553e9ef270374
the corpus checksum ledger names this file with the same digest
joined 99,162,213 to merged 99,161,331, minus 882 (minus 0.0009%)
boundary drops 882 · 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-07T07:58:42Z 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,114,868 125,211,393 0-38 cc1e93cba8d857bdb4890bd8f732056de42437e4c1974991f87aa1b8e39318a5 book 770,337 69,749,411 39-41 10923e29d5ad6e98d7830b9d9881d17f97dcfe5176f8b0534466b5866ff11cb2 last_trade_price 45,081 2,592,534 42-42 85c09c93b4a1e7ec30a53544de0765ac9925d775d63ac30e83557946117bd000 market_resolved 879 129,121 43-43 c29320e35cafb04345e4179d1e53a2d11d66784991ab05aa46168d330173640b new_market 894 84,415 44-44 6ca5ee60b5080a22d59726534ad40163e24e5f6997ad7508f250c2b9e07ec02c price_change 88,227,352 937,595,578 45-381 92bbcd08a0be7c8024a283a0e4f45cf4b38f7324cb0ba9d08c9af7aba240255e tick_size_change 1,920 71,714 382-382 17b1edf5d4f8c269bbd5b7df5c66d71b4c3f272c7eee525ab6f8cde9eeaf7cb5 EVENT MIX count share price_change 88,227,352 88.97% best_bid_ask 10,114,868 10.20% book 770,337 0.78% last_trade_price 45,081 0.05% tick_size_change 1,920 <0.01% new_market 894 <0.01% market_resolved 879 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,114,978 10,114,868 110 68 FULL book 770,351 770,337 14 249,468 FULL last_trade_price 45,081 45,081 0 0 FULL market_resolved 879 879 0 6 FULL new_market 894 894 0 0 FULL price_change 88,228,110 88,227,352 758 100 FULL tick_size_change 1,920 1,920 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,112,472 47,108 18ms 27ms 232ms 1.2min 0 transport_latency_assumed best_bid_ask i 10,109,785 33,335 21ms 28ms 120ms 11.7s 0 transport_latency_assumed best_bid_ask m 10,113,131 5,018,228 4ms 11ms 76ms 5.8s 0 transport_latency_assumed best_bid_ask n 10,111,730 2,439 43ms 54ms 215ms 18.5s 0 transport_latency_assumed best_bid_ask o 10,113,532 5,013,758 4ms 11ms 78ms 11.1s 0 transport_latency_assumed book h 131,409 31,949 31ms 8.1h 29.8d 130.3d 0 book_staleness book i 670,577 498,927 21.3min 1.8d 45.7d 130.4d 0 book_staleness book m 160,672 100,854 18ms 13.6h 31.7d 130.3d 0 book_staleness book n 145,111 44,470 122ms 11.7h 31.7d 130.3d 0 book_staleness book o 153,411 94,137 14ms 12.6h 31.7d 130.3d 0 book_staleness last_trade_price h 44,932 298 20ms 83ms 1.0s 31.8s 0 transport_latency_assumed last_trade_price i 44,703 172 23ms 127ms 5.3s 11.8s 0 transport_latency_assumed last_trade_price m 44,846 22,682 6ms 19ms 185ms 1.8s 0 transport_latency_assumed last_trade_price n 44,411 40 47ms 321ms 8.3s 18.6s 0 transport_latency_assumed last_trade_price o 44,886 21,889 6ms 21ms 224ms 2.7s 0 transport_latency_assumed market_resolved h 801 5 22ms 33.6s 47.2s 49.7s 0 transport_latency_assumed market_resolved i 801 123 24ms 30.0s 45.0s 46.2s 0 transport_latency_assumed market_resolved m 801 368 6ms 31.1s 46.4s 47.6s 0 transport_latency_assumed market_resolved n 795 79 45ms 257ms 51.4s 54.9s 0 transport_latency_assumed market_resolved o 801 304 6ms 37.7s 53.4s 54.6s 0 transport_latency_assumed new_market h 538 109 228ms 23.9s 33.5s 1.7min 0 transport_latency_assumed new_market i 538 100 130ms 22.7s 48.6s 1.5min 0 transport_latency_assumed new_market m 538 360 72ms 21.5s 33.5s 1.2min 0 transport_latency_assumed new_market n 538 101 254ms 31.6s 35.3s 1.9min 0 transport_latency_assumed new_market o 538 224 88ms 32.9s 48.3s 1.5min 0 transport_latency_assumed price_change h 88,165,944 514,002 18ms 34ms 394ms 1.2min 0 transport_latency_assumed price_change i 88,098,012 358,114 21ms 35ms 458ms 11.8s 0 transport_latency_assumed price_change m 88,161,088 44,619,008 4ms 12ms 114ms 7.7s 0 transport_latency_assumed price_change n 88,009,308 38,188 43ms 70ms 1.5s 18.9s 0 transport_latency_assumed price_change o 88,185,036 42,698,040 5ms 12ms 121ms 11.1s 0 transport_latency_assumed tick_size_change h 1,920 36 18ms 29ms 228ms 528ms 0 transport_latency_assumed tick_size_change i 1,920 4 21ms 28ms 76ms 631ms 0 transport_latency_assumed tick_size_change m 1,920 1,010 4ms 11ms 94ms 408ms 0 transport_latency_assumed tick_size_change n 1,920 not meas. 43ms 57ms 177ms 564ms 0 transport_latency_assumed tick_size_change o 1,920 870 5ms 12ms 83ms 173ms 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/06/2026-10-07T06.parquet sha256sum 2026-10-07T06.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.