Hour audit: 2026-10-07T12
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-07T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T12:00:00.000061218+00:00 · last event 2026-10-07T12:59:59.999980732+00:00
VOLUME 128,848,737 rows · 1,500,162,487 bytes (1.40 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 128,487,314 · m: 128,469,165 · o: 128,439,084 · i: 128,279,511 · n: 128,013,210 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,185,541 (0.92%) · m: 65,555,107 (50.88%) · o: 61,282,493 (47.56%) · i: 689,414 (0.54%) · n: 136,182 (0.11%) (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 128,848,737 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 eed301bbd987ced4ef9ab30992d0c807dd050395a717676b6fc2b002bf634550
the corpus checksum ledger names this file with the same digest
joined 128,849,978 to merged 128,848,737, minus 1,241 (minus 0.0010%)
boundary drops 1,241 · 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-07T15:26:44Z 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,520,624 148,960,112 0-43 aedde0668bd066be20c5d1f65f51337f5d8e7809bde26b80f6e0f5310bea57fc book 578,020 55,950,487 44-46 ea1b5b9cd98ea50dce3be23af175876a3fa3af403e758e7f053152b36b9dd2c3 last_trade_price 54,234 3,121,048 47-47 40ba1bc3bc68c8461e4ee53a1cffa88d1b4f3cdd44ea6992bc844312c11c44f5 market_resolved 803 122,694 48-48 abcaeb63d9874839dd42e684291f4a316b3a8bf9e98919f0976213368e13ff9e new_market 940 98,496 49-49 9f2a57df2fda75a71f986a7faaa500290bcaef306bb7a794b4b60ca8a43dddb2 price_change 116,689,096 1,290,258,104 50-495 a19d50145a1cbf495e248e520553c8f6e7a6ebd5e30cc71943bef2c91ca8980a tick_size_change 5,020 183,165 496-496 55ca9e958eb4a8009181062523a1573b3daa36492de6e26fcc8c538cf858ee92 EVENT MIX count share price_change 116,689,096 90.56% best_bid_ask 11,520,624 8.94% book 578,020 0.45% last_trade_price 54,234 0.04% tick_size_change 5,020 <0.01% new_market 940 <0.01% market_resolved 803 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,520,704 11,520,624 80 64 FULL book 578,184 578,020 164 180,989 FULL last_trade_price 54,235 54,234 1 2 FULL market_resolved 803 803 0 0 FULL new_market 940 940 0 0 FULL price_change 116,690,092 116,689,096 996 52 FULL tick_size_change 5,020 5,020 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,517,962 84,932 19ms 31ms 240ms 30.7s 0 transport_latency_assumed best_bid_ask i 11,518,426 57,794 21ms 34ms 167ms 6.4s 0 transport_latency_assumed best_bid_ask m 11,519,440 5,928,088 5ms 15ms 106ms 5.7s 0 transport_latency_assumed best_bid_ask n 11,513,948 3,334 44ms 64ms 349ms 18.6s 0 transport_latency_assumed best_bid_ask o 11,519,413 5,446,476 5ms 16ms 107ms 6.0s 0 transport_latency_assumed book h 292,836 149,411 1.1min 1.2d 45.9d 130.6d 0 book_staleness book i 117,560 8,101 27ms 1.4s 1.0d 112.1d 0 book_staleness book m 242,664 164,492 16.6s 22.1h 41.7d 130.6d 0 book_staleness book n 226,076 97,134 9.9s 20.6h 41.8d 130.6d 0 book_staleness book o 234,898 158,882 9.5s 20.8h 42.7d 130.6d 0 book_staleness last_trade_price h 54,023 437 21ms 122ms 822ms 18.0s 0 transport_latency_assumed last_trade_price i 53,942 276 26ms 343ms 3.0s 6.4s 0 transport_latency_assumed last_trade_price m 54,164 26,960 7ms 27ms 184ms 2.1s 0 transport_latency_assumed last_trade_price n 52,917 25 57ms 2.6s 10.6s 18.6s 0 transport_latency_assumed last_trade_price o 54,100 26,536 7ms 27ms 194ms 3.3s 0 transport_latency_assumed market_resolved h 743 8 21ms 14.6s 48.0s 53.7s 0 transport_latency_assumed market_resolved i 743 66 25ms 14.6s 47.8s 52.7s 0 transport_latency_assumed market_resolved m 743 344 7ms 14.9s 48.0s 53.0s 0 transport_latency_assumed market_resolved n 743 60 46ms 141ms 54.2s 54.3s 0 transport_latency_assumed market_resolved o 743 325 7ms 17.0s 50.4s 55.1s 0 transport_latency_assumed new_market h 620 62 150ms 11.3s 21.9s 1.7min 0 transport_latency_assumed new_market i 620 181 102ms 12.2s 23.7s 1.5min 0 transport_latency_assumed new_market m 620 365 61ms 21.1s 29.3s 1.7min 0 transport_latency_assumed new_market n 620 129 114ms 17.4s 51.2s 1.7min 0 transport_latency_assumed new_market o 620 203 81ms 17.3s 30.7s 1.7min 0 transport_latency_assumed price_change h 116,616,110 950,672 19ms 38ms 410ms 31.4s 0 transport_latency_assumed price_change i 116,583,200 622,960 22ms 45ms 646ms 6.4s 0 transport_latency_assumed price_change m 116,646,514 59,432,322 5ms 17ms 122ms 5.8s 0 transport_latency_assumed price_change n 116,213,886 35,500 45ms 99ms 3.5s 18.7s 0 transport_latency_assumed price_change o 116,624,290 55,647,642 5ms 18ms 123ms 6.0s 0 transport_latency_assumed tick_size_change h 5,020 19 18ms 27ms 127ms 1.2s 0 transport_latency_assumed tick_size_change i 5,020 36 21ms 30ms 118ms 381ms 0 transport_latency_assumed tick_size_change m 5,020 2,536 5ms 11ms 62ms 176ms 0 transport_latency_assumed tick_size_change n 5,020 not meas. 43ms 53ms 185ms 3.2s 0 transport_latency_assumed tick_size_change o 5,020 2,429 5ms 12ms 67ms 270ms 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/12/2026-10-07T12.parquet sha256sum 2026-10-07T12.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.