Hour audit: 2026-09-18T11
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-18T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T11:00:00.000069547+00:00 · last event 2026-09-18T11:59:59.999974581+00:00
VOLUME 122,323,670 rows · 1,328,257,821 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 121,155,407 · h: 121,126,230 · e: 121,015,972 · f: 116,177,654 · c: 112,340,658 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 216,706 (0.18%) · h: 14,807,422 (12.11%) · e: 1,213,482 (0.99%) · f: 953,945 (0.78%) · c: 105,132,115 (85.95%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 122,323,670 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1aa01dda90cb5b6dd56314b5f679a11084b9173ee0c897027fe05da803781465
the corpus checksum ledger names this file with the same digest
joined 122,325,695 to merged 122,323,670, minus 2,025 (minus 0.0017%)
boundary drops 2,025 · 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-18T13:39:05Z 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,080,581 142,672,796 0-46 3ee03b85a53eaa1237a2b9219bcd0d02d450c199c08f46805975b916f7f123ea book 1,171,833 81,014,648 47-51 a530d8035cd3c43ad02123b478ba0ee4c144cf0d7da60bcd13deaa553f41e221 last_trade_price 57,784 3,337,939 52-52 9fdbf4b7b78e550fb7b5e9e88f87d8f2e9685ae40593aa9919428a2416ac9b2b market_resolved 541 86,866 53-53 d34ba0e63e08015e0fcb07d8dd1a98364ba4e112ad62f618049a8234b0e08007 new_market 2,717 286,056 54-54 cce66ee41e7b4268cb6415c77aa427d10a23cdfedd3a43b688c3bd7ba4f4e5b5 price_change 109,006,022 1,099,312,391 55-470 462a170cfb94c313fec35301d4a5eaf9319e7b10760181d7f3a3aac1530eed59 tick_size_change 4,192 155,268 471-471 dd248495c4545080379f1ddebbe993acf18ae621f6be25202a177e3ffcc5bea9 EVENT MIX count share price_change 109,006,022 89.11% best_bid_ask 12,080,581 9.88% book 1,171,833 0.96% last_trade_price 57,784 0.05% tick_size_change 4,192 <0.01% new_market 2,717 <0.01% market_resolved 541 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,080,822 12,080,581 241 1,870 FULL book 1,171,927 1,171,833 94 195,896 FULL last_trade_price 57,784 57,784 0 189 FULL market_resolved 541 541 0 11 FULL new_market 2,717 2,717 0 2 FULL price_change 109,007,712 109,006,022 1,690 947 FULL tick_size_change 4,192 4,192 0 53 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,206,755 10,540,492 5ms 15ms 217ms 3.7s 0 transport_latency_assumed best_bid_ask e 12,073,842 111,236 41ms 53ms 264ms 22.3s 0 transport_latency_assumed best_bid_ask f 11,559,111 45,584 48ms 62ms 284ms 22.8s 0 transport_latency_assumed best_bid_ask g 12,071,528 8,791 80ms 103ms 424ms 21.7s 0 transport_latency_assumed best_bid_ask h 12,075,015 1,374,478 18ms 34ms 338ms 42.2s 0 transport_latency_assumed book c 978,983 617,283 3.2min 10.5h 36.9d 111.6d 0 book_staleness book e 124,990 6,036 45ms 691ms 8.0min 93.0d 0 book_staleness book f 573,886 423,584 2.0min 6.5h 33.9d 111.6d 0 book_staleness book g 266,135 105,522 8.9s 31.7min 26.9d 111.5d 0 book_staleness book h 127,741 19,408 23ms 293ms 21.4min 93.0d 0 book_staleness last_trade_price c 52,601 49,377 11ms 53ms 369ms 5.0s 0 transport_latency_assumed last_trade_price e 57,100 911 53ms 341ms 7.6s 22.5s 0 transport_latency_assumed last_trade_price f 54,875 489 62ms 552ms 6.8s 22.8s 0 transport_latency_assumed last_trade_price g 57,022 143 97ms 322ms 6.8s 20.9s 0 transport_latency_assumed last_trade_price h 57,364 6,864 25ms 137ms 722ms 5.3s 0 transport_latency_assumed market_resolved c 485 457 5ms 18ms 4.7min 5.1min 0 transport_latency_assumed market_resolved e 496 5 42ms 191ms 4.0s 1.0min 0 transport_latency_assumed market_resolved f 501 27 49ms 265ms 5.9min 5.9min 0 transport_latency_assumed market_resolved g 496 not meas. 83ms 268ms 846ms 1.1s 0 transport_latency_assumed market_resolved h 496 52 19ms 71ms 234ms 880ms 0 transport_latency_assumed new_market c 1,872 1,429 72ms 20.8s 49.1s 4.3min 0 transport_latency_assumed new_market e 1,874 281 191ms 21.2s 38.9s 1.2min 0 transport_latency_assumed new_market f 1,874 287 157ms 21.5s 47.0s 4.0min 0 transport_latency_assumed new_market g 1,874 181 271ms 19.8s 34.4s 1.1min 0 transport_latency_assumed new_market h 1,874 539 161ms 22.6s 38.7s 1.2min 0 transport_latency_assumed price_change c 100,095,982 93,919,272 5ms 17ms 237ms 4.0s 0 transport_latency_assumed price_change e 108,753,478 1,094,995 41ms 70ms 841ms 22.5s 0 transport_latency_assumed price_change f 103,983,319 483,966 48ms 79ms 1.2s 23.0s 0 transport_latency_assumed price_change g 108,754,160 102,069 81ms 126ms 824ms 21.7s 0 transport_latency_assumed price_change h 108,859,548 13,405,720 18ms 41ms 425ms 43.0s 0 transport_latency_assumed tick_size_change c 3,980 3,805 5ms 13ms 112ms 291ms 0 transport_latency_assumed tick_size_change e 4,192 18 41ms 79ms 196ms 495ms 0 transport_latency_assumed tick_size_change f 4,088 8 48ms 66ms 198ms 8.6s 0 transport_latency_assumed tick_size_change g 4,192 not meas. 80ms 105ms 343ms 10.2s 0 transport_latency_assumed tick_size_change h 4,192 361 18ms 38ms 156ms 194ms 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-18/11/2026-09-18T11.parquet sha256sum 2026-09-18T11.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.