Hour audit: 2026-09-19T00
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-19T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T00:00:00.000051005+00:00 · last event 2026-09-19T00:59:59.999974533+00:00
VOLUME 120,253,794 rows · 1,275,943,173 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 119,775,761 · h: 119,742,537 · e: 119,698,828 · g: 119,691,548 · f: 114,932,161 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 113,471,478 (94.36%) · h: 5,366,296 (4.46%) · e: 646,985 (0.54%) · g: 66,225 (0.06%) · f: 702,810 (0.58%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 120,253,794 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 76ef426fbb6c3ba4f599e3a95011ecd937135dfe8db077aca0d73a76d216cbec
the corpus checksum ledger names this file with the same digest
joined 120,264,301 to merged 120,253,794, minus 10,507 (minus 0.0087%)
boundary drops 10,507 · 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-19T03:44:33Z 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 12,999,140 144,040,467 0-49 09b82a0c9b13e499533df90d5fb6ac88bc86cc737939eea8f967b8139984e4b4 book 580,125 56,621,108 50-52 e7fb5368bf56c5e2bcf7a8825cb116c8352f4fe1046ded2002a619802499b99c last_trade_price 62,678 3,512,000 53-53 c16b8fcfe49e832cd022783d18a3877887a58318cbcf7fc724639d47fe673a12 market_resolved 961 146,101 54-54 b247b84e075d437737fdd54dd51de3d38d1d4991bceec069bac38780e68244f9 new_market 1,228 131,496 55-55 52e73d6177cb4c83f1f10b6eea703c2db9fae308ce23f783d396db199d175985 price_change 106,606,706 1,070,015,824 56-462 cf863d6a9ffb46117dd4dc40d784e8893393089b63024170f4c098bee19c1a8c tick_size_change 2,956 108,303 463-463 37767515cc80d39d9595df96f522a2e3a4a27b377840ac5c26cafeb871d36c96 EVENT MIX count share price_change 106,606,706 88.65% best_bid_ask 12,999,140 10.81% book 580,125 0.48% last_trade_price 62,678 0.05% tick_size_change 2,956 <0.01% new_market 1,228 <0.01% market_resolved 961 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,000,134 12,999,140 994 599 FULL book 580,229 580,125 104 208,807 FULL last_trade_price 62,679 62,678 1 71 FULL market_resolved 961 961 0 8 FULL new_market 1,228 1,228 0 0 FULL price_change 106,616,110 106,606,706 9,404 294 FULL tick_size_change 2,960 2,956 4 21 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,998,100 12,370,064 5ms 12ms 116ms 4.9s 0 transport_latency_assumed best_bid_ask e 12,996,257 65,417 41ms 51ms 189ms 17.2s 0 transport_latency_assumed best_bid_ask f 12,429,597 25,865 47ms 59ms 216ms 17.7s 0 transport_latency_assumed best_bid_ask g 12,996,004 3,652 79ms 99ms 362ms 18.4s 0 transport_latency_assumed best_bid_ask h 12,996,597 534,142 18ms 38ms 177ms 31.3s 0 transport_latency_assumed book c 136,029 125,095 7ms 42ms 7.4h 112.1d 0 book_staleness book e 136,416 3,797 44ms 466ms 8.4h 93.5d 0 book_staleness book f 557,230 419,426 6.5min 8.5h 27.4d 112.1d 0 book_staleness book g 153,964 18,690 86ms 4.3min 5.1d 112.1d 0 book_staleness book h 138,153 13,117 21ms 99ms 8.4h 93.5d 0 book_staleness last_trade_price c 62,450 58,123 11ms 50ms 279ms 5.1s 0 transport_latency_assumed last_trade_price e 62,237 430 52ms 254ms 4.2s 17.2s 0 transport_latency_assumed last_trade_price f 59,848 179 57ms 268ms 2.7s 17.7s 0 transport_latency_assumed last_trade_price g 62,244 90 92ms 263ms 6.1s 15.3s 0 transport_latency_assumed last_trade_price h 62,259 3,856 24ms 77ms 376ms 8.6s 0 transport_latency_assumed market_resolved c 900 864 5ms 12ms 101ms 56.6s 0 transport_latency_assumed market_resolved e 900 4 42ms 120ms 497ms 55.5s 0 transport_latency_assumed market_resolved f 892 61 48ms 279ms 5.1min 5.1min 0 transport_latency_assumed market_resolved g 900 2 80ms 223ms 487ms 1.0s 0 transport_latency_assumed market_resolved h 900 30 19ms 60ms 204ms 55.9s 0 transport_latency_assumed new_market c 822 480 97ms 17.5s 1.1min 1.3min 0 transport_latency_assumed new_market e 822 163 178ms 15.3s 59.0s 1.4min 0 transport_latency_assumed new_market f 822 169 171ms 19.7s 1.2min 1.6min 0 transport_latency_assumed new_market g 822 97 253ms 16.5s 59.5s 1.2min 0 transport_latency_assumed new_market h 822 319 127ms 12.0s 57.2s 1.4min 0 transport_latency_assumed price_change c 106,574,504 100,913,956 5ms 14ms 150ms 5.1s 0 transport_latency_assumed price_change e 106,499,240 577,174 41ms 60ms 350ms 17.2s 0 transport_latency_assumed price_change f 101,880,896 257,110 47ms 68ms 383ms 17.7s 0 transport_latency_assumed price_change g 106,474,658 43,694 80ms 113ms 580ms 19.4s 0 transport_latency_assumed price_change h 106,540,846 4,814,772 18ms 41ms 238ms 31.3s 0 transport_latency_assumed tick_size_change c 2,956 2,896 5ms 8ms 26ms 202ms 0 transport_latency_assumed tick_size_change e 2,956 not meas. 41ms 45ms 82ms 187ms 0 transport_latency_assumed tick_size_change f 2,876 not meas. 46ms 50ms 80ms 135ms 0 transport_latency_assumed tick_size_change g 2,956 not meas. 79ms 90ms 129ms 235ms 0 transport_latency_assumed tick_size_change h 2,960 60 18ms 31ms 95ms 3.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-19/00/2026-09-19T00.parquet sha256sum 2026-09-19T00.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.