Hour audit: 2026-09-07T19
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-07T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T19:00:00.000033909+00:00 · last event 2026-09-07T19:59:59.999939729+00:00
VOLUME 101,848,645 rows · 1,090,467,777 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 100,881,258 · f: 100,465,407 · g: 100,305,628 · e: 98,249,977 · c: 88,588,175 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 14,408,224 (14.15%) · f: 605,442 (0.59%) · g: 48,014 (0.05%) · e: 1,706,455 (1.68%) · c: 85,080,510 (83.54%) (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 101,848,645 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 02e865a5c6efc63508dd334e37bad483e36120ac636baa54443e00eedfc4f6ff
the corpus checksum ledger names this file with the same digest
joined 101,852,587 to merged 101,848,645, minus 3,942 (minus 0.0039%)
boundary drops 3,942 · 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-07T20:57:20Z 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 10,824,534 117,096,456 0-41 a950fc553e52e12f465264e0c0a69f4df182852975ca17c2cf69e057ba87900c book 1,461,598 80,002,836 42-47 a44aae9cfb001917b376eca36e426afd16df46ee99f0916a7db356e3930331b3 last_trade_price 54,932 3,145,409 48-48 b8dadac1e4f4aeef17c2e014e2694a54e7cd884bae01ade8335f6ad9e710dc78 market_resolved 1,904 271,984 49-49 a329e3a62d96a974528b3bb8a56a2fc36244638461ba8c4ba19184101519b960 new_market 5,199 379,960 50-50 d5d8cc315e5bf3cdb2b2855c1267a718f68992f1a803a4afdc9172bfe0d37ae6 price_change 89,495,210 888,218,664 51-392 6289d5c9b94f22854f3f8a789c4e9935adb090be8bc0538edc044ae5b1758d53 tick_size_change 5,268 190,838 393-393 e52e59e332cc21dfcc331cef1720fd79648f4e5004a84c300afba01dfd9004ea EVENT MIX count share price_change 89,495,210 87.87% best_bid_ask 10,824,534 10.63% book 1,461,598 1.44% last_trade_price 54,932 0.05% tick_size_change 5,268 <0.01% new_market 5,199 <0.01% market_resolved 1,904 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,824,790 10,824,534 256 3,522 FULL book 1,461,986 1,461,598 388 179,934 FULL last_trade_price 54,934 54,932 2 311 FULL market_resolved 1,904 1,904 0 98 FULL new_market 5,199 5,199 0 0 FULL price_change 89,498,506 89,495,210 3,296 3,746 FULL tick_size_change 5,268 5,268 0 270 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,439,496 9,076,426 5ms 10ms 129ms 8.6s 0 transport_latency_assumed best_bid_ask e 10,664,470 194,381 39ms 47ms 309ms 8.8s 0 transport_latency_assumed best_bid_ask f 10,820,664 62,255 45ms 57ms 345ms 7.6s 0 transport_latency_assumed best_bid_ask g 10,813,682 4,237 82ms 116ms 747ms 41.5s 0 transport_latency_assumed best_bid_ask h 10,815,014 1,487,235 17ms 29ms 372ms 50.0s 0 transport_latency_assumed book c 1,206,930 1,198,832 25.5min 10.9h 31.1d 100.9d 0 book_staleness book e 110,617 4,399 42ms 286ms 46.0s 82.2d 0 book_staleness book f 117,257 2,950 48ms 246ms 6.1s 82.2d 0 book_staleness book g 128,077 7,483 93ms 15.1s 11.0h 82.3d 0 book_staleness book h 576,455 247,934 9.4min 10.1h 30.2d 100.9d 0 book_staleness last_trade_price c 46,880 44,697 10ms 40ms 206ms 5.0s 0 transport_latency_assumed last_trade_price e 51,469 747 45ms 169ms 3.9s 8.9s 0 transport_latency_assumed last_trade_price f 54,890 457 52ms 172ms 3.0s 7.7s 0 transport_latency_assumed last_trade_price g 54,278 35 98ms 385ms 12.6s 41.5s 0 transport_latency_assumed last_trade_price h 54,878 8,996 23ms 77ms 666ms 36.3s 0 transport_latency_assumed market_resolved c 1,747 1,710 5ms 6.1min 14.9min 15.8min 0 transport_latency_assumed market_resolved e 1,668 42 40ms 179ms 50.0s 2.4min 0 transport_latency_assumed market_resolved f 1,694 2 47ms 185ms 28.7s 57.1s 0 transport_latency_assumed market_resolved g 1,694 4 87ms 260ms 847ms 1.4s 0 transport_latency_assumed market_resolved h 1,690 146 19ms 60ms 277ms 1.2s 0 transport_latency_assumed new_market c 4,327 2,975 4.3min 11.4min 12.4min 12.6min 0 transport_latency_assumed new_market e 2,229 527 226ms 26.0s 1.1min 1.9min 0 transport_latency_assumed new_market f 2,229 295 252ms 28.3s 59.7s 1.2min 0 transport_latency_assumed new_market g 2,229 411 380ms 29.8s 1.0min 1.2min 0 transport_latency_assumed new_market h 2,229 991 163ms 20.3s 1.1min 1.5min 0 transport_latency_assumed price_change c 77,884,515 74,751,766 5ms 11ms 136ms 9.0s 0 transport_latency_assumed price_change e 87,414,364 1,506,338 39ms 55ms 418ms 9.2s 0 transport_latency_assumed price_change f 89,463,405 539,468 45ms 65ms 441ms 8.6s 0 transport_latency_assumed price_change g 89,300,400 35,844 82ms 145ms 1.1s 41.5s 0 transport_latency_assumed price_change h 89,425,724 12,661,794 18ms 33ms 383ms 50.0s 0 transport_latency_assumed tick_size_change c 4,280 4,104 5ms 10ms 108ms 351ms 0 transport_latency_assumed tick_size_change e 5,160 21 39ms 47ms 197ms 450ms 0 transport_latency_assumed tick_size_change f 5,268 15 45ms 57ms 204ms 313ms 0 transport_latency_assumed tick_size_change g 5,268 not meas. 81ms 106ms 416ms 7.5s 0 transport_latency_assumed tick_size_change h 5,268 1,128 17ms 25ms 79ms 9.6s 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-07/19/2026-09-07T19.parquet sha256sum 2026-09-07T19.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.