Hour audit: 2026-09-17T17
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-17T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T17:00:00.000003241+00:00 · last event 2026-09-17T17:59:59.999751975+00:00
VOLUME 112,282,683 rows · 1,170,894,480 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 112,238,408 · e: 112,194,972 · f: 112,173,955 · h: 112,170,237 · g: 112,103,904 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 106,925,939 (95.23%) · e: 430,739 (0.38%) · f: 253,548 (0.23%) · h: 4,630,655 (4.12%) · g: 41,802 (0.04%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 112,282,683 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 52c7123901aa13f7817680bcd2f026e5c4f25197a29b45327e9d6e698f4059d4
the corpus checksum ledger names this file with the same digest
joined 112,284,880 to merged 112,282,683, minus 2,197 (minus 0.0020%)
boundary drops 2,197 · 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-17T19:02:14Z 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,836,410 124,652,880 0-41 06c03f391ac1f388cf78fa7802ff2d02a743fffc49877c2b75600a18727784cf book 158,990 17,412,274 42-42 ba53d74f47622f4ad45bf831eab249e4cc5a37e0f382cfe5226c9e7ce52372f7 last_trade_price 64,563 3,750,482 43-43 b453ee109e61a34bdfd450cf06fd141e8fadb17f40f3ee441feaf60c348975d8 market_resolved 849 135,912 44-44 184042488c7a7a0e0dd3dc543c2ddc692864f3abb4ef2e59c05b2ef24f4466e1 new_market 1,045 111,370 45-45 077e6a74a5e7477f30c1865b6bf24bca03a8cd438a51bfd51f9ec1e8cdea0c7d price_change 101,216,826 1,023,405,193 46-432 ee908124f6b3f09770f69626bf01fe5be9079d9a9c6d993d84097baa1ae4c2c0 tick_size_change 4,000 145,727 433-433 faf286eb0b9579e01f167f500ce345f06ddd0d9875aef4f4d0c081506bc7fdd0 EVENT MIX count share price_change 101,216,826 90.14% best_bid_ask 10,836,410 9.65% book 158,990 0.14% last_trade_price 64,563 0.06% tick_size_change 4,000 <0.01% new_market 1,045 <0.01% market_resolved 849 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,836,608 10,836,410 198 167 FULL book 159,005 158,990 15 8,409 FULL last_trade_price 64,567 64,563 4 0 FULL market_resolved 849 849 0 0 FULL new_market 1,045 1,045 0 0 FULL price_change 101,218,806 101,216,826 1,980 99 FULL tick_size_change 4,000 4,000 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,835,544 10,372,345 5ms 12ms 88ms 3.2s 0 transport_latency_assumed best_bid_ask e 10,834,425 32,273 41ms 51ms 181ms 9.1s 0 transport_latency_assumed best_bid_ask f 10,834,460 15,763 45ms 57ms 203ms 7.3s 0 transport_latency_assumed best_bid_ask g 10,833,572 1,457 79ms 100ms 337ms 12.8s 0 transport_latency_assumed best_bid_ask h 10,834,156 414,572 18ms 30ms 129ms 8.7s 0 transport_latency_assumed book c 138,200 130,959 7ms 31ms 13.9min 92.3d 0 book_staleness book e 138,051 5,273 44ms 365ms 12.9min 92.3d 0 book_staleness book f 138,342 4,536 48ms 451ms 15.1min 92.3d 0 book_staleness book g 141,766 7,932 84ms 2.2s 36.4min 92.3d 0 book_staleness book h 138,230 10,290 22ms 88ms 16.5min 48.3d 0 book_staleness last_trade_price c 64,381 61,214 11ms 47ms 249ms 4.9s 0 transport_latency_assumed last_trade_price e 64,383 322 52ms 227ms 2.4s 9.1s 0 transport_latency_assumed last_trade_price f 64,406 170 58ms 258ms 2.7s 6.2s 0 transport_latency_assumed last_trade_price g 64,153 20 96ms 588ms 8.3s 12.6s 0 transport_latency_assumed last_trade_price h 64,306 2,837 25ms 82ms 525ms 8.7s 0 transport_latency_assumed market_resolved c 841 819 6ms 13ms 42.6s 1.0min 0 transport_latency_assumed market_resolved e 841 2 43ms 148ms 31.4s 58.8s 0 transport_latency_assumed market_resolved f 841 not meas. 47ms 155ms 31.4s 59.6s 0 transport_latency_assumed market_resolved g 841 2 82ms 235ms 28.5s 58.0s 0 transport_latency_assumed market_resolved h 841 26 19ms 60ms 32.6s 59.4s 0 transport_latency_assumed new_market c 700 410 74ms 21.6s 47.9s 1.2min 0 transport_latency_assumed new_market e 700 93 188ms 13.7s 45.8s 1.6min 0 transport_latency_assumed new_market f 700 81 177ms 13.3s 45.9s 1.6min 0 transport_latency_assumed new_market g 700 89 316ms 16.6s 48.3s 57.8s 0 transport_latency_assumed new_market h 700 372 80ms 14.4s 1.3min 1.3min 0 transport_latency_assumed price_change c 101,194,742 96,356,420 6ms 14ms 135ms 3.9s 0 transport_latency_assumed price_change e 101,152,572 392,704 41ms 63ms 461ms 9.1s 0 transport_latency_assumed price_change f 101,131,206 232,994 45ms 70ms 482ms 7.4s 0 transport_latency_assumed price_change g 101,058,872 32,302 79ms 122ms 1.1s 12.8s 0 transport_latency_assumed price_change h 101,128,004 4,202,406 18ms 35ms 214ms 8.8s 0 transport_latency_assumed tick_size_change c 4,000 3,772 5ms 15ms 272ms 338ms 0 transport_latency_assumed tick_size_change e 4,000 72 41ms 57ms 355ms 551ms 0 transport_latency_assumed tick_size_change f 4,000 4 45ms 69ms 421ms 654ms 0 transport_latency_assumed tick_size_change g 4,000 not meas. 79ms 103ms 516ms 727ms 0 transport_latency_assumed tick_size_change h 4,000 152 18ms 33ms 439ms 2.1s 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-17/17/2026-09-17T17.parquet sha256sum 2026-09-17T17.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.