Hour audit: 2026-09-13T19
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-13T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T19:00:00.000175194+00:00 · last event 2026-09-13T19:59:59.999937016+00:00
VOLUME 154,710,476 rows · 1,769,614,572 bytes (1.65 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 149,353,120 · e: 132,663,402 · f: 108,831,411 · g: 106,243,073 · c: 88,389,968 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 61,952,238 (40.04%) · e: 5,954,635 (3.85%) · f: 2,512,336 (1.62%) · g: 1,214,799 (0.79%) · c: 83,076,468 (53.70%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 2dbf7d370a51d52b933e35d3191095167b86f42cce953e77509dce9f2be4a6b8
the corpus checksum ledger names this file with the same digest
joined 154,732,050 to merged 154,710,476, minus 21,574 (minus 0.0139%)
boundary drops 21,574 · 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-13T21:40:53Z 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 14,536,300 166,530,535 0-55 5793a141bf64990afc3c3a4b7b35e344762aedd77618107aa431f830a32896e2 book 5,374,830 162,849,301 56-76 7ab1034aa37105007cf09427643143e9d5c6b080b9db0320f17fa721d4772bd9 last_trade_price 57,071 3,433,813 77-77 ea9bb8ce15e01a429e5f99e5a7d9ec39aacd00649b56baa445f057e3d5ab195c market_resolved 17,213 669,922 78-78 b42051c1a23c6b23bbb07424a70d62c1a83963fe49504671f304e4d5502aa2b0 new_market 18,694 813,003 79-79 e17caf6af404902b7ab33ab8be5ef25458313914992e76a5bb071bb6ce7bf19b price_change 134,697,312 1,433,232,215 80-593 db7a7f567c68ba7f631b17e9b4821259871814c2acc352d5e6cc2aa2ff9c81f2 tick_size_change 9,056 330,303 594-594 b2b6656a799dc5673b499801ca3b532c0e60f4ff1c44cd6a5aebd7391551011c EVENT MIX count share price_change 134,697,312 87.06% best_bid_ask 14,536,300 9.40% book 5,374,830 3.47% last_trade_price 57,071 0.04% new_market 18,694 0.01% market_resolved 17,213 0.01% tick_size_change 9,056 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,536,488 14,536,300 188 14,997 FULL book 5,394,351 5,374,830 19,521 171,538 FULL last_trade_price 57,073 57,071 2 1,722 FULL market_resolved 17,220 17,213 7 1,504 FULL new_market 18,728 18,694 34 902 FULL price_change 134,699,134 134,697,312 1,822 9,728 FULL tick_size_change 9,056 9,056 0 1,762 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,283,839 7,862,450 5ms 16ms 198ms 6.5s 0 transport_latency_assumed best_bid_ask e 12,840,341 537,824 41ms 71ms 375ms 11.0s 0 transport_latency_assumed best_bid_ask f 10,386,985 148,934 47ms 86ms 423ms 16.0s 0 transport_latency_assumed best_bid_ask g 10,071,124 21,213 84ms 191ms 955ms 1.4min 0 transport_latency_assumed best_bid_ask h 14,530,927 5,965,879 19ms 52ms 676ms 53.4s 0 transport_latency_assumed book c 4,013,962 3,044,819 30.5min 2.1d 36.2d 106.9d 0 book_staleness book e 1,155,386 353,206 16.8min 2.1d 36.0d 106.9d 0 book_staleness book f 2,662,316 935,564 26.8min 2.1d 36.2d 106.9d 0 book_staleness book g 2,922,107 988,645 27.4min 2.1d 36.2d 106.9d 0 book_staleness book h 125,062 52,596 25ms 168ms 3.9s 33.0d 0 book_staleness last_trade_price c 31,074 29,159 11ms 57ms 305ms 5.0s 0 transport_latency_assumed last_trade_price e 49,804 1,997 55ms 251ms 4.4s 11.2s 0 transport_latency_assumed last_trade_price f 39,682 620 62ms 264ms 4.7s 15.9s 0 transport_latency_assumed last_trade_price g 38,296 159 99ms 475ms 7.8s 1.4min 0 transport_latency_assumed last_trade_price h 57,032 25,136 27ms 100ms 1.0s 34.3s 0 transport_latency_assumed market_resolved c 15,898 13,031 22.7min 40.6min 51.1min 52.7min 0 transport_latency_assumed market_resolved e 2,624 301 106ms 4.2min 9.8min 10.2min 0 transport_latency_assumed market_resolved f 2,623 94 124ms 16.3min 19.5min 19.8min 0 transport_latency_assumed market_resolved g 7,953 2,709 12.0min 29.1min 37.3min 37.9min 0 transport_latency_assumed market_resolved h 2,440 1,078 33ms 86ms 1.9s 55.1s 0 transport_latency_assumed new_market c 17,188 13,495 12.1min 35.1min 49.8min 1.4h 0 transport_latency_assumed new_market e 4,163 975 247ms 2.3min 5.5min 1.2h 0 transport_latency_assumed new_market f 4,866 869 316ms 8.7min 13.1min 1.1h 0 transport_latency_assumed new_market g 9,372 1,933 4.5min 20.8min 30.5min 1.4h 0 transport_latency_assumed new_market h 3,799 1,422 170ms 21.5s 57.8s 27.1min 0 transport_latency_assumed price_change c 76,023,371 72,109,283 6ms 17ms 202ms 6.5s 0 transport_latency_assumed price_change e 118,603,460 5,059,918 41ms 83ms 459ms 11.1s 0 transport_latency_assumed price_change f 95,728,279 1,426,143 47ms 100ms 513ms 16.3s 0 transport_latency_assumed price_change g 93,188,413 200,128 85ms 225ms 1.4s 1.4min 0 transport_latency_assumed price_change h 134,624,804 55,901,840 19ms 55ms 698ms 53.5s 0 transport_latency_assumed tick_size_change c 4,636 4,231 6ms 26ms 292ms 1.2s 0 transport_latency_assumed tick_size_change e 7,624 414 41ms 85ms 429ms 812ms 0 transport_latency_assumed tick_size_change f 6,660 112 47ms 81ms 392ms 1.1s 0 transport_latency_assumed tick_size_change g 5,808 12 85ms 333ms 899ms 6.3s 0 transport_latency_assumed tick_size_change h 9,056 4,287 19ms 61ms 849ms 6.9s 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-13/19/2026-09-13T19.parquet sha256sum 2026-09-13T19.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.