Hour audit: 2026-10-03T01
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-03T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T01:00:00.000020028+00:00 · last event 2026-10-03T01:59:59.999542207+00:00
VOLUME 114,586,480 rows · 1,246,341,836 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 114,054,434 · h: 114,041,755 · g: 113,991,172 · m: 113,924,032 · k: 109,631,048 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 432,740 (0.38%) · h: 1,263,616 (1.10%) · g: 15,571 (0.01%) · m: 108,040,164 (94.29%) · k: 4,834,389 (4.22%) (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 114,586,480 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0b8072c669445eaa7309dd6de964a145c9181a62882a64f0a7ebe7d5184d9bc9
the corpus checksum ledger names this file with the same digest
joined 114,593,820 to merged 114,586,480, minus 7,340 (minus 0.0064%)
boundary drops 7,340 · 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-03T03:48:18Z as ghikm
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,883,222 124,725,877 0-41 c272b744f6da506e8c7c09555132238ff7c1fcbc7b35c8d645c0c85646064b7c book 603,202 60,793,426 42-44 d35b101a51ee1703ee817bca2e483debc17f61acbf699a1ceaa15cb009a35b5d last_trade_price 50,396 2,835,680 45-45 4a3edd47504fa7b96f9de6e24148a01421c87910e73616c6346a091e99adfc34 market_resolved 861 120,780 46-46 6455ef90e1ceb793ec89f99e06de37a2b23347141e7dc7ae8074501b433f6923 new_market 985 96,684 47-47 d2983b8a3ff9c9dff4e0da7bf5648f18e849b2077fbbd1b283f5fed10e0c5884 price_change 103,044,570 1,056,345,179 48-441 641a4ccf35b23d9ef655351878a457a301880fb8bf1d9e779e255ad09d810d60 tick_size_change 3,244 115,467 442-442 688fcd73ec3fb8efab3df21b18397e0d9627cc5b6ab366b32ea45babb5cf8563 EVENT MIX count share price_change 103,044,570 89.93% best_bid_ask 10,883,222 9.50% book 603,202 0.53% last_trade_price 50,396 0.04% tick_size_change 3,244 <0.01% new_market 985 <0.01% market_resolved 861 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,883,418 10,883,222 196 594 FULL book 603,242 603,202 40 234,401 FULL last_trade_price 50,396 50,396 0 61 FULL market_resolved 861 861 0 56 FULL new_market 985 985 0 0 FULL price_change 103,051,674 103,044,570 7,104 865 FULL tick_size_change 3,244 3,244 0 26 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,881,762 771 79ms 97ms 324ms 24.3s 0 transport_latency_assumed best_bid_ask h 10,881,377 110,985 17ms 24ms 125ms 57.8s 0 transport_latency_assumed best_bid_ask i 10,881,892 34,467 22ms 29ms 95ms 9.4s 0 transport_latency_assumed best_bid_ask k 10,366,623 392,857 13ms 23ms 121ms 1.3min 0 transport_latency_assumed best_bid_ask m 10,879,122 10,344,142 4ms 10ms 58ms 6.3s 0 transport_latency_assumed book g 108,299 6,798 85ms 1.5s 1.0d 107.6d 0 book_staleness book h 106,424 6,987 21ms 71ms 6.8h 107.6d 0 book_staleness book i 109,285 8,733 25ms 139ms 1.0d 107.6d 0 book_staleness book k 583,783 478,504 26.2min 1.0d 41.5d 126.2d 0 book_staleness book m 110,702 102,180 6ms 135ms 12.8d 118.4d 0 book_staleness last_trade_price g 50,277 69 84ms 287ms 4.7s 14.7s 0 transport_latency_assumed last_trade_price h 50,178 918 19ms 36ms 294ms 49.2s 0 transport_latency_assumed last_trade_price i 50,177 397 24ms 42ms 306ms 7.9s 0 transport_latency_assumed last_trade_price k 48,242 2,976 14ms 33ms 222ms 1.3min 0 transport_latency_assumed last_trade_price m 49,854 46,036 6ms 15ms 129ms 1.2s 0 transport_latency_assumed market_resolved g 735 13 81ms 228ms 43.3s 43.4s 0 transport_latency_assumed market_resolved h 735 2 19ms 73ms 46.9s 46.9s 0 transport_latency_assumed market_resolved i 735 65 24ms 104ms 38.5s 38.5s 0 transport_latency_assumed market_resolved k 748 137 15ms 3.9min 13.6min 15.6min 0 transport_latency_assumed market_resolved m 735 644 5ms 37ms 38.9s 39.0s 0 transport_latency_assumed new_market g 627 50 378ms 40.2s 1.2min 1.7min 0 transport_latency_assumed new_market h 627 139 175ms 35.9s 1.1min 1.3min 0 transport_latency_assumed new_market i 627 168 122ms 35.5s 44.4s 1.7min 0 transport_latency_assumed new_market k 661 112 214ms 37.0s 8.0min 8.1min 0 transport_latency_assumed new_market m 627 516 80ms 38.7s 1.2min 1.7min 0 transport_latency_assumed price_change g 102,946,228 7,870 79ms 102ms 658ms 24.7s 0 transport_latency_assumed price_change h 102,999,170 1,144,556 18ms 26ms 187ms 58.5s 0 transport_latency_assumed price_change i 103,008,474 388,902 23ms 31ms 173ms 11.3s 0 transport_latency_assumed price_change k 98,627,851 3,959,690 13ms 25ms 157ms 1.3min 0 transport_latency_assumed price_change m 102,879,748 97,543,552 5ms 11ms 66ms 7.3s 0 transport_latency_assumed tick_size_change g 3,244 not meas. 79ms 96ms 352ms 1.0s 0 transport_latency_assumed tick_size_change h 3,244 29 17ms 23ms 273ms 6.7s 0 transport_latency_assumed tick_size_change i 3,244 8 22ms 28ms 169ms 330ms 0 transport_latency_assumed tick_size_change k 3,140 113 13ms 22ms 137ms 3.5s 0 transport_latency_assumed tick_size_change m 3,244 3,094 5ms 9ms 55ms 207ms 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-03/01/2026-10-03T01.parquet sha256sum 2026-10-03T01.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.