Hour audit: 2026-09-15T07
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-15T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T07:00:00.000438716+00:00 · last event 2026-09-15T07:59:59.999493073+00:00
VOLUME 103,988,584 rows · 1,071,528,458 bytes (1021.89 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 103,498,675 · h: 103,439,626 · e: 103,437,894 · f: 103,417,193 · c: 99,691,313 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 43,587 (0.04%) · h: 7,492,236 (7.20%) · e: 511,013 (0.49%) · f: 132,945 (0.13%) · c: 95,808,803 (92.13%) (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 103,988,584 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 48c3137c738faed51add59e90e57f74229dcfa083bc658d4e2f2cbde500037a0
the corpus checksum ledger names this file with the same digest
joined 103,991,253 to merged 103,988,584, minus 2,669 (minus 0.0026%)
boundary drops 2,669 · 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-15T08:57:45Z 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,236,544 124,239,367 0-42 4cbdd2d9b5ca2d2250ea6e405aead9864e7db58fe91ef16857863ae1c835efbb book 485,628 52,550,656 43-44 809c727405c7228dd4671709ca23bfd7efb3a91759bdf09f64ef2e691ce0ca5f last_trade_price 51,413 2,910,542 45-45 1128ffe64461e3543fd7e8313f26e15ce814edd24ba674bdb9b6675de6315753 market_resolved 855 135,891 46-46 f0775ecfd8f8dc4322c87f299cf68d6fdd5837936f65f19680002b723f2551fd new_market 986 105,981 47-47 94637131eb5d0051b804e028366dd05b3e85d2cf2978a18feb79e5c1bf7eb2dc price_change 92,210,958 890,321,224 48-399 2da4354518481c92a12c370263cd653f1e5d8d383495102c2a21b1567df56e3a tick_size_change 2,200 81,682 400-400 49bbff08ae076df9d16c5cc0880538568d69d9c8252194d65256ec746abbdb41 EVENT MIX count share price_change 92,210,958 88.67% best_bid_ask 11,236,544 10.81% book 485,628 0.47% last_trade_price 51,413 0.05% tick_size_change 2,200 <0.01% new_market 986 <0.01% market_resolved 855 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,236,850 11,236,544 306 695 FULL book 485,672 485,628 44 169,738 FULL last_trade_price 51,413 51,413 0 106 FULL market_resolved 860 855 5 57 FULL new_market 986 986 0 0 FULL price_change 92,213,272 92,210,958 2,314 473 FULL tick_size_change 2,200 2,200 0 74 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,790,892 10,384,817 5ms 10ms 79ms 4.2s 0 transport_latency_assumed best_bid_ask e 11,234,624 49,578 41ms 46ms 149ms 4.1s 0 transport_latency_assumed best_bid_ask f 11,234,341 11,256 50ms 56ms 168ms 4.6s 0 transport_latency_assumed best_bid_ask g 11,232,124 1,116 84ms 132ms 399ms 19.9s 0 transport_latency_assumed best_bid_ask h 11,233,749 789,777 17ms 23ms 108ms 40.5s 0 transport_latency_assumed book c 449,563 435,143 3.2min 1.4d 34.5d 108.4d 0 book_staleness book e 110,950 4,401 44ms 210ms 1.1h 89.7d 0 book_staleness book f 113,457 5,490 52ms 402ms 8.9h 89.9d 0 book_staleness book g 144,154 26,642 119ms 34.0min 9.7d 108.4d 0 book_staleness book h 110,722 13,952 21ms 90ms 1.2h 89.8d 0 book_staleness last_trade_price c 48,046 45,811 10ms 45ms 215ms 4.9s 0 transport_latency_assumed last_trade_price e 51,154 535 49ms 144ms 1.0s 5.0s 0 transport_latency_assumed last_trade_price f 51,091 153 57ms 161ms 1.5s 5.0s 0 transport_latency_assumed last_trade_price g 50,923 23 102ms 527ms 7.9s 15.0s 0 transport_latency_assumed last_trade_price h 50,951 4,891 23ms 75ms 339ms 7.8s 0 transport_latency_assumed market_resolved c 755 722 5ms 12ms 5.6min 5.9min 0 transport_latency_assumed market_resolved e 800 3 43ms 122ms 536ms 59.8s 0 transport_latency_assumed market_resolved f 800 1 51ms 133ms 380ms 585ms 0 transport_latency_assumed market_resolved g 802 1 97ms 255ms 681ms 1.1s 0 transport_latency_assumed market_resolved h 798 128 20ms 61ms 421ms 1.0min 0 transport_latency_assumed new_market c 680 423 85ms 13.8s 37.4s 1.3min 0 transport_latency_assumed new_market e 680 111 190ms 19.1s 41.7s 1.1min 0 transport_latency_assumed new_market f 680 89 180ms 14.7s 37.9s 2.5min 0 transport_latency_assumed new_market g 680 55 327ms 16.3s 37.7s 2.3min 0 transport_latency_assumed new_market h 680 308 112ms 441ms 30.1s 1.4min 0 transport_latency_assumed price_change c 88,399,473 84,940,073 5ms 11ms 90ms 4.5s 0 transport_latency_assumed price_change e 92,037,486 456,383 42ms 51ms 259ms 6.5s 0 transport_latency_assumed price_change f 92,014,624 115,952 50ms 62ms 281ms 6.4s 0 transport_latency_assumed price_change g 92,067,792 15,750 84ms 148ms 856ms 20.2s 0 transport_latency_assumed price_change h 92,040,526 6,682,800 17ms 26ms 159ms 40.9s 0 transport_latency_assumed tick_size_change c 1,904 1,814 5ms 10ms 51ms 200ms 0 transport_latency_assumed tick_size_change e 2,200 2 41ms 46ms 101ms 189ms 0 transport_latency_assumed tick_size_change f 2,200 4 50ms 62ms 90ms 211ms 0 transport_latency_assumed tick_size_change g 2,200 not meas. 81ms 102ms 165ms 315ms 0 transport_latency_assumed tick_size_change h 2,200 380 17ms 27ms 64ms 1.3s 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-15/07/2026-09-15T07.parquet sha256sum 2026-09-15T07.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.