Hour audit: 2026-09-05T00
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-05T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T00:00:00.029778156+00:00 · last event 2026-09-05T00:59:59.999976771+00:00
VOLUME 113,445,987 rows · 1,176,580,853 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 112,533,600 · h: 112,521,857 · e: 112,515,614 · b: 103,588,106 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 100,135 (0.09%) · h: 137,219 (0.12%) · e: 112,514,301 (99.18%) · b: 694,332 (0.61%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 113,445,987 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 d0cbe7c423ac74f008c1fb5cd29246b706a1e212fc4318feee282565d8e06647
the corpus checksum ledger names this file with the same digest
joined 113,448,305 to merged 113,445,987, minus 2,318 (minus 0.0020%)
boundary drops 2,318 · 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-05T01:55:18Z as bceh
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 12,043,500 130,414,802 0-45 e9c450754055706f9075d798bcff9ab338154a30d42f0e5d99f7f337e1554c35 book 1,103,947 72,046,998 46-50 9a57b99c145099c0cf7e7a54ae5395cafc59c4f9cab874d3b1424d9f223e19b7 last_trade_price 47,570 2,731,293 51-51 0785093404a66256af6726fa634f98ddef36ba3cc22730170a3d0d6b0a95060a market_resolved 1,493 194,585 52-52 6dc8d6b955f981899883246d84952e25dca1f2dec27275c468d3c740fccee8d3 new_market 949 95,321 53-53 bfeb34e3172fb6ecaac8f9835c0336aeb4d893de61398452a51707f263162160 price_change 100,245,564 969,698,435 54-436 c518007d0f19c50d4a3df3441efa266f6f70acc3074efd3f7912e2643ac2369a tick_size_change 2,964 107,978 437-437 f1033f838b47255cb26ed606d45d97d71b70d4f2918c71adc86d529ba0ff2ce3 EVENT MIX count share price_change 100,245,564 88.36% best_bid_ask 12,043,500 10.62% book 1,103,947 0.97% last_trade_price 47,570 0.04% tick_size_change 2,964 <0.01% market_resolved 1,493 <0.01% new_market 949 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,043,692 12,043,500 192 1,377 FULL book 1,104,491 1,103,947 544 187,612 FULL last_trade_price 47,570 47,570 0 249 FULL market_resolved 1,493 1,493 0 1 FULL new_market 949 949 0 0 FULL price_change 100,247,146 100,245,564 1,582 670 FULL tick_size_change 2,964 2,964 0 75 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,978,285 72 55ms 68ms 183ms 4.1s 0 transport_latency_assumed best_bid_ask c 12,042,448 494 6ms 9ms 56ms 4.0s 0 transport_latency_assumed best_bid_ask e 12,040,852 12,040,717 39ms 47ms 189ms 2.2s 0 transport_latency_assumed best_bid_ask h 12,041,650 2,217 18ms 21ms 90ms 22.4s 0 transport_latency_assumed book b 912,213 693,139 2.7min 8.2h 33.4d 98.1d 0 book_staleness book c 217,063 95,058 9.6s 3.0h 27.3d 98.1d 0 book_staleness book e 208,223 208,137 5.2s 3.0h 24.2d 98.1d 0 book_staleness book h 219,075 107,613 10.2s 3.1h 26.2d 98.1d 0 book_staleness last_trade_price b 41,966 not meas. 62ms 149ms 1.7s 5.0s 0 transport_latency_assumed last_trade_price c 47,532 6 11ms 39ms 228ms 5.0s 0 transport_latency_assumed last_trade_price e 47,532 47,532 45ms 100ms 797ms 5.0s 0 transport_latency_assumed last_trade_price h 47,539 32 23ms 55ms 348ms 10.2s 0 transport_latency_assumed market_resolved b 1,412 269 58ms 7.1min 12.1min 12.6min 0 transport_latency_assumed market_resolved c 1,200 3 6ms 12ms 56.2s 57.7s 0 transport_latency_assumed market_resolved e 1,200 1,200 40ms 132ms 1.3s 1.0min 0 transport_latency_assumed market_resolved h 1,200 21 18ms 87ms 1.0min 1.0min 0 transport_latency_assumed new_market b 642 106 182ms 19.4s 9.2min 9.2min 0 transport_latency_assumed new_market c 605 82 69ms 14.7s 20.6s 1.1min 0 transport_latency_assumed new_market e 605 605 132ms 12.3s 22.0s 1.6min 0 transport_latency_assumed new_market h 605 156 102ms 14.6s 21.2s 1.9min 0 transport_latency_assumed price_change b 91,650,924 746 55ms 69ms 219ms 4.1s 0 transport_latency_assumed price_change c 100,221,788 4,492 6ms 10ms 66ms 4.2s 0 transport_latency_assumed price_change e 100,214,238 100,213,146 40ms 52ms 209ms 2.3s 0 transport_latency_assumed price_change h 100,208,824 27,180 18ms 23ms 108ms 28.2s 0 transport_latency_assumed tick_size_change b 2,664 not meas. 55ms 68ms 185ms 477ms 0 transport_latency_assumed tick_size_change c 2,964 not meas. 6ms 9ms 74ms 233ms 0 transport_latency_assumed tick_size_change e 2,964 2,964 40ms 63ms 193ms 349ms 0 transport_latency_assumed tick_size_change h 2,964 not meas. 18ms 22ms 85ms 3.7s 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-05/00/2026-09-05T00.parquet sha256sum 2026-09-05T00.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.