Hour audit: 2026-09-16T23
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-16T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T23:00:00.000099061+00:00 · last event 2026-09-16T23:59:59.999894794+00:00
VOLUME 124,028,237 rows · 1,304,879,359 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 123,263,735 · e: 123,260,591 · g: 119,095,924 · f: 118,450,077 · c: 116,210,272 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 12,708,953 (10.25%) · e: 456,912 (0.37%) · g: 380,231 (0.31%) · f: 270,362 (0.22%) · c: 110,211,779 (88.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 124,028,237 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 03d635e2b94e390c0db9d37c0946d028a45082ebdbdbe2f60e20430ab99e3d7e
the corpus checksum ledger names this file with the same digest
joined 124,031,758 to merged 124,028,237, minus 3,521 (minus 0.0028%)
boundary drops 3,521 · 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-17T01:01:13Z 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 14,744,088 164,980,730 0-56 32446f6e0e294d3b9ccf19d0c0b0f1cf0ae15f85604c7e3b7717f6f14b5fb0db book 828,158 65,372,087 57-60 5f7363c9de350be02f701ba0643ce660f283b9e7772b14d9ab31acaf519275ba last_trade_price 46,647 2,697,078 61-61 db578bad0dd445e103094cfa9e1b3a8643bf3d159a93f4d6868f96bbea13fa0e market_resolved 935 142,812 62-62 5e3648713587fb0b72d132639feab60ba3a7eb8d26fdee7dcd122822ead93758 new_market 948 98,767 63-63 f79412acbdd8f70c63251addbf82335ee760ca979e99cb9a85776b1f244906c6 price_change 108,403,997 1,070,047,756 64-477 610a11a04ef4d274e0292bd18638a4ae85e6459c75b163271a6ba686e2331278 tick_size_change 3,464 127,171 478-478 c22228af9519e81e92388d2a07ed4b0186d991f85690450700bd3a85f715ce9f EVENT MIX count share price_change 108,403,997 87.40% best_bid_ask 14,744,088 11.89% book 828,158 0.67% last_trade_price 46,647 0.04% tick_size_change 3,464 <0.01% new_market 948 <0.01% market_resolved 935 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,744,368 14,744,088 280 1,109 FULL book 829,452 828,158 1,294 175,992 FULL last_trade_price 46,648 46,647 1 171 FULL market_resolved 935 935 0 72 FULL new_market 948 948 0 12 FULL price_change 108,405,943 108,403,997 1,946 177 FULL tick_size_change 3,464 3,464 0 92 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,838,006 13,194,836 5ms 11ms 82ms 1.5s 0 transport_latency_assumed best_bid_ask e 14,742,344 46,643 40ms 48ms 148ms 12.1s 0 transport_latency_assumed best_bid_ask f 14,153,583 16,092 45ms 56ms 163ms 16.7s 0 transport_latency_assumed best_bid_ask g 14,228,846 1,593 80ms 99ms 273ms 21.8s 0 transport_latency_assumed best_bid_ask h 14,742,935 1,484,924 18ms 25ms 95ms 34.8s 0 transport_latency_assumed book c 563,010 310,172 2.7min 1.0d 36.2d 110.1d 0 book_staleness book e 122,877 24,470 45ms 7.6min 9.5d 110.1d 0 book_staleness book f 482,609 114,409 2.4min 21.2h 35.9d 110.0d 0 book_staleness book g 480,247 362,140 2.2min 20.7h 35.4d 110.0d 0 book_staleness book h 102,962 16,967 21ms 112ms 28.4min 91.5d 0 book_staleness last_trade_price c 43,700 40,850 10ms 50ms 234ms 4.8s 0 transport_latency_assumed last_trade_price e 46,526 260 51ms 219ms 4.4s 12.1s 0 transport_latency_assumed last_trade_price f 44,223 91 56ms 189ms 2.4s 16.7s 0 transport_latency_assumed last_trade_price g 44,703 21 95ms 235ms 2.3s 21.8s 0 transport_latency_assumed last_trade_price h 46,500 5,425 24ms 74ms 313ms 7.9s 0 transport_latency_assumed market_resolved c 896 870 5ms 26ms 5.8min 6.5min 0 transport_latency_assumed market_resolved e 884 1 112ms 195ms 365ms 50.8s 0 transport_latency_assumed market_resolved f 887 3 119ms 214ms 4.4min 5.3min 0 transport_latency_assumed market_resolved g 824 3 206ms 348ms 668ms 5.2min 0 transport_latency_assumed market_resolved h 884 58 37ms 73ms 196ms 48.4s 0 transport_latency_assumed new_market c 628 413 61ms 12.4s 1.7h 1.7h 0 transport_latency_assumed new_market e 616 131 166ms 23.6s 52.0s 1.2min 0 transport_latency_assumed new_market f 617 124 151ms 13.4s 24.7s 2.4min 0 transport_latency_assumed new_market g 616 66 226ms 19.1s 50.2s 8.5min 0 transport_latency_assumed new_market h 616 214 80ms 14.3s 50.5s 56.0s 0 transport_latency_assumed price_change c 101,760,800 96,661,526 5ms 13ms 94ms 2.2s 0 transport_latency_assumed price_change e 108,343,880 385,396 41ms 55ms 288ms 12.1s 0 transport_latency_assumed price_change f 103,764,882 139,642 46ms 62ms 251ms 16.8s 0 transport_latency_assumed price_change g 104,337,364 16,408 81ms 103ms 388ms 21.8s 0 transport_latency_assumed price_change h 108,366,374 11,201,025 18ms 28ms 122ms 37.6s 0 transport_latency_assumed tick_size_change c 3,232 3,112 5ms 8ms 99ms 192ms 0 transport_latency_assumed tick_size_change e 3,464 11 40ms 46ms 120ms 362ms 0 transport_latency_assumed tick_size_change f 3,276 1 45ms 53ms 166ms 523ms 0 transport_latency_assumed tick_size_change g 3,324 not meas. 79ms 95ms 253ms 611ms 0 transport_latency_assumed tick_size_change h 3,464 340 18ms 24ms 66ms 3.0s 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-16/23/2026-09-16T23.parquet sha256sum 2026-09-16T23.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.