Hour audit: 2026-10-05T03
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-05T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T03:00:00.000015106+00:00 · last event 2026-10-05T03:59:59.999905892+00:00
VOLUME 103,747,826 rows · 1,118,827,347 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured n: 103,656,590 · o: 103,611,869 · m: 103,518,714 · i: 103,515,665 · h: 103,478,867 (each machine's own feed; these overlap and do not sum to the file)
supplied n: 57,857 (0.06%) · o: 49,258,785 (47.48%) · m: 53,484,307 (51.55%) · i: 280,249 (0.27%) · h: 666,628 (0.64%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 103,747,826 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 150b897f26ee5045da0a7eb77e497a1b82916d2895376409a615aa000ccdcd5d
the corpus checksum ledger names this file with the same digest
joined 103,750,226 to merged 103,747,826, minus 2,400 (minus 0.0023%)
boundary drops 2,400 · 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-05T04:59:45Z 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 9,512,140 114,481,385 0-36 2a47284f6f47dc4561d06fd57c2389ee5fb8a63d25a7b825a131fdf0cb7afb53 book 164,279 17,295,494 37-37 570710bc5c135c906a6e848c92957c40ac039629172d7607b52852e9b601a9cb last_trade_price 42,811 2,462,791 38-38 76487f9f9b1606fb391855867c4abc01f4ba82f043bef3839c49967e7e6b41cd market_resolved 1,570 252,069 39-39 a00c9593a43e2fdb24a866bac3da224869895408d2f8ec540f5bdb6f393f3c55 new_market 600 63,124 40-40 602b4344c6d49b1a6f927b5e8a9767598fe1dc1dacdbf6cea2810e2cb1a24137 price_change 94,022,746 982,954,428 41-399 219a634493028b8436736f33459781a1e95a1d181d58427567c845891971bc31 tick_size_change 3,680 132,902 400-400 092b38fe9b013a2a3623137751212b5007896873f25755cb2ca2f1dc118396c9 EVENT MIX count share price_change 94,022,746 90.63% best_bid_ask 9,512,140 9.17% book 164,279 0.16% last_trade_price 42,811 0.04% tick_size_change 3,680 <0.01% market_resolved 1,570 <0.01% new_market 600 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,512,416 9,512,140 276 60 FULL book 164,279 164,279 0 34,061 FULL last_trade_price 42,811 42,811 0 0 FULL market_resolved 1,570 1,570 0 0 FULL new_market 600 600 0 0 FULL price_change 94,024,870 94,022,746 2,124 1,161 FULL tick_size_change 3,680 3,680 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,507,986 50,603 18ms 24ms 92ms 11.5s 0 transport_latency_assumed best_bid_ask i 9,510,295 19,001 22ms 29ms 87ms 7.3s 0 transport_latency_assumed best_bid_ask m 9,509,466 4,916,143 5ms 11ms 57ms 6.2s 0 transport_latency_assumed best_bid_ask n 9,511,102 1,563 48ms 62ms 132ms 10.0s 0 transport_latency_assumed best_bid_ask o 9,511,384 4,524,830 5ms 11ms 59ms 3.4s 0 transport_latency_assumed book h 90,858 5,269 21ms 87ms 3.5h 109.6d 0 book_staleness book i 90,272 4,536 25ms 84ms 3.7h 109.7d 0 book_staleness book m 95,998 55,193 7ms 2.1s 21.0h 109.7d 0 book_staleness book n 117,660 30,375 55ms 3.7h 27.7d 128.2d 0 book_staleness book o 117,268 68,906 8ms 3.7h 27.7d 109.7d 0 book_staleness last_trade_price h 42,549 529 19ms 37ms 252ms 5.1s 0 transport_latency_assumed last_trade_price i 42,677 249 24ms 45ms 329ms 7.2s 0 transport_latency_assumed last_trade_price m 42,511 23,248 6ms 17ms 144ms 3.2s 0 transport_latency_assumed last_trade_price n 42,708 26 50ms 103ms 479ms 3.4s 0 transport_latency_assumed last_trade_price o 42,603 18,759 6ms 19ms 154ms 1.2s 0 transport_latency_assumed market_resolved h 1,542 8 19ms 46ms 46.6s 56.1s 0 transport_latency_assumed market_resolved i 1,542 104 24ms 52ms 51.7s 55.1s 0 transport_latency_assumed market_resolved m 1,542 732 6ms 22ms 53.6s 57.0s 0 transport_latency_assumed market_resolved n 1,542 3 49ms 113ms 52.6s 56.2s 0 transport_latency_assumed market_resolved o 1,542 723 6ms 16ms 47.4s 52.5s 0 transport_latency_assumed new_market h 402 64 68ms 12.2s 59.5s 1.6min 0 transport_latency_assumed new_market i 402 55 60ms 25.4s 56.8s 1.5min 0 transport_latency_assumed new_market m 402 188 36ms 35.7s 58.1s 1.7min 0 transport_latency_assumed new_market n 402 30 104ms 12.2s 56.7s 1.5min 0 transport_latency_assumed new_market o 402 263 34ms 40.1s 1.5min 1.7min 0 transport_latency_assumed price_change h 93,831,850 610,142 18ms 27ms 138ms 16.1s 0 transport_latency_assumed price_change i 93,866,797 256,304 23ms 31ms 129ms 7.3s 0 transport_latency_assumed price_change m 93,865,115 48,486,870 5ms 12ms 67ms 6.3s 0 transport_latency_assumed price_change n 93,979,496 25,860 48ms 70ms 242ms 10.4s 0 transport_latency_assumed price_change o 93,934,990 44,643,570 5ms 12ms 72ms 4.1s 0 transport_latency_assumed tick_size_change h 3,680 13 18ms 24ms 62ms 356ms 0 transport_latency_assumed tick_size_change i 3,680 not meas. 23ms 31ms 61ms 150ms 0 transport_latency_assumed tick_size_change m 3,680 1,933 5ms 11ms 45ms 332ms 0 transport_latency_assumed tick_size_change n 3,680 not meas. 47ms 60ms 105ms 170ms 0 transport_latency_assumed tick_size_change o 3,680 1,734 5ms 10ms 36ms 69ms 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-05/03/2026-10-05T03.parquet sha256sum 2026-10-05T03.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.