Hour audit: 2026-09-08T19
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-09-08T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T19:00:00.000015550+00:00 · last event 2026-09-08T19:59:59.999989983+00:00
VOLUME 119,337,080 rows · 1,354,673,383 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 116,831,429 · e: 116,647,628 · g: 111,355,215 · f: 107,939,793 · c: 91,067,400 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 29,699,560 (24.89%) · e: 3,623,031 (3.04%) · g: 297,775 (0.25%) · f: 1,209,918 (1.01%) · c: 84,506,796 (70.81%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 44f21374f1d19ac373ab3932d8c687db0c518e6d15fa0c89a55a80f7f3f476df
the corpus checksum ledger names this file with the same digest
joined 119,340,838 to merged 119,337,080, minus 3,758 (minus 0.0031%)
boundary drops 3,758 · 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-09-08T21:01:11Z as cefgh
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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,993,746 140,095,228 0-45 d42808496ed27962bd47f900b60e53f716ba070ced3938718981d472e5702d23 book 2,598,110 104,449,155 46-55 534ec39016c6530c5844a7c398189747a9b642e48e7fa056df74d097be33a0e9 last_trade_price 72,804 4,098,746 56-56 311b6d964c64c52577220cfe5ecb1b58c8e7e32b7cd68ac19b83908d9794390e market_resolved 1,988 219,272 57-57 66d7035fa5992ce007c399e89143af23a40d6e70d6167fbfa9253fd5a8707141 new_market 17,498 1,185,493 58-58 14624d2c4b094d3c5c692e543fe55c9617dcfb5eb9e8f698516b393786fc7c31 price_change 104,647,594 1,103,070,373 59-458 2f4c50db70da3b8ef69aff26d93bff14761db91ef181f576a7be2a3c74140a16 tick_size_change 5,340 198,363 459-459 d9eb1292eb640d4c800c0678b45ba991e443fafd94ca745afa0682d540df93c2 EVENT MIX count share price_change 104,647,594 87.69% best_bid_ask 11,993,746 10.05% book 2,598,110 2.18% last_trade_price 72,804 0.06% new_market 17,498 0.01% tick_size_change 5,340 <0.01% market_resolved 1,988 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,994,022 11,993,746 276 5,311 FULL book 2,598,206 2,598,110 96 185,420 FULL last_trade_price 72,806 72,804 2 618 FULL market_resolved 1,988 1,988 0 59 FULL new_market 17,498 17,498 0 140 FULL price_change 104,650,978 104,647,594 3,384 4,745 FULL tick_size_change 5,340 5,340 0 300 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,015,151 8,363,502 6ms 25ms 241ms 9.5s 0 transport_latency_assumed best_bid_ask e 11,984,854 412,316 42ms 106ms 515ms 23.5s 0 transport_latency_assumed best_bid_ask f 10,943,423 112,279 47ms 104ms 461ms 19.6s 0 transport_latency_assumed best_bid_ask g 11,426,851 19,755 89ms 256ms 1.1s 48.3s 0 transport_latency_assumed best_bid_ask h 11,988,397 3,085,894 20ms 66ms 827ms 1.1min 0 transport_latency_assumed book c 2,412,579 2,313,835 24.4min 1.1d 31.2d 101.9d 0 book_staleness book e 164,665 9,588 77ms 3.0s 58.2min 83.3d 0 book_staleness book f 918,038 120,039 9.3min 20.6h 28.0d 101.9d 0 book_staleness book g 557,530 110,080 4.3min 18.8h 27.0d 101.9d 0 book_staleness book h 164,527 44,568 31ms 472ms 46.2s 39.4d 0 book_staleness last_trade_price c 54,469 50,393 12ms 67ms 363ms 5.0s 0 transport_latency_assumed last_trade_price e 71,705 1,686 66ms 1.4s 12.3s 23.4s 0 transport_latency_assumed last_trade_price f 65,683 663 68ms 1.1s 11.7s 19.6s 0 transport_latency_assumed last_trade_price g 65,578 230 131ms 2.1s 19.6s 39.4s 0 transport_latency_assumed last_trade_price h 72,588 19,832 28ms 168ms 1.4s 45.2s 0 transport_latency_assumed market_resolved c 1,692 1,546 13ms 10.5min 19.6min 19.8min 0 transport_latency_assumed market_resolved e 1,322 28 43ms 224ms 758ms 2.4s 0 transport_latency_assumed market_resolved f 1,403 90 50ms 2.3min 9.6min 13.1min 0 transport_latency_assumed market_resolved g 1,299 5 92ms 422ms 2.3s 4.4min 0 transport_latency_assumed market_resolved h 1,322 319 22ms 124ms 720ms 9.2s 0 transport_latency_assumed new_market c 14,867 10,551 5.6min 17.1min 20.4min 22.2min 0 transport_latency_assumed new_market e 6,876 1,411 190ms 1.7min 6.4min 9.0min 0 transport_latency_assumed new_market f 8,743 1,737 259ms 9.0min 11.7min 16.4min 0 transport_latency_assumed new_market g 6,794 856 298ms 1.6min 6.3min 9.6min 0 transport_latency_assumed new_market h 6,876 2,943 132ms 1.8min 6.3min 5.0d 0 transport_latency_assumed price_change c 79,564,442 73,763,158 6ms 28ms 251ms 20.6s 0 transport_latency_assumed price_change e 104,412,866 3,197,870 42ms 149ms 2.8s 23.6s 0 transport_latency_assumed price_change f 95,997,683 975,076 47ms 140ms 1.6s 19.6s 0 transport_latency_assumed price_change g 99,292,023 166,840 90ms 329ms 5.3s 48.3s 0 transport_latency_assumed price_change h 104,592,379 26,544,650 20ms 73ms 811ms 1.1min 0 transport_latency_assumed tick_size_change c 4,200 3,811 6ms 25ms 239ms 446ms 0 transport_latency_assumed tick_size_change e 5,340 132 41ms 102ms 337ms 3.2s 0 transport_latency_assumed tick_size_change f 4,820 34 46ms 94ms 345ms 11.6s 0 transport_latency_assumed tick_size_change g 5,140 9 87ms 215ms 715ms 8.0s 0 transport_latency_assumed tick_size_change h 5,340 1,354 20ms 47ms 335ms 2.2s 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-09-08/19/2026-09-08T19.parquet sha256sum 2026-09-08T19.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.