Hour audit: 2026-09-12T21
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-12T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T21:00:00.000302892+00:00 · last event 2026-09-12T21:59:59.999828698+00:00
VOLUME 128,617,641 rows · 1,425,792,990 bytes (1.33 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 123,513,226 · e: 123,503,417 · f: 118,505,133 · g: 117,993,259 · c: 53,992,900 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 72,032,216 (56.00%) · e: 3,852,379 (3.00%) · f: 999,513 (0.78%) · g: 140,403 (0.11%) · c: 51,593,130 (40.11%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 8b3a3d35c274d8eb028f080636fecc29c54fed3c8ef7a8d6722a17a6b640763e
the corpus checksum ledger names this file with the same digest
joined 128,636,050 to merged 128,617,641, minus 18,409 (minus 0.0143%)
boundary drops 18,409 · 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-12T23:00:17Z 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 12,291,482 139,714,595 0-46 533f066bc00a908aced1098eac78dce5b3509e4753416cad3219a030c7185b5f book 5,181,675 137,558,942 47-66 079c5f7dab37076844a7f7c9517cafbab8dd96b88cdba094eb91d51ebf0c76ea last_trade_price 68,983 3,839,441 67-67 6a4cd2d2121e26247ae9a8b66d725c5f711b9834bd8028a774d5b072b0f88788 market_resolved 17,614 1,282,451 68-68 17ce542c88d81be5e3a6892eb213335bfc1b60cdffcc55af3f86faa160ec9a28 new_market 36,869 1,226,054 69-69 3c9733b1028fbfdcd89a573b79affd7266266764671289b7c64179e9e6065863 price_change 111,015,802 1,140,515,954 70-493 12ee591131f7ae7a088de2a76d8718ecd5097b26d9a2fb0d0ece476075295dfe tick_size_change 5,216 194,074 494-494 471c518fb0fde3289539e846f96fa1e104a9ead0c6e97724383823183e39e3a3 EVENT MIX count share price_change 111,015,802 86.31% best_bid_ask 12,291,482 9.56% book 5,181,675 4.03% last_trade_price 68,983 0.05% new_market 36,869 0.03% market_resolved 17,614 0.01% tick_size_change 5,216 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,291,718 12,291,482 236 22,467 FULL book 5,197,481 5,181,675 15,806 195,544 FULL last_trade_price 68,984 68,983 1 1,716 FULL market_resolved 17,614 17,614 0 3,886 FULL new_market 36,869 36,869 0 5,348 FULL price_change 111,018,168 111,015,802 2,366 24,424 FULL tick_size_change 5,216 5,216 0 780 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 4,897,456 4,671,628 6ms 14ms 145ms 5.1s 0 transport_latency_assumed best_bid_ask e 12,287,285 369,217 40ms 46ms 248ms 12.7s 0 transport_latency_assumed best_bid_ask f 11,757,055 80,513 45ms 54ms 272ms 7.7s 0 transport_latency_assumed best_bid_ask g 11,708,888 8,700 77ms 103ms 610ms 34.2s 0 transport_latency_assumed best_bid_ask h 12,288,707 7,161,424 18ms 29ms 334ms 46.5s 0 transport_latency_assumed book c 4,961,820 4,876,715 14.4min 1.2d 35.1d 106.0d 0 book_staleness book e 148,932 8,812 43ms 226ms 11.2s 87.4d 0 book_staleness book f 536,662 145,578 2.4min 20.0h 25.2d 106.0d 0 book_staleness book g 547,600 56,465 3.2min 20.3h 28.1d 106.0d 0 book_staleness book h 150,188 94,105 22ms 79ms 36.7s 87.3d 0 book_staleness last_trade_price c 22,513 21,154 12ms 47ms 305ms 4.6s 0 transport_latency_assumed last_trade_price e 68,283 2,633 47ms 168ms 5.2s 12.7s 0 transport_latency_assumed last_trade_price f 65,462 810 53ms 214ms 3.4s 7.7s 0 transport_latency_assumed last_trade_price g 61,861 50 96ms 1.3s 16.2s 34.1s 0 transport_latency_assumed last_trade_price h 68,622 44,336 24ms 73ms 606ms 11.9s 0 transport_latency_assumed market_resolved c 15,288 15,178 23.1min 1.2h 1.5h 1.6h 0 transport_latency_assumed market_resolved e 3,960 128 110ms 192ms 613ms 35.8s 0 transport_latency_assumed market_resolved f 3,901 146 115ms 205ms 4.3min 4.6min 0 transport_latency_assumed market_resolved g 3,747 16 198ms 358ms 37.6s 5.6min 0 transport_latency_assumed market_resolved h 3,960 2,146 37ms 75ms 1.2s 35.0s 0 transport_latency_assumed new_market c 36,230 34,958 32.2min 1.1h 1.8h 3.5h 0 transport_latency_assumed new_market e 1,710 433 239ms 23.2s 31.7s 44.6min 0 transport_latency_assumed new_market f 1,720 449 233ms 33.6s 4.0min 2.1h 0 transport_latency_assumed new_market g 1,711 245 337ms 22.1s 28.2s 55.0min 0 transport_latency_assumed new_market h 1,710 784 173ms 20.6s 29.1s 1.2h 0 transport_latency_assumed price_change c 44,057,385 41,971,441 6ms 14ms 150ms 7.7s 0 transport_latency_assumed price_change e 110,988,035 3,471,004 40ms 50ms 293ms 12.8s 0 transport_latency_assumed price_change f 106,135,421 771,946 45ms 58ms 317ms 7.7s 0 transport_latency_assumed price_change g 105,664,504 74,918 78ms 118ms 746ms 34.2s 0 transport_latency_assumed price_change h 110,994,823 64,726,493 18ms 32ms 333ms 50.4s 0 transport_latency_assumed tick_size_change c 2,208 2,056 7ms 16ms 51ms 251ms 0 transport_latency_assumed tick_size_change e 5,212 152 40ms 52ms 289ms 598ms 0 transport_latency_assumed tick_size_change f 4,912 71 45ms 84ms 360ms 534ms 0 transport_latency_assumed tick_size_change g 4,948 9 78ms 132ms 624ms 1.3s 0 transport_latency_assumed tick_size_change h 5,216 2,928 18ms 32ms 377ms 2.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-12/21/2026-09-12T21.parquet sha256sum 2026-09-12T21.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.