Hour audit: 2026-09-19T09
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-19T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T09:00:00.000054462+00:00 · last event 2026-09-19T09:59:59.999943935+00:00
VOLUME 129,960,766 rows · 1,407,274,100 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 127,950,476 · e: 127,909,182 · g: 122,998,387 · f: 122,903,130 · c: 107,008,119 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 25,961,806 (19.98%) · e: 1,299,442 (1.00%) · g: 354,003 (0.27%) · f: 374,606 (0.29%) · c: 101,970,909 (78.46%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 129,960,766 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7cb85d5251c1ce0446d75d7b60c0f7dcd5878487e085e773db5c803f5b05b22f
the corpus checksum ledger names this file with the same digest
joined 129,974,009 to merged 129,960,766, minus 13,243 (minus 0.0102%)
boundary drops 13,243 · 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-19T11:03: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 14,234,076 161,871,727 0-54 2949d4bb75fb8f76681e181413e874104335293ff8932f6041bc333fcd58d7a1 book 2,164,130 110,176,913 55-63 2798c1a54388f07afbc2611e824c091be2c1186e00a6a595a132c39d72893683 last_trade_price 51,404 3,021,032 64-64 54214c1c52d15861f295cc8f18e8b9c81f1d78d74cfb7682676d47d9ddc4650d market_resolved 574 73,420 65-65 ef872b357d3dabe863b273402c4dbb61e38ee29f20be7256484f87d3b8ee4fd9 new_market 458 47,506 66-66 570845ccf4da02e1f26c466c215fadb41322202080ec2264a828aa9cb1cb97c8 price_change 113,506,300 1,130,464,837 67-499 ad183cca913a8c0db228ff1619f2863f6a91644a83dec2ce4250ebef27d12397 tick_size_change 3,824 140,929 500-500 2a086c7913b72c92172b97f5c17796309f7b5db00835cd5871be566b40ea7ade EVENT MIX count share price_change 113,506,300 87.34% best_bid_ask 14,234,076 10.95% book 2,164,130 1.67% last_trade_price 51,404 0.04% tick_size_change 3,824 <0.01% market_resolved 574 <0.01% new_market 458 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,234,390 14,234,076 314 3,641 FULL book 2,175,098 2,164,130 10,968 188,601 FULL last_trade_price 51,405 51,404 1 519 FULL market_resolved 574 574 0 5 FULL new_market 458 458 0 6 FULL price_change 113,508,260 113,506,300 1,960 1,435 FULL tick_size_change 3,824 3,824 0 152 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,741,178 11,245,443 5ms 11ms 78ms 5.4s 0 transport_latency_assumed best_bid_ask e 14,232,097 124,623 42ms 48ms 126ms 5.5s 0 transport_latency_assumed best_bid_ask f 13,654,951 20,365 48ms 56ms 149ms 4.4s 0 transport_latency_assumed best_bid_ask g 13,623,105 3,927 77ms 92ms 220ms 8.4s 0 transport_latency_assumed best_bid_ask h 14,230,785 2,839,718 18ms 26ms 86ms 9.6s 0 transport_latency_assumed book c 1,769,269 1,617,556 4.9min 17.3h 37.8d 112.5d 0 book_staleness book e 214,436 54,811 1.4s 32.3min 27.8d 112.5d 0 book_staleness book f 591,779 93,289 3.0min 14.9h 34.6d 112.5d 0 book_staleness book g 630,705 286,682 3.7min 15.1h 34.8d 112.5d 0 book_staleness book h 256,470 111,792 20.0s 36.8min 27.8d 112.5d 0 book_staleness last_trade_price c 42,868 40,507 10ms 44ms 240ms 5.0s 0 transport_latency_assumed last_trade_price e 51,251 725 49ms 128ms 1.1s 5.5s 0 transport_latency_assumed last_trade_price f 48,949 195 56ms 159ms 1.6s 5.1s 0 transport_latency_assumed last_trade_price g 48,906 99 88ms 215ms 3.2s 8.4s 0 transport_latency_assumed last_trade_price h 51,066 9,878 23ms 67ms 316ms 5.3s 0 transport_latency_assumed market_resolved c 479 457 5ms 6.5min 12.2min 13.0min 0 transport_latency_assumed market_resolved e 448 5 44ms 174ms 450ms 856ms 0 transport_latency_assumed market_resolved f 447 not meas. 50ms 202ms 2.9min 4.0min 0 transport_latency_assumed market_resolved g 458 33 84ms 482ms 6.5min 6.5min 0 transport_latency_assumed market_resolved h 448 79 19ms 62ms 182ms 374ms 0 transport_latency_assumed new_market c 352 234 71ms 5.3min 6.5min 8.4min 0 transport_latency_assumed new_market e 302 44 73ms 325ms 28.9s 1.1min 0 transport_latency_assumed new_market f 296 47 83ms 11.3s 5.5min 5.6min 0 transport_latency_assumed new_market g 302 26 100ms 437ms 5.3min 5.3min 0 transport_latency_assumed new_market h 302 107 56ms 309ms 26.0s 1.0min 0 transport_latency_assumed price_change c 93,450,629 89,063,638 5ms 12ms 111ms 5.5s 0 transport_latency_assumed price_change e 113,406,824 1,119,184 42ms 53ms 256ms 5.8s 0 transport_latency_assumed price_change f 108,603,060 260,704 49ms 62ms 313ms 6.6s 0 transport_latency_assumed price_change g 108,691,191 63,228 78ms 97ms 388ms 8.4s 0 transport_latency_assumed price_change h 113,407,601 22,999,546 18ms 30ms 136ms 10.0s 0 transport_latency_assumed tick_size_change c 3,344 3,074 5ms 24ms 85ms 155ms 0 transport_latency_assumed tick_size_change e 3,824 50 43ms 73ms 223ms 412ms 0 transport_latency_assumed tick_size_change f 3,648 6 49ms 60ms 188ms 509ms 0 transport_latency_assumed tick_size_change g 3,720 8 77ms 98ms 241ms 944ms 0 transport_latency_assumed tick_size_change h 3,804 686 18ms 47ms 175ms 389ms 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/09/2026-09-19T09.parquet sha256sum 2026-09-19T09.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.