Hour audit: 2026-09-29T19
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-29T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T19:00:00.000029206+00:00 · last event 2026-09-29T19:59:59.999992617+00:00
VOLUME 115,551,181 rows · 1,343,327,627 bytes (1.25 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 113,715,886 · h: 113,461,964 · k: 108,633,850 · g: 107,236,481 · c: 101,510,023 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 5,736,839 (4.96%) · h: 4,403,493 (3.81%) · k: 17,610,741 (15.24%) · g: 139,532 (0.12%) · c: 87,660,576 (75.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 115,551,181 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d4fa93307be44ed30de1a435244d0b5667651d17c1d796fedfa223265f7d6136
the corpus checksum ledger names this file with the same digest
joined 115,557,349 to merged 115,551,181, minus 6,168 (minus 0.0053%)
boundary drops 6,168 · 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-29T22:13:22Z 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 11,386,310 140,642,922 0-43 3dbd7e6aac39cdabd48fc902d3e3f3ed006dd9148be91b060435f69155ca729f book 1,672,122 85,222,578 44-50 d2c386b60d330c839ad32ba3ec452c33b53155cc5fc95314702ae6609c55cbca last_trade_price 64,240 3,714,994 51-51 1a0a8c53a5d5e1798f1b477d0e893ec890e3ac5ac978ae4744d0c0452d2213c8 market_resolved 2,287 281,622 52-52 f4abc8f9ccc31fff71ae9899fa77ce45428998636f78b281ced0daad4bb552d6 new_market 5,300 499,421 53-53 e0bdcc16d57c975d5a6405e929f6b5ec53ab9f2cf61344fe6c092ce608e71c29 price_change 102,415,814 1,111,465,224 54-444 9835e794bc8f333e364e3eba4aa0670c8934ce40594c43b9b676f6154dc22a66 tick_size_change 5,108 184,639 445-445 3814df27402f4356fe81ffa1287abc4ed83257f4e8bb1cc268b57b1cfb047f72 EVENT MIX count share price_change 102,415,814 88.63% best_bid_ask 11,386,310 9.85% book 1,672,122 1.45% last_trade_price 64,240 0.06% new_market 5,300 <0.01% tick_size_change 5,108 <0.01% market_resolved 2,287 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,386,619 11,386,310 309 2,232 FULL book 1,675,840 1,672,122 3,718 230,629 FULL last_trade_price 64,241 64,240 1 311 FULL market_resolved 2,287 2,287 0 214 FULL new_market 5,340 5,300 40 661 FULL price_change 102,417,914 102,415,814 2,100 1,767 FULL tick_size_change 5,108 5,108 0 178 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,966,128 8,618,368 6ms 32ms 321ms 6.7s 0 transport_latency_assumed best_bid_ask g 10,762,874 5,018 80ms 181ms 1.7s 52.8s 0 transport_latency_assumed best_bid_ask h 11,360,826 445,027 22ms 101ms 3.4s 2.6min 0 transport_latency_assumed best_bid_ask i 11,375,298 570,151 21ms 52ms 470ms 1.3min 0 transport_latency_assumed best_bid_ask k 10,806,021 1,747,746 13ms 39ms 404ms 2.1min 0 transport_latency_assumed book c 1,484,491 1,432,750 1.5h 2.6d 38.2d 122.9d 0 book_staleness book g 648,954 88,837 32.5min 2.1d 38.2d 122.9d 0 book_staleness book h 208,797 34,722 115ms 12.9h 24.2d 122.9d 0 book_staleness book i 157,027 18,534 31ms 20.8min 3.8d 121.3d 0 book_staleness book k 649,831 97,279 28.3min 2.1d 38.2d 122.9d 0 book_staleness last_trade_price c 56,282 48,058 7ms 46ms 373ms 5.0s 0 transport_latency_assumed last_trade_price g 57,368 38 101ms 3.0s 28.7s 46.4s 0 transport_latency_assumed last_trade_price h 63,381 2,583 26ms 292ms 3.8s 1.6min 0 transport_latency_assumed last_trade_price i 63,440 3,099 25ms 275ms 1.9s 25.1s 0 transport_latency_assumed last_trade_price k 60,461 10,462 15ms 83ms 552ms 53.1s 0 transport_latency_assumed market_resolved c 2,136 1,872 9ms 20.8min 34.1min 34.6min 0 transport_latency_assumed market_resolved g 1,537 4 81ms 21.1s 51.2s 5.6min 0 transport_latency_assumed market_resolved h 1,541 14 24ms 30.4s 49.9s 51.5s 0 transport_latency_assumed market_resolved i 1,541 255 22ms 23.6s 46.9s 56.4s 0 transport_latency_assumed market_resolved k 1,530 142 14ms 23.5s 53.6s 5.2min 0 transport_latency_assumed new_market c 4,212 2,311 476ms 14.5min 28.1min 31.2min 0 transport_latency_assumed new_market g 2,710 653 558ms 58.4s 5.5min 6.3min 0 transport_latency_assumed new_market h 2,661 542 407ms 47.9s 1.0min 1.2min 0 transport_latency_assumed new_market i 2,661 979 303ms 50.0s 1.1min 1.8min 0 transport_latency_assumed new_market k 2,542 815 245ms 51.7s 4.7min 4.8min 0 transport_latency_assumed price_change c 89,992,258 77,553,142 6ms 34ms 328ms 6.7s 0 transport_latency_assumed price_change g 95,758,234 44,982 81ms 334ms 11.0s 52.9s 0 transport_latency_assumed price_change h 101,819,654 3,920,455 22ms 140ms 4.0s 2.6min 0 transport_latency_assumed price_change i 102,110,811 5,143,637 21ms 72ms 811ms 1.3min 0 transport_latency_assumed price_change k 97,108,705 15,753,598 14ms 45ms 433ms 2.1min 0 transport_latency_assumed tick_size_change c 4,516 4,075 5ms 14ms 165ms 228ms 0 transport_latency_assumed tick_size_change g 4,804 not meas. 78ms 94ms 371ms 696ms 0 transport_latency_assumed tick_size_change h 5,104 150 21ms 54ms 1.5s 31.3s 0 transport_latency_assumed tick_size_change i 5,108 184 21ms 37ms 326ms 2.7s 0 transport_latency_assumed tick_size_change k 4,760 699 13ms 19ms 46ms 495ms 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/19/2026-09-29T19.parquet sha256sum 2026-09-29T19.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.