Hour audit: 2026-09-29T20
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-29T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T20:00:00.000000020+00:00 · last event 2026-09-29T20:59:59.999992371+00:00
VOLUME 101,513,667 rows · 1,137,010,510 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 101,155,636 · i: 101,153,836 · k: 101,121,158 · h: 100,952,879 · g: 100,609,472 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 88,602,422 (87.28%) · i: 1,696,054 (1.67%) · k: 9,263,207 (9.13%) · h: 1,853,192 (1.83%) · g: 98,792 (0.10%) (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 101,513,667 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8d5a5fe720698cdd4d261b9d4d8bad4d2c81e6c5e278fee30da80f5971cbd384
the corpus checksum ledger names this file with the same digest
joined 101,534,715 to merged 101,513,667, minus 21,048 (minus 0.0207%)
boundary drops 21,048 · 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-29T23:13:38Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,801,104 131,383,492 0-41 2d4d4678e6f5bae1a7fb575dfc522fa7f99d8528a2dfea0e3365c698589918b1 book 549,611 47,969,873 42-44 92dbc670753fdee982e91688280d865af8326fd3a30782a568a719ff32baafa9 last_trade_price 58,536 3,357,894 45-45 940bd54bc111e3c4ea09112e3cfe17a5f4488cf433d6c7fc8aeef26565b8df41 market_resolved 1,816 274,369 46-46 3ec9aba7eaa0ccaca80187d389f71f4d3468146671998c9dac22b57c6c1efd0d new_market 2,904 321,564 47-47 bd4ea899a39de5a6fd577f3cb49ea9fcb8891ee7ddf89c3d4742d8616dc2d017 price_change 90,092,476 952,281,380 48-391 8234d541c1474d5459af52a4206de34dad8fc03d79014ab580418d79b7deb7b5 tick_size_change 7,220 262,069 392-392 f72171f43fc7df5c1b87d024034b937fccc4598649857eb45821dbb2693e1cf2 EVENT MIX count share price_change 90,092,476 88.75% best_bid_ask 10,801,104 10.64% book 549,611 0.54% last_trade_price 58,536 0.06% tick_size_change 7,220 <0.01% new_market 2,904 <0.01% market_resolved 1,816 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,803,862 10,801,104 2,758 184 FULL book 549,639 549,611 28 157,520 FULL last_trade_price 58,544 58,536 8 13 FULL market_resolved 1,816 1,816 0 1 FULL new_market 2,904 2,904 0 0 FULL price_change 90,110,730 90,092,476 18,254 327 FULL tick_size_change 7,220 7,220 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,799,182 9,519,466 6ms 23ms 356ms 24.6s 0 transport_latency_assumed best_bid_ask g 10,791,058 3,276 79ms 143ms 998ms 37.7s 0 transport_latency_assumed best_bid_ask h 10,785,821 182,187 20ms 55ms 1.4s 2.8min 0 transport_latency_assumed best_bid_ask i 10,798,334 159,190 21ms 36ms 354ms 1.2min 0 transport_latency_assumed best_bid_ask k 10,798,695 936,985 13ms 25ms 308ms 1.2min 0 transport_latency_assumed book c 250,556 198,025 5.1s 1.1d 37.0d 122.9d 0 book_staleness book g 202,200 65,671 976ms 18.7h 27.1d 122.9d 0 book_staleness book h 225,136 93,893 456ms 21.2h 34.3d 122.9d 0 book_staleness book i 252,383 101,675 5.9s 1.1d 35.1d 122.9d 0 book_staleness book k 218,363 90,347 89ms 20.7h 30.2d 122.9d 0 book_staleness last_trade_price c 58,267 50,861 7ms 37ms 535ms 6.4s 0 transport_latency_assumed last_trade_price g 56,761 9 93ms 1.6s 13.6s 38.2s 0 transport_latency_assumed last_trade_price h 57,974 947 22ms 162ms 2.7s 1.9min 0 transport_latency_assumed last_trade_price i 58,375 791 23ms 139ms 1.2s 20.9s 0 transport_latency_assumed last_trade_price k 58,265 5,928 14ms 48ms 421ms 1.0min 0 transport_latency_assumed market_resolved c 1,720 1,553 6ms 15ms 48.0s 48.1s 0 transport_latency_assumed market_resolved g 1,720 not meas. 80ms 277ms 52.4s 57.2s 0 transport_latency_assumed market_resolved h 1,719 20 20ms 84ms 55.4s 55.5s 0 transport_latency_assumed market_resolved i 1,720 142 21ms 95ms 51.6s 53.1s 0 transport_latency_assumed market_resolved k 1,720 101 14ms 50ms 53.2s 58.0s 0 transport_latency_assumed new_market c 2,085 881 481ms 32.5s 1.3min 2.1min 0 transport_latency_assumed new_market g 2,085 222 7.6s 32.3s 1.1min 2.1min 0 transport_latency_assumed new_market h 2,085 364 7.9s 33.9s 2.0min 2.2min 0 transport_latency_assumed new_market i 2,085 801 536ms 34.6s 2.0min 2.2min 0 transport_latency_assumed new_market k 2,085 636 474ms 34.2s 1.0min 1.5min 0 transport_latency_assumed price_change c 90,036,606 78,825,242 6ms 27ms 416ms 32.4s 0 transport_latency_assumed price_change g 89,548,428 29,614 80ms 237ms 5.2s 39.3s 0 transport_latency_assumed price_change h 89,872,928 1,575,666 20ms 77ms 1.8s 2.9min 0 transport_latency_assumed price_change i 90,033,719 1,433,358 21ms 49ms 523ms 1.2min 0 transport_latency_assumed price_change k 90,034,810 8,228,596 13ms 31ms 352ms 1.2min 0 transport_latency_assumed tick_size_change c 7,220 6,394 6ms 19ms 354ms 1.9s 0 transport_latency_assumed tick_size_change g 7,220 not meas. 79ms 137ms 622ms 2.0s 0 transport_latency_assumed tick_size_change h 7,216 115 20ms 46ms 565ms 14.2s 0 transport_latency_assumed tick_size_change i 7,220 97 21ms 41ms 274ms 623ms 0 transport_latency_assumed tick_size_change k 7,220 614 13ms 24ms 235ms 871ms 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-29/20/2026-09-29T20.parquet sha256sum 2026-09-29T20.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.