Hour audit: 2026-09-13T22
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-13T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T22:00:00.000023205+00:00 · last event 2026-09-13T22:59:59.999536050+00:00
VOLUME 134,601,435 rows · 1,469,698,476 bytes (1.37 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 132,030,239 · h: 132,020,170 · f: 122,576,193 · g: 118,212,790 · c: 104,244,907 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 2,357,699 (1.75%) · h: 32,800,845 (24.37%) · f: 991,281 (0.74%) · g: 384,287 (0.29%) · c: 98,067,323 (72.86%) (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 134,601,435 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 53c45166714d8da9ae9943b3e370457428f492cac0dd53ee3eeba7af082b2dfb
the corpus checksum ledger names this file with the same digest
joined 134,604,449 to merged 134,601,435, minus 3,014 (minus 0.0022%)
boundary drops 3,014 · 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-14T01:09:42Z 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 13,827,847 153,083,483 0-52 ccc4007c761877b8683b128660fb6b67ef909ec40eff63d183cf362363879a6d book 2,661,619 106,434,101 53-63 109a5218179f07fdd2ede822e11cc85bd18a9ae68cc9ea82c4e3053e3c494262 last_trade_price 61,135 3,498,538 64-64 f12a9206dba34f12e53fae03c5e7497eb9861821c3ec3c7cfd41df4928031407 market_resolved 4,907 460,172 65-65 6fb62c4090468e4f560c65ffd96f566626fa9a91658f91b9ae5a1c005e2922b5 new_market 2,639 230,346 66-66 c7f59f71a1e1a923968ec0606d9693a7659f53f73f82c51391ea63a6bda96ca3 price_change 118,038,512 1,204,287,757 67-517 0ec8fbe07d1271257416548b2ca4ac426f50c166999caeb68280c257ae3e677b tick_size_change 4,776 173,256 518-518 fff05a58d0908f437faec9d6df1ddc404545956781803623fc50c5e2eedd31c1 EVENT MIX count share price_change 118,038,512 87.69% best_bid_ask 13,827,847 10.27% book 2,661,619 1.98% last_trade_price 61,135 0.05% market_resolved 4,907 <0.01% tick_size_change 4,776 <0.01% new_market 2,639 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,828,065 13,827,847 218 4,728 FULL book 2,661,657 2,661,619 38 169,016 FULL last_trade_price 61,137 61,135 2 686 FULL market_resolved 4,907 4,907 0 179 FULL new_market 2,639 2,639 0 15 FULL price_change 118,041,268 118,038,512 2,756 3,159 FULL tick_size_change 4,776 4,776 0 273 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,644,199 10,038,638 5ms 16ms 128ms 4.2s 0 transport_latency_assumed best_bid_ask e 13,825,664 247,240 40ms 57ms 272ms 15.5s 0 transport_latency_assumed best_bid_ask f 12,718,592 68,458 46ms 68ms 315ms 18.5s 0 transport_latency_assumed best_bid_ask g 12,239,232 3,693 84ms 120ms 699ms 32.8s 0 transport_latency_assumed best_bid_ask h 13,825,585 3,469,818 18ms 36ms 253ms 53.7s 0 transport_latency_assumed book c 2,117,991 1,996,472 34.8min 2.2d 36.3d 107.0d 0 book_staleness book e 130,957 4,130 44ms 418ms 14.8s 88.4d 0 book_staleness book f 1,082,214 283,881 19.7min 2.2d 36.1d 107.0d 0 book_staleness book g 1,161,054 343,486 20.7min 2.2d 36.2d 107.0d 0 book_staleness book h 132,600 33,650 21ms 93ms 1.3h 88.5d 0 book_staleness last_trade_price c 47,160 43,656 11ms 55ms 291ms 5.0s 0 transport_latency_assumed last_trade_price e 60,995 1,173 52ms 293ms 9.7s 15.5s 0 transport_latency_assumed last_trade_price f 56,355 522 60ms 309ms 5.1s 18.5s 0 transport_latency_assumed last_trade_price g 53,198 34 99ms 487ms 11.2s 32.7s 0 transport_latency_assumed last_trade_price h 60,961 15,750 25ms 86ms 558ms 41.4s 0 transport_latency_assumed market_resolved c 4,030 3,644 54ms 12.6min 16.8min 17.1min 0 transport_latency_assumed market_resolved e 2,666 38 58ms 150ms 285ms 877ms 0 transport_latency_assumed market_resolved f 2,729 41 74ms 212ms 5.1min 5.6min 0 transport_latency_assumed market_resolved g 3,089 465 193ms 7.0min 11.0min 11.5min 0 transport_latency_assumed market_resolved h 2,666 719 33ms 70ms 167ms 42.6s 0 transport_latency_assumed new_market c 1,920 1,357 119ms 4.3min 39.3min 2.4h 0 transport_latency_assumed new_market e 1,415 273 234ms 22.8s 1.5min 31.8min 0 transport_latency_assumed new_market f 1,509 337 258ms 50.6s 1.5min 1.2h 0 transport_latency_assumed new_market g 1,516 251 459ms 49.9s 19.2min 2.6h 0 transport_latency_assumed new_market h 1,418 421 173ms 18.7s 1.3min 1.4min 0 transport_latency_assumed price_change c 91,425,563 85,979,589 5ms 17ms 141ms 4.5s 0 transport_latency_assumed price_change e 118,003,766 2,104,772 41ms 67ms 454ms 15.6s 0 transport_latency_assumed price_change f 108,710,222 638,026 47ms 78ms 473ms 18.6s 0 transport_latency_assumed price_change g 104,750,213 36,358 85ms 142ms 1.2s 33.0s 0 transport_latency_assumed price_change h 117,992,164 29,279,767 18ms 39ms 282ms 54.0s 0 transport_latency_assumed tick_size_change c 4,044 3,967 5ms 9ms 51ms 247ms 0 transport_latency_assumed tick_size_change e 4,776 73 40ms 47ms 422ms 949ms 0 transport_latency_assumed tick_size_change f 4,572 16 46ms 70ms 411ms 781ms 0 transport_latency_assumed tick_size_change g 4,488 not meas. 83ms 102ms 766ms 1.2s 0 transport_latency_assumed tick_size_change h 4,776 720 18ms 33ms 320ms 6.3s 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-13/22/2026-09-13T22.parquet sha256sum 2026-09-13T22.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.