Hour audit: 2026-09-30T03
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-30T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T03:00:00.000112065+00:00 · last event 2026-09-30T03:59:59.999891652+00:00
VOLUME 106,583,415 rows · 1,129,036,096 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 106,115,147 · k: 106,081,898 · m: 106,004,589 · g: 105,965,851 · i: 105,812,745 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 907,700 (0.85%) · k: 3,012,641 (2.83%) · m: 101,885,702 (95.59%) · g: 87,415 (0.08%) · i: 689,957 (0.65%) (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 106,583,415 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 3d4a33d70a68ee295950a3d4ee53e5eecf34ad43616acbeb8153d80c2f2154d3
the corpus checksum ledger names this file with the same digest
joined 106,585,807 to merged 106,583,415, minus 2,392 (minus 0.0022%)
boundary drops 2,392 · 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-30T15:05:52Z as ghikm
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 9,750,279 110,765,199 0-37 11ccc3c1c2a3cf089d07f81c7b8a0f3c4bd2ced682bd137c7921e0dd2e6a899e book 780,908 65,216,713 38-40 2ceb7e4451b31ac88c6a304a4867ae1d7c5a77292144fb906147d4b75d27b9ac last_trade_price 44,359 2,523,971 41-41 6515701509b0f4754516880827288570b9362357c73b9a32b4af5186b3219610 market_resolved 975 149,769 42-42 74bfd835a436b156abae0d8c27228623e425ca9cff29c4309000a10a9a7b887c new_market 572 61,350 43-43 886fb564d9def57aef6de6a0d80df371d1a42281defb3f4f71d9211f2be1d1bf price_change 96,004,286 949,025,746 44-410 e1f38c95cb9ae8aa1e5cbaddce0df01be86b15fa6b1dc977d14e850768292b5a tick_size_change 2,036 75,870 411-411 3df46de18153e3c7016703dc4645f53c1bcf483491110230880b32b2f46eecac EVENT MIX count share price_change 96,004,286 90.07% best_bid_ask 9,750,279 9.15% book 780,908 0.73% last_trade_price 44,359 0.04% tick_size_change 2,036 <0.01% market_resolved 975 <0.01% new_market 572 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,750,508 9,750,279 229 78 FULL book 781,102 780,908 194 214,755 FULL last_trade_price 44,360 44,359 1 1 FULL market_resolved 975 975 0 0 FULL new_market 572 572 0 0 FULL price_change 96,006,254 96,004,286 1,968 83 FULL tick_size_change 2,036 2,036 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,747,345 408 79ms 97ms 266ms 10.9s 0 transport_latency_assumed best_bid_ask h 9,744,864 49,070 17ms 23ms 105ms 46.7s 0 transport_latency_assumed best_bid_ask i 9,747,590 50,985 18ms 24ms 96ms 8.8s 0 transport_latency_assumed best_bid_ask k 9,747,335 236,388 13ms 22ms 91ms 12.0s 0 transport_latency_assumed best_bid_ask m 9,745,571 9,413,428 4ms 8ms 45ms 9.4s 0 transport_latency_assumed book g 231,480 82,147 1.5min 1.5d 38.6d 123.2d 0 book_staleness book h 449,772 255,557 33.5min 2.3d 38.6d 123.2d 0 book_staleness book i 99,179 7,768 20ms 2.5s 3.0d 104.7d 0 book_staleness book k 368,239 203,987 14.8min 1.9d 38.6d 123.2d 0 book_staleness book m 323,694 231,449 7.2min 1.7d 38.6d 123.2d 0 book_staleness last_trade_price g 44,172 1 87ms 229ms 1.6s 8.4s 0 transport_latency_assumed last_trade_price h 44,013 457 19ms 45ms 265ms 6.0s 0 transport_latency_assumed last_trade_price i 44,076 435 20ms 50ms 265ms 2.4s 0 transport_latency_assumed last_trade_price k 44,073 1,632 14ms 33ms 199ms 2.9s 0 transport_latency_assumed last_trade_price m 44,141 41,834 5ms 12ms 102ms 1.1s 0 transport_latency_assumed market_resolved g 930 20 80ms 215ms 51.5s 56.6s 0 transport_latency_assumed market_resolved h 930 2 18ms 62ms 50.4s 50.4s 0 transport_latency_assumed market_resolved i 930 80 19ms 112ms 52.0s 52.0s 0 transport_latency_assumed market_resolved k 930 17 14ms 45ms 42.6s 42.6s 0 transport_latency_assumed market_resolved m 930 856 4ms 12ms 49.2s 49.2s 0 transport_latency_assumed new_market g 390 33 230ms 11.5s 34.7s 1.5min 0 transport_latency_assumed new_market h 390 103 80ms 10.9s 32.7s 1.3min 0 transport_latency_assumed new_market i 390 107 87ms 11.7s 39.8s 1.7min 0 transport_latency_assumed new_market k 390 83 91ms 10.7s 31.3s 1.3min 0 transport_latency_assumed new_market m 390 246 44ms 11.2s 32.8s 1.7min 0 transport_latency_assumed price_change g 95,939,498 4,806 79ms 111ms 474ms 12.4s 0 transport_latency_assumed price_change h 95,873,142 602,491 18ms 28ms 152ms 47.1s 0 transport_latency_assumed price_change i 95,918,544 630,577 18ms 28ms 154ms 9.3s 0 transport_latency_assumed price_change k 95,918,895 2,570,494 13ms 25ms 114ms 13.0s 0 transport_latency_assumed price_change m 95,887,827 92,195,918 4ms 9ms 62ms 9.5s 0 transport_latency_assumed tick_size_change g 2,036 not meas. 79ms 99ms 383ms 728ms 0 transport_latency_assumed tick_size_change h 2,036 20 18ms 25ms 344ms 763ms 0 transport_latency_assumed tick_size_change i 2,036 5 18ms 27ms 258ms 438ms 0 transport_latency_assumed tick_size_change k 2,036 40 13ms 23ms 203ms 405ms 0 transport_latency_assumed tick_size_change m 2,036 1,971 4ms 8ms 97ms 257ms 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-30/03/2026-09-30T03.parquet sha256sum 2026-09-30T03.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.