Hour audit: 2026-10-04T07
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-04T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T07:00:00.000135324+00:00 · last event 2026-10-04T07:59:59.999589319+00:00
VOLUME 91,543,527 rows · 983,302,531 bytes (937.75 MiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 91,496,425 · h: 91,485,833 · i: 91,482,515 · o: 91,469,348 · n: 91,458,152 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 45,006,144 (49.16%) · h: 210,857 (0.23%) · i: 366,868 (0.40%) · o: 45,918,386 (50.16%) · n: 41,272 (0.05%) (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 91,543,527 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e43bfa081522efd17a72bf67a1416717a8974188dc0168256ef748a13a2a193d
the corpus checksum ledger names this file with the same digest
joined 91,544,396 to merged 91,543,527, minus 869 (minus 0.0009%)
boundary drops 869 · 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-04T09:42:33Z 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 8,873,577 107,981,493 0-33 2483c12d50287f8b6cd16b6045a263a22ae6368fd186358a2057918b7c018102 book 111,087 11,134,561 34-34 c29f7a3c93dfdcb167b225a6fc3ee5172212f6546019408b55c4f6d549eec567 last_trade_price 44,916 2,675,182 35-35 699c3c07dafc2849c97cd7656b469fd628217e1a32701a55fce110e929541bdb market_resolved 901 137,390 36-36 13c6d521bf34c277e0ec4fe5c3b4adb0c074b53ec594e304886714e0c6a9a63c new_market 1,530 142,457 37-37 457898a28efb1ccc4de181d063f6be122d674ef0a6701976734544bfb333a029 price_change 82,508,916 860,088,918 38-352 8c89cbebfbca6bae049ea497bb20cfab9039b1a469aefc135a8a34f0167004b7 tick_size_change 2,600 96,397 353-353 db144a564b313900aa687c328774fa394af03676d7818c80fc88ba3bb7362eb2 EVENT MIX count share price_change 82,508,916 90.13% best_bid_ask 8,873,577 9.69% book 111,087 0.12% last_trade_price 44,916 0.05% tick_size_change 2,600 <0.01% new_market 1,530 <0.01% market_resolved 901 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,873,654 8,873,577 77 109 FULL book 111,087 111,087 0 8,457 FULL last_trade_price 44,916 44,916 0 0 FULL market_resolved 901 901 0 0 FULL new_market 1,530 1,530 0 0 FULL price_change 82,509,708 82,508,916 792 401 FULL tick_size_change 2,600 2,600 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 8,871,900 13,840 18ms 23ms 233ms 53.7s 0 transport_latency_assumed best_bid_ask i 8,872,014 26,256 14ms 22ms 112ms 6.2s 0 transport_latency_assumed best_bid_ask m 8,872,800 4,333,072 4ms 8ms 57ms 6.1s 0 transport_latency_assumed best_bid_ask n 8,871,691 2,435 45ms 53ms 200ms 16.1s 0 transport_latency_assumed best_bid_ask o 8,872,650 4,497,974 4ms 8ms 55ms 5.4s 0 transport_latency_assumed book h 97,945 7,049 22ms 170ms 1.4d 108.8d 0 book_staleness book i 92,530 1,500 17ms 54ms 1.7min 100.9d 0 book_staleness book m 93,366 45,789 6ms 17ms 55.1min 127.4d 0 book_staleness book n 98,699 7,863 49ms 1.4s 2.3d 108.9d 0 book_staleness book o 93,970 48,886 6ms 18ms 2.4h 108.9d 0 book_staleness last_trade_price h 44,861 169 20ms 33ms 450ms 12.4s 0 transport_latency_assumed last_trade_price i 44,780 136 17ms 35ms 557ms 4.7s 0 transport_latency_assumed last_trade_price m 44,848 21,307 5ms 12ms 149ms 3.0s 0 transport_latency_assumed last_trade_price n 44,760 16 48ms 117ms 2.2s 16.1s 0 transport_latency_assumed last_trade_price o 44,789 23,288 5ms 10ms 156ms 2.4s 0 transport_latency_assumed market_resolved h 832 25 20ms 91ms 51.4s 51.5s 0 transport_latency_assumed market_resolved i 832 43 19ms 125ms 51.7s 51.8s 0 transport_latency_assumed market_resolved m 832 386 5ms 14.4s 53.7s 54.2s 0 transport_latency_assumed market_resolved n 832 1 47ms 212ms 46.6s 46.6s 0 transport_latency_assumed market_resolved o 832 446 5ms 14.5s 53.4s 55.9s 0 transport_latency_assumed new_market h 917 198 187ms 25.8s 40.8s 1.6min 0 transport_latency_assumed new_market i 917 151 179ms 25.9s 42.4s 1.6min 0 transport_latency_assumed new_market m 917 436 65ms 25.3s 40.4s 1.7min 0 transport_latency_assumed new_market n 917 265 216ms 29.8s 44.9s 1.7min 0 transport_latency_assumed new_market o 917 480 73ms 26.8s 51.1s 1.7min 0 transport_latency_assumed price_change h 82,466,778 189,576 18ms 25ms 372ms 53.9s 0 transport_latency_assumed price_change i 82,468,842 338,774 14ms 23ms 284ms 8.3s 0 transport_latency_assumed price_change m 82,481,062 40,603,824 4ms 9ms 113ms 7.0s 0 transport_latency_assumed price_change n 82,438,653 30,692 45ms 58ms 492ms 16.2s 0 transport_latency_assumed price_change o 82,453,590 41,346,050 4ms 9ms 111ms 5.4s 0 transport_latency_assumed tick_size_change h 2,600 not meas. 18ms 23ms 70ms 27.2s 0 transport_latency_assumed tick_size_change i 2,600 8 14ms 22ms 43ms 80ms 0 transport_latency_assumed tick_size_change m 2,600 1,330 4ms 8ms 20ms 39ms 0 transport_latency_assumed tick_size_change n 2,600 not meas. 45ms 51ms 94ms 125ms 0 transport_latency_assumed tick_size_change o 2,600 1,262 4ms 8ms 25ms 40ms 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-04/07/2026-10-04T07.parquet sha256sum 2026-10-04T07.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.