Hour audit: 2026-09-05T11
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-05T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T11:00:00.052236655+00:00 · last event 2026-09-05T11:59:59.999998897+00:00
VOLUME 114,143,431 rows · 1,175,224,753 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 113,719,322 · h: 113,690,390 · f: 113,667,335 · g: 113,649,081 · c: 109,583,843 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 28,444 (0.02%) · h: 11,651 (0.01%) · f: 69,108 (0.06%) · g: 113,646,185 (99.56%) · c: 388,043 (0.34%) (rows of the merged file that came from it; these partition it)
7 product-machine pairs publish no supplied count; the figures above still sum to the file's 114,143,431 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 90977e3ba4011fa89a559c0dd67b4ae36d2a0350cf81f7d3a8d67aa829a9e100
the corpus checksum ledger names this file with the same digest
joined 114,146,363 to merged 114,143,431, minus 2,932 (minus 0.0026%)
boundary drops 2,932 · 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-05T21:47:34Z 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,141,192 113,443,574 0-38 5ad6f06a706332a119dca1b10707df46dbc36ccbb83bc73e3db1b9cc369fbc13 book 528,667 55,873,893 39-41 9aab26e11efeeb4b59f9ca90908d516c83462b23eaf698528622e7d1ee048df6 last_trade_price 58,304 3,349,852 42-42 d01d662e705365e8aacfec32fa0f94fef78e6ef7b061ed980216822926358684 market_resolved 628 102,004 43-43 eb3d1c0f9a60b27fc37899cf403a142ca1ff947234104771949f5e3e0c17690a new_market 1,162 115,714 44-44 d21fdbc865a313ba0b576d2fdb4dd98e1b2fe12591c6eb6c63b3f3fba7eb1f21 price_change 103,407,186 1,000,810,661 45-439 0b1771e860870103aafe8d86b0bd36833a46542f0f6fe1a603c8f34f740597d8 tick_size_change 6,292 227,710 440-440 7d5c1680feb65ab63e9d57245bc36d8f93259b9d3424f79c434b1e5d9787aa7e EVENT MIX count share price_change 103,407,186 90.59% best_bid_ask 10,141,192 8.88% book 528,667 0.46% last_trade_price 58,304 0.05% tick_size_change 6,292 <0.01% new_market 1,162 <0.01% market_resolved 628 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,141,420 10,141,192 228 626 FULL book 528,683 528,667 16 187,708 FULL last_trade_price 58,304 58,304 0 117 FULL market_resolved 628 628 0 5 FULL new_market 1,162 1,162 0 0 FULL price_change 103,409,874 103,407,186 2,688 334 FULL tick_size_change 6,292 6,292 0 18 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,735,257 497 35ms 70ms 110ms 4.7s 0 transport_latency_assumed best_bid_ask e 10,139,204 1,762 39ms 44ms 129ms 1.9s 0 transport_latency_assumed best_bid_ask f 10,135,863 5,216 48ms 59ms 266ms 3.4s 0 transport_latency_assumed best_bid_ask g 10,132,872 10,132,644 83ms 112ms 538ms 9.8s 0 transport_latency_assumed best_bid_ask h 10,139,653 1,073 17ms 22ms 110ms 12.6s 0 transport_latency_assumed book c 508,088 383,711 1.3min 10.0h 30.8d 98.5d 0 book_staleness book e 126,894 7,306 42ms 135ms 4.7h 80.0d 0 book_staleness book f 123,673 4,480 49ms 130ms 1.2h 29.6d 0 book_staleness book g 131,895 131,889 86ms 2.7s 10.6h 34.9d 0 book_staleness book h 120,850 1,281 21ms 41ms 2.7s 80.0d 0 book_staleness last_trade_price c 55,913 2 42ms 80ms 249ms 5.0s 0 transport_latency_assumed last_trade_price e 58,276 109 45ms 80ms 506ms 5.0s 0 transport_latency_assumed last_trade_price f 57,877 531 53ms 94ms 851ms 5.0s 0 transport_latency_assumed last_trade_price g 57,658 57,658 91ms 166ms 1.6s 9.8s 0 transport_latency_assumed last_trade_price h 58,170 4 22ms 51ms 303ms 5.8s 0 transport_latency_assumed market_resolved c 609 14 35ms 73ms 4.9min 4.9min 0 transport_latency_assumed market_resolved e 614 not meas. 40ms 197ms 503ms 539ms 0 transport_latency_assumed market_resolved f 614 not meas. 48ms 66ms 372ms 658ms 0 transport_latency_assumed market_resolved g 614 614 84ms 139ms 701ms 1.7s 0 transport_latency_assumed market_resolved h 614 not meas. 18ms 104ms 185ms 361ms 0 transport_latency_assumed new_market c 756 71 138ms 19.0s 5.7min 5.8min 0 transport_latency_assumed new_market e 746 149 178ms 18.7s 27.0s 2.0min 0 transport_latency_assumed new_market f 746 145 173ms 12.3s 34.6s 56.3s 0 transport_latency_assumed new_market g 746 746 294ms 13.6s 34.5s 56.9s 0 transport_latency_assumed new_market h 746 51 135ms 15.7s 26.5s 1.3min 0 transport_latency_assumed price_change c 99,277,000 3,748 35ms 71ms 131ms 6.5s 0 transport_latency_assumed price_change e 103,387,296 19,118 40ms 45ms 165ms 1.9s 0 transport_latency_assumed price_change f 103,342,270 58,736 48ms 66ms 296ms 3.4s 0 transport_latency_assumed price_change g 103,319,004 103,316,342 82ms 127ms 556ms 9.9s 0 transport_latency_assumed price_change h 103,364,065 9,242 18ms 23ms 138ms 13.0s 0 transport_latency_assumed tick_size_change c 6,220 not meas. 32ms 67ms 77ms 433ms 0 transport_latency_assumed tick_size_change e 6,292 not meas. 39ms 43ms 71ms 260ms 0 transport_latency_assumed tick_size_change f 6,292 not meas. 48ms 102ms 255ms 471ms 0 transport_latency_assumed tick_size_change g 6,292 6,292 84ms 183ms 492ms 2.3s 0 transport_latency_assumed tick_size_change h 6,292 not meas. 18ms 20ms 89ms 1.5s 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/11/2026-09-05T11.parquet sha256sum 2026-09-05T11.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.