Hour audit: 2026-10-05T01
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-05T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T01:00:00.000005599+00:00 · last event 2026-10-05T01:59:59.999590671+00:00
VOLUME 108,916,264 rows · 1,211,752,175 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 108,796,540 · n: 108,765,411 · h: 108,632,926 · m: 108,624,594 · i: 108,209,172 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 55,204,061 (50.68%) · n: 94,854 (0.09%) · h: 801,363 (0.74%) · m: 52,447,534 (48.15%) · i: 368,452 (0.34%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 4266902c6e7756a7876f4411f879605767cf16ab9727ff9e4003129be6512426
the corpus checksum ledger names this file with the same digest
joined 108,918,282 to merged 108,916,264, minus 2,018 (minus 0.0019%)
boundary drops 2,018 · 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-05T03:00: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 10,107,928 123,538,464 0-38 10637cee706dab8e952689523b400c7a370c5bbec38d975be9a0743d13a3c212 book 228,090 22,960,368 39-39 239c577e6c33b72ca538ff1be8ed23640b811c2ff1bb7c6a406e8ded8069afa3 last_trade_price 52,126 2,966,431 40-40 eb94ba6521614d01f2755b77b57fd48000b5d15529b7d4ed512344a8715067e2 market_resolved 1,101 169,034 41-41 05208552e50400d4a0ec4d4c0ef98f0cba6454088a856f320d7a2b7ac50276e0 new_market 921 88,787 42-42 f4a66a147fba8fdef893a4f0eae5a2434f5b3e8295d75ed06f5d1fe2313be362 price_change 98,523,622 1,060,694,887 43-418 672a16d9cd73d319645c1446e8ed40e05cfd3205c90e6eb445fcc85315ed57e5 tick_size_change 2,476 93,112 419-419 0aad4eabb8793358da6d5617e261829ef6c86954dedf1c6585acfa2e2282e960 EVENT MIX count share price_change 98,523,622 90.46% best_bid_ask 10,107,928 9.28% book 228,090 0.21% last_trade_price 52,126 0.05% tick_size_change 2,476 <0.01% market_resolved 1,101 <0.01% new_market 921 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,108,050 10,107,928 122 112 FULL book 228,096 228,090 6 49,555 FULL last_trade_price 52,126 52,126 0 0 FULL market_resolved 1,101 1,101 0 8 FULL new_market 921 921 0 0 FULL price_change 98,525,512 98,523,622 1,890 1,205 FULL tick_size_change 2,476 2,476 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,103,405 65,227 17ms 26ms 130ms 46.4s 0 transport_latency_assumed best_bid_ask i 10,088,585 28,191 21ms 30ms 136ms 8.3s 0 transport_latency_assumed best_bid_ask m 10,102,896 4,910,114 5ms 13ms 70ms 12.6s 0 transport_latency_assumed best_bid_ask n 10,106,188 2,464 48ms 65ms 168ms 14.1s 0 transport_latency_assumed best_bid_ask o 10,107,170 5,101,932 5ms 13ms 67ms 5.9s 0 transport_latency_assumed book h 111,272 6,803 21ms 181ms 3.8h 109.6d 0 book_staleness book i 114,813 12,272 24ms 995ms 4.1h 109.6d 0 book_staleness book m 117,965 61,202 7ms 8.3s 22.2h 109.6d 0 book_staleness book n 161,257 54,569 77ms 4.1h 29.5d 128.2d 0 book_staleness book o 146,814 93,244 9ms 3.4h 27.6d 109.7d 0 book_staleness last_trade_price h 51,749 419 19ms 67ms 470ms 9.6s 0 transport_latency_assumed last_trade_price i 50,818 226 23ms 113ms 1.4s 3.3s 0 transport_latency_assumed last_trade_price m 51,718 23,512 6ms 22ms 177ms 1.2s 0 transport_latency_assumed last_trade_price n 52,054 52 53ms 200ms 12.1s 14.1s 0 transport_latency_assumed last_trade_price o 52,054 27,917 6ms 20ms 158ms 1.2s 0 transport_latency_assumed market_resolved h 1,056 5 20ms 21.8s 52.0s 52.1s 0 transport_latency_assumed market_resolved i 1,048 163 23ms 19.7s 49.7s 49.8s 0 transport_latency_assumed market_resolved m 1,056 409 6ms 21.5s 51.1s 51.2s 0 transport_latency_assumed market_resolved n 1,056 19 51ms 29.3s 51.0s 51.0s 0 transport_latency_assumed market_resolved o 1,056 505 6ms 25.7s 55.5s 56.3s 0 transport_latency_assumed new_market h 560 98 75ms 18.1s 48.0s 1.6min 0 transport_latency_assumed new_market i 560 106 77ms 23.0s 53.5s 1.8min 0 transport_latency_assumed new_market m 560 298 49ms 15.6s 41.0s 1.8min 0 transport_latency_assumed new_market n 560 88 142ms 24.9s 56.4s 1.7min 0 transport_latency_assumed new_market o 560 331 49ms 21.6s 1.3min 1.7min 0 transport_latency_assumed price_change h 98,362,408 728,786 18ms 31ms 232ms 47.5s 0 transport_latency_assumed price_change i 97,950,876 327,478 21ms 35ms 395ms 8.3s 0 transport_latency_assumed price_change m 98,347,923 47,450,829 5ms 15ms 90ms 12.6s 0 transport_latency_assumed price_change n 98,441,820 37,658 49ms 77ms 416ms 14.1s 0 transport_latency_assumed price_change o 98,486,410 49,978,871 5ms 15ms 85ms 6.1s 0 transport_latency_assumed tick_size_change h 2,476 25 17ms 27ms 232ms 6.0s 0 transport_latency_assumed tick_size_change i 2,472 16 21ms 31ms 358ms 1.8s 0 transport_latency_assumed tick_size_change m 2,476 1,170 5ms 13ms 241ms 345ms 0 transport_latency_assumed tick_size_change n 2,476 4 48ms 63ms 167ms 433ms 0 transport_latency_assumed tick_size_change o 2,476 1,261 5ms 14ms 115ms 368ms 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/01/2026-10-05T01.parquet sha256sum 2026-10-05T01.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.