Hour audit: 2026-09-14T06
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-14T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T06:00:00.000192990+00:00 · last event 2026-09-14T06:59:59.999566232+00:00
VOLUME 98,617,284 rows · 940,218,944 bytes (896.66 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 98,564,039 · c: 98,547,896 · e: 98,544,346 · g: 98,535,993 · h: 98,519,958 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 101,738 (0.10%) · c: 96,158,320 (97.51%) · e: 197,319 (0.20%) · g: 44,335 (0.04%) · h: 2,115,572 (2.15%) (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 98,617,284 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 06861d0dc6f6fcd35e4d87f45ab5a8906cd42de3a88d975ca84711ecca247d99
the corpus checksum ledger names this file with the same digest
joined 98,620,163 to merged 98,617,284, minus 2,879 (minus 0.0029%)
boundary drops 2,879 · 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-14T07:55:48Z 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 10,820,076 113,143,018 0-41 be92e903d4e13fa24272d97c09ddab2f0a56b59323a50c1695498c81a3792b38 book 118,025 12,405,374 42-42 20c886b1cfd69037cb6cb0db5b5a888757cb120b2e0b949bacb215725846a9b1 last_trade_price 43,236 2,462,047 43-43 c3e922be44504d14a03949da874536aa6863d89e1a1e6a54b97e30f0261f533e market_resolved 504 83,688 44-44 cc0f84765e873400d80e0d746ee79d7b86b30904c5a281ad75ab5f2b112dcb8e new_market 701 76,605 45-45 4c55d70749cdcf61c6a0f3f19ddf9e732f375ba2103380ef5136b9234e75ec5e price_change 87,633,342 810,870,220 46-380 75ff48f94bffee15d6b6a1813390f68b4a086697fb7e7ce4ea4ae8b203af38f7 tick_size_change 1,400 51,434 381-381 990610ed09dd23ef93a7fba7ce52c8833542584916d83ea64f6a520fd05decdc EVENT MIX count share price_change 87,633,342 88.86% best_bid_ask 10,820,076 10.97% book 118,025 0.12% last_trade_price 43,236 0.04% tick_size_change 1,400 <0.01% new_market 701 <0.01% market_resolved 504 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,820,321 10,820,076 245 170 FULL book 118,029 118,025 4 12,430 FULL last_trade_price 43,236 43,236 0 0 FULL market_resolved 504 504 0 0 FULL new_market 701 701 0 0 FULL price_change 87,635,972 87,633,342 2,630 240 FULL tick_size_change 1,400 1,400 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,819,424 10,590,915 4ms 7ms 51ms 2.2s 0 transport_latency_assumed best_bid_ask e 10,817,988 14,452 40ms 44ms 106ms 8.1s 0 transport_latency_assumed best_bid_ask f 10,818,131 7,149 47ms 50ms 123ms 12.7s 0 transport_latency_assumed best_bid_ask g 10,816,571 1,297 81ms 97ms 253ms 8.4s 0 transport_latency_assumed best_bid_ask h 10,819,054 206,263 17ms 20ms 77ms 50.5s 0 transport_latency_assumed book c 92,335 89,256 6ms 15ms 5.4h 88.8d 0 book_staleness book e 90,738 1,447 41ms 67ms 51.6s 88.7d 0 book_staleness book f 92,436 2,984 48ms 104ms 4.9h 107.4d 0 book_staleness book g 110,356 20,934 87ms 30.0min 6.8d 107.3d 0 book_staleness book h 90,368 3,404 20ms 38ms 1.3s 88.7d 0 book_staleness last_trade_price c 43,129 41,792 9ms 38ms 175ms 4.5s 0 transport_latency_assumed last_trade_price e 43,074 103 46ms 94ms 328ms 8.1s 0 transport_latency_assumed last_trade_price f 43,136 61 53ms 104ms 623ms 12.8s 0 transport_latency_assumed last_trade_price g 43,132 9 91ms 171ms 637ms 8.4s 0 transport_latency_assumed last_trade_price h 43,180 1,271 22ms 54ms 203ms 8.9s 0 transport_latency_assumed market_resolved c 504 500 4ms 7ms 32ms 505ms 0 transport_latency_assumed market_resolved e 504 not meas. 41ms 120ms 281ms 902ms 0 transport_latency_assumed market_resolved f 504 not meas. 48ms 128ms 235ms 816ms 0 transport_latency_assumed market_resolved g 504 not meas. 88ms 251ms 557ms 949ms 0 transport_latency_assumed market_resolved h 504 4 18ms 49ms 103ms 5.2s 0 transport_latency_assumed new_market c 502 345 73ms 15.6s 24.6s 55.1s 0 transport_latency_assumed new_market e 502 101 154ms 14.9s 25.3s 57.5s 0 transport_latency_assumed new_market f 502 48 150ms 15.2s 25.7s 1.0min 0 transport_latency_assumed new_market g 502 45 232ms 928ms 21.3s 1.3min 0 transport_latency_assumed new_market h 502 162 123ms 15.8s 26.4s 55.1s 0 transport_latency_assumed price_change c 87,590,602 85,434,164 5ms 8ms 73ms 2.9s 0 transport_latency_assumed price_change e 87,590,140 181,216 40ms 45ms 161ms 8.2s 0 transport_latency_assumed price_change f 87,607,930 91,492 47ms 52ms 188ms 12.7s 0 transport_latency_assumed price_change g 87,563,528 22,050 81ms 100ms 348ms 14.7s 0 transport_latency_assumed price_change h 87,564,950 1,904,420 17ms 22ms 116ms 50.8s 0 transport_latency_assumed tick_size_change c 1,400 1,348 5ms 8ms 95ms 129ms 0 transport_latency_assumed tick_size_change e 1,400 not meas. 40ms 44ms 151ms 202ms 0 transport_latency_assumed tick_size_change f 1,400 4 47ms 52ms 118ms 244ms 0 transport_latency_assumed tick_size_change g 1,400 not meas. 81ms 99ms 238ms 562ms 0 transport_latency_assumed tick_size_change h 1,400 48 17ms 21ms 108ms 421ms 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-14/06/2026-09-14T06.parquet sha256sum 2026-09-14T06.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.