Hour audit: 2026-09-22T04
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-22T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T04:00:00.000502647+00:00 · last event 2026-09-22T04:59:59.999995853+00:00
VOLUME 113,671,944 rows · 1,171,335,811 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 113,013,918 · e: 112,489,718 · c: 108,935,135 · f: 108,744,917 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 10,314,370 (9.07%) · e: 737,348 (0.65%) · c: 101,962,185 (89.70%) · f: 658,041 (0.58%) (rows of the merged file that came from it; these partition it)
4 expected, all 4 contributed
INTEGRITY sha256 7063ab125d424b56087fbcfbf993dba007d69a1ba460807c1c5e2f26995e8224
the corpus checksum ledger names this file with the same digest
joined 113,677,383 to merged 113,671,944, minus 5,439 (minus 0.0048%)
boundary drops 5,439 · 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-22T05:56:14Z as cefh
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,373,866 118,159,353 0-39 d4238f6007c942b74cfb002275c9197c230a9fe315ea86fb4440b1f6e89615fe book 686,837 57,899,344 40-42 e998b722e121115a5a6a5983075eadd5606e8c541e9d032ebfb7b2d06477dfb2 last_trade_price 50,016 2,813,265 43-43 f07102b2ea215d2db1d21d2cff43de4e157d0bf4bd2bfbe5b09db1eae498738b market_resolved 760 106,093 44-44 8be6308c95f9ffc4adf2a8f8eb9802e05e4a4030593de2b7bf49629ae207f3c3 new_market 3,245 325,535 45-45 6a629e3ae6694255374f7a30f4c418ab5f03966d6ce004b101da836474110ad2 price_change 102,554,424 990,637,569 46-437 0bc2ad13e127ba1aba46ca7f4cea9c67861f929fbc482c7933884296a40deb02 tick_size_change 2,796 100,890 438-438 3001798cc173db4f10ae42a53418ded74ff1fd811388b20b456b8759a68e87ba EVENT MIX count share price_change 102,554,424 90.22% best_bid_ask 10,373,866 9.13% book 686,837 0.60% last_trade_price 50,016 0.04% new_market 3,245 <0.01% tick_size_change 2,796 <0.01% market_resolved 760 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,374,121 10,373,866 255 570 FULL book 689,917 686,837 3,080 173,264 FULL last_trade_price 50,016 50,016 0 85 FULL market_resolved 760 760 0 2 FULL new_market 3,245 3,245 0 14 FULL price_change 102,556,528 102,554,424 2,104 444 FULL tick_size_change 2,796 2,796 0 67 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,951,363 9,361,248 5ms 16ms 191ms 6.8s 0 transport_latency_assumed best_bid_ask e 10,368,938 65,415 40ms 58ms 305ms 16.6s 0 transport_latency_assumed best_bid_ask f 9,951,685 25,755 47ms 67ms 317ms 12.5s 0 transport_latency_assumed best_bid_ask h 10,370,444 921,448 18ms 35ms 302ms 28.4s 0 transport_latency_assumed book c 503,090 261,244 5.5min 2.6d 40.6d 115.3d 0 book_staleness book e 114,754 11,090 44ms 8.8s 3.5d 96.8d 0 book_staleness book f 479,009 354,960 4.7min 2.6d 40.6d 115.2d 0 book_staleness book h 160,346 59,543 37ms 3.6h 27.4d 115.2d 0 book_staleness last_trade_price c 48,446 44,704 6ms 27ms 259ms 3.3s 0 transport_latency_assumed last_trade_price e 49,343 418 43ms 179ms 6.4s 16.6s 0 transport_latency_assumed last_trade_price f 46,676 218 50ms 167ms 4.6s 11.8s 0 transport_latency_assumed last_trade_price h 49,744 4,676 19ms 55ms 399ms 6.8s 0 transport_latency_assumed market_resolved c 660 606 5ms 98ms 5.5min 5.5min 0 transport_latency_assumed market_resolved e 644 24 42ms 12.5s 1.0min 1.0min 0 transport_latency_assumed market_resolved f 675 46 49ms 432ms 5.7min 5.7min 0 transport_latency_assumed market_resolved h 644 84 19ms 12.5s 1.0min 1.0min 0 transport_latency_assumed new_market c 2,120 1,384 98ms 47.6s 1.8min 2.5min 0 transport_latency_assumed new_market e 2,120 585 222ms 48.3s 1.7min 2.4min 0 transport_latency_assumed new_market f 2,134 455 218ms 44.1s 4.0min 1.6h 0 transport_latency_assumed new_market h 2,120 821 175ms 41.5s 1.9min 2.5min 0 transport_latency_assumed price_change c 98,426,828 92,290,546 5ms 18ms 200ms 6.8s 0 transport_latency_assumed price_change e 101,951,123 659,786 41ms 71ms 921ms 16.7s 0 transport_latency_assumed price_change f 98,262,042 276,585 48ms 79ms 552ms 12.5s 0 transport_latency_assumed price_change h 102,427,824 9,327,507 18ms 39ms 356ms 31.0s 0 transport_latency_assumed tick_size_change c 2,628 2,453 5ms 21ms 125ms 200ms 0 transport_latency_assumed tick_size_change e 2,796 30 41ms 68ms 269ms 632ms 0 transport_latency_assumed tick_size_change f 2,696 22 48ms 78ms 342ms 575ms 0 transport_latency_assumed tick_size_change h 2,796 291 18ms 41ms 305ms 1.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-22/04/2026-09-22T04.parquet sha256sum 2026-09-22T04.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.