Hour audit: 2026-09-17T18
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-17T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T18:00:00.000002128+00:00 · last event 2026-09-17T18:59:59.998207607+00:00
VOLUME 118,186,968 rows · 1,314,727,762 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 117,028,284 · h: 116,261,334 · g: 115,435,782 · c: 112,936,205 · f: 111,455,311 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,424,247 (1.21%) · h: 12,254,767 (10.37%) · g: 169,902 (0.14%) · c: 103,237,793 (87.35%) · f: 1,100,259 (0.93%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 ec6b9bb765b686befb6b3cb4dd86b2488db9640d71c48cc7ca112e57318bae1f
the corpus checksum ledger names this file with the same digest
joined 118,188,104 to merged 118,186,968, minus 1,136 (minus 0.0010%)
boundary drops 1,136 · 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-17T20:01:58Z 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 11,272,294 134,820,844 0-43 8142251ab63b36eb1a12c382b8e92d6be6952e00e4e3c244cfe4c7aff3ab1dff book 1,252,553 87,988,656 44-48 209b516b05fd64d781fd16702a3becbb34b603c6e1ac73b89aa12286beb2dd81 last_trade_price 66,330 3,832,826 49-49 45565cf79965f3c842a695a0676e104862db186b2a8f127640fa06b004c156e7 market_resolved 944 131,692 50-50 8c2227d455ff18c4eef221bd24739dc5f4c5cf7127337a515ebf672e53ae1890 new_market 9,515 957,578 51-51 8b6e4a85c925b91857735af8205d2bd4838bf21935062f26878836379be56512 price_change 105,580,912 1,085,487,071 52-454 da5ecd93a91f2df43ed5a8b82526cc3ef45ef94778177bcc2be05a1c21e9ba50 tick_size_change 4,420 164,536 455-455 03fe4cd9ecd7cf9d4a99f0b509142def58a9e6ef94c5a10bf3c2e46b2b4a30e9 EVENT MIX count share price_change 105,580,912 89.33% best_bid_ask 11,272,294 9.54% book 1,252,553 1.06% last_trade_price 66,330 0.06% new_market 9,515 <0.01% tick_size_change 4,420 <0.01% market_resolved 944 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,272,414 11,272,294 120 2,793 FULL book 1,252,567 1,252,553 14 152,330 FULL last_trade_price 66,330 66,330 0 245 FULL market_resolved 944 944 0 31 FULL new_market 9,515 9,515 0 43 FULL price_change 105,581,914 105,580,912 1,002 1,106 FULL tick_size_change 4,420 4,420 0 112 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,821,055 9,944,723 6ms 28ms 243ms 7.9s 0 transport_latency_assumed best_bid_ask e 11,259,113 122,595 42ms 90ms 416ms 33.7s 0 transport_latency_assumed best_bid_ask f 10,658,071 72,179 46ms 102ms 428ms 29.0s 0 transport_latency_assumed best_bid_ask g 11,162,311 7,024 82ms 228ms 858ms 57.3s 0 transport_latency_assumed best_bid_ask h 11,171,557 1,125,773 19ms 53ms 677ms 53.6s 0 transport_latency_assumed book c 635,397 579,493 1.9min 17.2h 36.0d 110.9d 0 book_staleness book e 376,380 146,789 24.9s 44.5min 26.2d 110.9d 0 book_staleness book f 673,039 309,749 1.8min 18.3h 36.1d 110.9d 0 book_staleness book g 281,302 85,923 3.9s 25.7min 26.2d 110.9d 0 book_staleness book h 334,885 130,599 10.9s 32.8min 26.2d 110.9d 0 book_staleness last_trade_price c 63,771 58,350 12ms 78ms 356ms 5.0s 0 transport_latency_assumed last_trade_price e 65,448 575 68ms 904ms 11.2s 33.7s 0 transport_latency_assumed last_trade_price f 62,280 407 72ms 586ms 6.6s 29.1s 0 transport_latency_assumed last_trade_price g 63,070 81 118ms 1.2s 15.9s 57.1s 0 transport_latency_assumed last_trade_price h 65,808 6,917 27ms 149ms 1.0s 36.4s 0 transport_latency_assumed market_resolved c 820 778 6ms 1.6s 6.3min 6.4min 0 transport_latency_assumed market_resolved e 796 40 44ms 385ms 59.6s 1.0min 0 transport_latency_assumed market_resolved f 782 46 49ms 24.4s 4.8min 4.8min 0 transport_latency_assumed market_resolved g 794 30 84ms 388ms 1.4s 2.1min 0 transport_latency_assumed market_resolved h 793 50 21ms 170ms 58.8s 1.9min 0 transport_latency_assumed new_market c 6,037 3,609 106ms 43.2s 5.1min 2.5h 0 transport_latency_assumed new_market e 5,947 1,257 188ms 33.6s 1.4min 2.6min 0 transport_latency_assumed new_market f 5,941 927 197ms 32.1s 1.4min 2.6min 0 transport_latency_assumed new_market g 5,941 860 311ms 33.8s 1.3min 1.9min 0 transport_latency_assumed new_market h 5,941 2,862 132ms 32.1s 1.4min 2.0min 0 transport_latency_assumed price_change c 101,404,765 92,646,954 6ms 35ms 273ms 8.0s 0 transport_latency_assumed price_change e 105,316,180 1,152,895 42ms 146ms 2.2s 34.6s 0 transport_latency_assumed price_change f 100,051,066 716,904 47ms 154ms 1.6s 29.3s 0 transport_latency_assumed price_change g 103,918,012 75,980 84ms 330ms 4.9s 57.7s 0 transport_latency_assumed price_change h 104,677,962 10,988,179 19ms 67ms 745ms 54.5s 0 transport_latency_assumed tick_size_change c 4,360 3,886 6ms 53ms 292ms 621ms 0 transport_latency_assumed tick_size_change e 4,420 96 42ms 117ms 412ms 3.6s 0 transport_latency_assumed tick_size_change f 4,132 47 46ms 143ms 442ms 1.4s 0 transport_latency_assumed tick_size_change g 4,352 4 82ms 290ms 947ms 11.5s 0 transport_latency_assumed tick_size_change h 4,388 387 19ms 55ms 435ms 2.5s 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/18/2026-09-17T18.parquet sha256sum 2026-09-17T18.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.