Hour audit: 2026-09-19T04
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-19T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T04:00:00.000124748+00:00 · last event 2026-09-19T04:59:59.999888737+00:00
VOLUME 105,590,926 rows · 1,047,864,261 bytes (999.32 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 105,516,325 · h: 105,484,396 · e: 105,408,119 · f: 105,374,687 · g: 105,306,493 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 100,517,089 (95.19%) · h: 3,938,872 (3.73%) · e: 779,559 (0.74%) · f: 307,156 (0.29%) · g: 48,250 (0.05%) (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 105,590,926 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d2067a4708f138b29701ed908a8ee15ebc5ea831939f08ed4bb92686932ed2cd
the corpus checksum ledger names this file with the same digest
joined 105,593,722 to merged 105,590,926, minus 2,796 (minus 0.0026%)
boundary drops 2,796 · 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-19T05:57:12Z 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,718,510 127,186,817 0-44 141dc67437c9f045ae38f9e258f0acf3b8ff73ab6a7a1b741b978258f1f8f7bf book 133,719 13,105,011 45-45 d0c9dc68164300329d1a3c213934edcbc4c6f005ecd44fd8c11a99f04666c7c9 last_trade_price 49,350 2,874,650 46-46 b47ccc081dab065f66115890633b57bdb53c4fb76f3f22b920799cc660525a92 market_resolved 1,649 268,601 47-47 27398a0eeef49a14662062f68cfb96c32a9c59d5bbce0d6677715eb81824b2f0 new_market 3,094 307,051 48-48 fa926a7e48bec64fe4a6b7daa5f866d84f197f56609ac6f54c2f0dec636f848e price_change 93,679,440 902,731,161 49-406 2efb070413a7dab436219ec22f1b948ac339fe1376c21dff4ec1c4bd4cd9fad4 tick_size_change 5,164 187,564 407-407 2128b3917f857141605ea69e1fa0aed15159c6985830edd7c479979e2250b3e2 EVENT MIX count share price_change 93,679,440 88.72% best_bid_ask 11,718,510 11.10% book 133,719 0.13% last_trade_price 49,350 0.05% tick_size_change 5,164 <0.01% new_market 3,094 <0.01% market_resolved 1,649 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,718,822 11,718,510 312 131 FULL book 133,719 133,719 0 8,484 FULL last_trade_price 49,350 49,350 0 0 FULL market_resolved 1,649 1,649 0 0 FULL new_market 3,094 3,094 0 0 FULL price_change 93,681,924 93,679,440 2,484 101 FULL tick_size_change 5,164 5,164 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,717,662 11,190,684 4ms 10ms 216ms 5.7s 0 transport_latency_assumed best_bid_ask e 11,713,036 85,492 42ms 51ms 261ms 16.6s 0 transport_latency_assumed best_bid_ask f 11,713,754 30,587 47ms 59ms 312ms 13.6s 0 transport_latency_assumed best_bid_ask g 11,711,925 5,418 79ms 101ms 541ms 37.2s 0 transport_latency_assumed best_bid_ask h 11,714,928 406,329 17ms 33ms 504ms 49.6s 0 transport_latency_assumed book c 110,605 100,522 6ms 121ms 12.3h 93.7d 0 book_staleness book e 109,311 6,806 44ms 2.2s 12.8h 93.7d 0 book_staleness book f 112,043 7,477 50ms 3.0s 13.0h 93.7d 0 book_staleness book g 110,786 7,032 86ms 3.2s 13.0h 112.2d 0 book_staleness book h 111,680 11,882 21ms 358ms 12.7h 93.7d 0 book_staleness last_trade_price c 49,178 45,840 10ms 56ms 411ms 5.0s 0 transport_latency_assumed last_trade_price e 48,040 535 51ms 208ms 5.6s 16.6s 0 transport_latency_assumed last_trade_price f 48,402 317 57ms 234ms 7.6s 13.6s 0 transport_latency_assumed last_trade_price g 47,816 22 94ms 370ms 11.3s 37.2s 0 transport_latency_assumed last_trade_price h 48,976 2,636 24ms 94ms 807ms 11.5s 0 transport_latency_assumed market_resolved c 1,644 1,605 4ms 9ms 130ms 702ms 0 transport_latency_assumed market_resolved e 1,644 13 44ms 162ms 522ms 1.0min 0 transport_latency_assumed market_resolved f 1,644 1 49ms 138ms 529ms 1.1s 0 transport_latency_assumed market_resolved g 1,644 not meas. 83ms 234ms 829ms 20.8s 0 transport_latency_assumed market_resolved h 1,644 30 20ms 64ms 387ms 4.8s 0 transport_latency_assumed new_market c 1,982 1,181 117ms 20.7s 1.8min 3.4min 0 transport_latency_assumed new_market e 1,982 445 202ms 22.0s 1.9min 3.3min 0 transport_latency_assumed new_market f 1,982 366 229ms 25.3s 1.8min 3.2min 0 transport_latency_assumed new_market g 1,982 296 306ms 22.7s 1.8min 3.2min 0 transport_latency_assumed new_market h 1,982 806 175ms 23.7s 2.0min 3.4min 0 transport_latency_assumed price_change c 93,630,090 89,172,420 4ms 11ms 223ms 6.9s 0 transport_latency_assumed price_change e 93,528,942 686,260 42ms 60ms 452ms 16.6s 0 transport_latency_assumed price_change f 93,491,698 268,408 47ms 69ms 486ms 13.6s 0 transport_latency_assumed price_change g 93,427,176 35,482 80ms 123ms 901ms 38.0s 0 transport_latency_assumed price_change h 93,600,022 3,516,870 18ms 37ms 552ms 50.0s 0 transport_latency_assumed tick_size_change c 5,164 4,837 4ms 14ms 143ms 209ms 0 transport_latency_assumed tick_size_change e 5,164 8 42ms 51ms 120ms 312ms 0 transport_latency_assumed tick_size_change f 5,164 not meas. 47ms 60ms 130ms 331ms 0 transport_latency_assumed tick_size_change g 5,164 not meas. 80ms 94ms 209ms 706ms 0 transport_latency_assumed tick_size_change h 5,164 319 18ms 29ms 95ms 3.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-19/04/2026-09-19T04.parquet sha256sum 2026-09-19T04.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.