Hour audit: 2026-09-05T19
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-05T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T19:00:00.059505957+00:00 · last event 2026-09-05T19:59:59.999977833+00:00
VOLUME 119,278,080 rows · 1,271,841,135 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 117,774,342 · e: 117,707,456 · h: 117,656,798 · g: 117,117,363 · c: 100,544,678 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 689,717 (0.58%) · e: 19,289 (0.02%) · h: 10,695 (0.01%) · g: 117,114,976 (98.19%) · c: 1,443,403 (1.21%) (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 119,278,080 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f2073e6ddc254828e761c77bd6b976a69f1b570bdadf3ea5c41b795aae22b03a
the corpus checksum ledger names this file with the same digest
joined 119,280,493 to merged 119,278,080, minus 2,413 (minus 0.0020%)
boundary drops 2,413 · 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-05T23:40:07Z 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 9,565,942 111,680,850 0-36 c1b6d497eda73863aa7bbe925c46c17f977ac568f924074f5088a7a614bf6c14 book 1,657,034 83,064,359 37-43 dd26d6c4bd73964593068382a7922c5cc31fcc216443de47a0cbae287b37876f last_trade_price 63,358 3,593,338 44-44 b49be6f63fe17e68accd2d1cf46b96172f5ec5e5366646d38b1ee8bd89ab4bc8 market_resolved 4,349 538,036 45-45 2492357c83167ccc8775ef04802536c1aedad76587e0007dc90b3ca9974e172e new_market 5,725 442,746 46-46 0145f6126bb48de06040cce83d75fd4787a008bb408d46277a3d57f68afab2be price_change 107,972,244 1,070,819,609 47-458 2ae33aeeb6e855bb0ca669dba984f0b6d24d03fac3d85a86135f501ebce2a13e tick_size_change 9,428 345,116 459-459 f91cc961191252260654ac7cd56dcecd04644e3fa5a2a58e73130f4bdb7570de EVENT MIX count share price_change 107,972,244 90.52% best_bid_ask 9,565,942 8.02% book 1,657,034 1.39% last_trade_price 63,358 0.05% tick_size_change 9,428 <0.01% new_market 5,725 <0.01% market_resolved 4,349 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,566,120 9,565,942 178 3,353 FULL book 1,657,062 1,657,034 28 181,873 FULL last_trade_price 63,359 63,358 1 292 FULL market_resolved 4,349 4,349 0 209 FULL new_market 5,725 5,725 0 32 FULL price_change 107,974,450 107,972,244 2,206 1,734 FULL tick_size_change 9,428 9,428 0 346 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,040,814 641 5ms 11ms 211ms 14.7s 0 transport_latency_assumed best_bid_ask e 9,562,857 1,287 40ms 54ms 355ms 7.8s 0 transport_latency_assumed best_bid_ask f 9,561,760 37,422 48ms 69ms 396ms 11.2s 0 transport_latency_assumed best_bid_ask g 9,525,478 9,525,300 84ms 206ms 2.7s 36.0s 0 transport_latency_assumed best_bid_ask h 9,561,881 1,292 18ms 42ms 606ms 58.9s 0 transport_latency_assumed book c 1,602,368 1,433,919 3.0min 14.1h 34.3d 98.9d 0 book_staleness book e 134,638 1,546 42ms 205ms 6.0s 80.4d 0 book_staleness book f 200,238 70,799 68ms 1.6h 14.2d 98.9d 0 book_staleness book g 147,965 147,963 90ms 16.5s 7.4h 98.9d 0 book_staleness book h 136,228 2,807 22ms 160ms 1.4min 80.3d 0 book_staleness last_trade_price c 54,520 1 10ms 44ms 405ms 7.3s 0 transport_latency_assumed last_trade_price e 63,340 129 45ms 137ms 2.7s 7.8s 0 transport_latency_assumed last_trade_price f 63,179 2,016 55ms 158ms 2.4s 11.2s 0 transport_latency_assumed last_trade_price g 61,211 61,210 92ms 397ms 12.9s 30.6s 0 transport_latency_assumed last_trade_price h 63,163 2 23ms 84ms 1.1s 49.9s 0 transport_latency_assumed market_resolved c 3,873 1,005 5ms 9.4min 15.9min 16.4min 0 transport_latency_assumed market_resolved e 3,311 8 42ms 191ms 41.7s 1.0min 0 transport_latency_assumed market_resolved f 3,311 25 51ms 197ms 583ms 50.4s 0 transport_latency_assumed market_resolved g 3,310 3,310 88ms 371ms 41.7s 1.0min 0 transport_latency_assumed market_resolved h 3,310 1 22ms 77ms 40.9s 1.0min 0 transport_latency_assumed new_market c 4,286 1,571 32.7s 13.1min 13.7min 1.2h 0 transport_latency_assumed new_market e 2,684 505 262ms 34.2s 51.1s 1.2h 0 transport_latency_assumed new_market f 2,652 776 290ms 31.5s 48.7s 42.7min 0 transport_latency_assumed new_market g 2,652 2,652 397ms 31.5s 48.5s 1.2h 0 transport_latency_assumed new_market h 2,662 221 227ms 32.7s 49.9s 1.2h 0 transport_latency_assumed price_change c 90,830,761 6,266 5ms 12ms 235ms 14.7s 0 transport_latency_assumed price_change e 107,931,198 15,814 40ms 61ms 407ms 7.8s 0 transport_latency_assumed price_change f 107,933,774 578,655 49ms 76ms 441ms 11.3s 0 transport_latency_assumed price_change g 107,367,343 107,365,137 84ms 219ms 4.1s 36.0s 0 transport_latency_assumed price_change h 107,880,126 6,372 18ms 45ms 610ms 1.0min 0 transport_latency_assumed tick_size_change c 8,056 not meas. 5ms 24ms 390ms 880ms 0 transport_latency_assumed tick_size_change e 9,428 not meas. 40ms 82ms 465ms 654ms 0 transport_latency_assumed tick_size_change f 9,428 24 49ms 106ms 483ms 654ms 0 transport_latency_assumed tick_size_change g 9,404 9,404 87ms 316ms 1.5s 22.2s 0 transport_latency_assumed tick_size_change h 9,428 not meas. 18ms 58ms 653ms 8.2s 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-05/19/2026-09-05T19.parquet sha256sum 2026-09-05T19.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.