Hour audit: 2026-09-08T09
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-08T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T09:00:00.000089679+00:00 · last event 2026-09-08T09:59:59.999949421+00:00
VOLUME 92,132,175 rows · 957,714,460 bytes (913.35 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 91,787,204 · h: 91,768,372 · f: 91,728,747 · e: 91,708,673 · g: 91,705,967 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 88,887,371 (96.48%) · h: 2,722,757 (2.96%) · f: 137,176 (0.15%) · e: 262,126 (0.28%) · g: 122,745 (0.13%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 92,132,175 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5c27568e2d5ed5c68872e765f4eff6ddde7e107339612d864742b0e8bc86762c
the corpus checksum ledger names this file with the same digest
joined 92,135,106 to merged 92,132,175, minus 2,931 (minus 0.0032%)
boundary drops 2,931 · 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-08T10:54:42Z 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 8,144,937 89,609,538 0-31 793e47ecfa828102b611315d1e8355e5bb7326251a46522abd045bd4e5947eb9 book 584,341 55,940,092 32-34 b9205d601d2887ff31537aa108e9a3ef31b660b2187dff497f8135bff7737910 last_trade_price 62,833 3,488,186 35-35 d88301b35330ab16341a904860eb207981cd6f3cdeb1cbdbde09a284fd4ad47a market_resolved 767 115,693 36-36 6b389e4663e144f43a9882334b704367c5ad1daddf5c3c769d096b8afd783086 new_market 347 45,125 37-37 fb96fa105028d788b459555a1f8f62e633d181487733474fa4b748c3990275d8 price_change 83,335,806 807,347,897 38-355 850057bcfaf4bd2a954a43231328819acf7d4e80b8897565d23b439611e5cac9 tick_size_change 3,144 114,054 356-356 02cc41be299f90c9587cb6b8f2abce028be130779ec3b50179578175cf19a2a6 EVENT MIX count share price_change 83,335,806 90.45% best_bid_ask 8,144,937 8.84% book 584,341 0.63% last_trade_price 62,833 0.07% tick_size_change 3,144 <0.01% market_resolved 767 <0.01% new_market 347 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,145,119 8,144,937 182 116 FULL book 584,461 584,341 120 153,212 FULL last_trade_price 62,834 62,833 1 1 FULL market_resolved 767 767 0 0 FULL new_market 347 347 0 0 FULL price_change 83,338,434 83,335,806 2,628 135 FULL tick_size_change 3,144 3,144 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,143,703 7,907,767 5ms 9ms 60ms 2.9s 0 transport_latency_assumed best_bid_ask e 8,140,714 13,057 38ms 42ms 122ms 3.1s 0 transport_latency_assumed best_bid_ask f 8,141,704 3,290 48ms 52ms 139ms 4.5s 0 transport_latency_assumed best_bid_ask g 8,139,311 440 80ms 97ms 236ms 9.3s 0 transport_latency_assumed best_bid_ask h 8,143,229 220,383 18ms 21ms 76ms 6.8s 0 transport_latency_assumed book c 260,354 222,874 446ms 9.3h 16.8d 101.5d 0 book_staleness book e 229,838 77,460 105ms 8.8h 16.8d 101.5d 0 book_staleness book f 236,163 79,911 125ms 8.9h 16.8d 101.4d 0 book_staleness book g 296,586 112,223 19.2s 10.6h 16.8d 101.5d 0 book_staleness book h 247,257 91,873 105ms 9.1h 16.8d 101.5d 0 book_staleness last_trade_price c 62,663 60,035 10ms 38ms 186ms 5.0s 0 transport_latency_assumed last_trade_price e 62,513 278 43ms 108ms 1.1s 5.0s 0 transport_latency_assumed last_trade_price f 62,496 107 53ms 108ms 733ms 5.0s 0 transport_latency_assumed last_trade_price g 62,500 36 89ms 166ms 623ms 5.1s 0 transport_latency_assumed last_trade_price h 62,722 2,377 23ms 62ms 564ms 5.0s 0 transport_latency_assumed market_resolved c 723 658 5ms 16ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 723 46 39ms 194ms 59.8s 1.0min 0 transport_latency_assumed market_resolved f 723 not meas. 49ms 202ms 59.9s 1.0min 0 transport_latency_assumed market_resolved g 723 not meas. 83ms 225ms 511ms 786ms 0 transport_latency_assumed market_resolved h 723 63 18ms 54ms 152ms 331ms 0 transport_latency_assumed new_market c 293 201 33ms 317ms 18.3s 20.6s 0 transport_latency_assumed new_market e 293 29 64ms 377ms 24.7s 55.2s 0 transport_latency_assumed new_market f 293 16 72ms 290ms 16.8s 1.1min 0 transport_latency_assumed new_market g 293 8 99ms 542ms 37.2s 1.1min 0 transport_latency_assumed new_market h 293 93 42ms 219ms 16.1s 57.6s 0 transport_latency_assumed price_change c 83,316,324 80,692,732 5ms 10ms 78ms 3.3s 0 transport_latency_assumed price_change e 83,271,448 171,256 38ms 45ms 193ms 3.1s 0 transport_latency_assumed price_change f 83,284,224 53,852 48ms 56ms 208ms 4.5s 0 transport_latency_assumed price_change g 83,203,410 10,038 80ms 100ms 315ms 10.0s 0 transport_latency_assumed price_change h 83,311,004 2,407,928 18ms 23ms 111ms 7.0s 0 transport_latency_assumed tick_size_change c 3,144 3,104 5ms 7ms 27ms 448ms 0 transport_latency_assumed tick_size_change e 3,144 not meas. 38ms 42ms 105ms 117ms 0 transport_latency_assumed tick_size_change f 3,144 not meas. 48ms 51ms 123ms 135ms 0 transport_latency_assumed tick_size_change g 3,144 not meas. 80ms 96ms 221ms 253ms 0 transport_latency_assumed tick_size_change h 3,144 40 18ms 20ms 37ms 86ms 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/09/2026-09-08T09.parquet sha256sum 2026-09-08T09.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.