Hour audit: 2026-10-02T23
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-10-02T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T23:00:00.000262809+00:00 · last event 2026-10-02T23:59:59.999977522+00:00
VOLUME 108,545,101 rows · 1,138,188,901 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 108,461,282 · h: 108,453,094 · i: 108,447,983 · m: 108,425,383 · g: 108,325,643 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 3,521,983 (3.24%) · h: 916,390 (0.84%) · i: 490,592 (0.45%) · m: 103,588,507 (95.43%) · g: 27,629 (0.03%) (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 108,545,101 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 38e80d853e2dbcf6ec65627990e050528dcb8255f7d3fc964e547d92e71b214f
the corpus checksum ledger names this file with the same digest
joined 108,547,219 to merged 108,545,101, minus 2,118 (minus 0.0020%)
boundary drops 2,118 · 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-10-03T01:45:57Z 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 10,463,892 121,306,821 0-39 448c8432f9ac0a5b0b9c5397a627b7bfb70c5188ee6fae2b0bf26e0fb5b2983a book 167,477 16,812,080 40-40 ae4a9d3cb0e29d8c8995ad9f3a7d86fa003622d83e739beee603797eb4a9410a last_trade_price 48,839 2,761,956 41-41 13462c1e7a83855324267cb1f0339ad92bdd0092a4927e842ee3bfe52f79f5ac market_resolved 2,255 342,750 42-42 3e8679e5d055a713d9c87ebeab7a8a8c036366d2b3143d1d634da184962d99b8 new_market 1,398 132,185 43-43 d03af5293f7a772378c0c089ebc2bf48ecb594511769224d68838563ea8ff8bb price_change 97,857,248 995,449,552 44-417 feea4a89d9423fc541d249943f2898fe1ca57d4a5a09d4b8ccab6d0d15b7edfa tick_size_change 3,992 145,545 418-418 5534af374aa31819305988c71a9b8d46e847c1807dd0a461b24acfee5ed860f8 EVENT MIX count share price_change 97,857,248 90.15% best_bid_ask 10,463,892 9.64% book 167,477 0.15% last_trade_price 48,839 0.04% tick_size_change 3,992 <0.01% market_resolved 2,255 <0.01% new_market 1,398 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,464,164 10,463,892 272 131 FULL book 167,479 167,477 2 29,642 FULL last_trade_price 48,841 48,839 2 2 FULL market_resolved 2,255 2,255 0 0 FULL new_market 1,398 1,398 0 0 FULL price_change 97,859,090 97,857,248 1,842 155 FULL tick_size_change 3,992 3,992 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,462,240 857 80ms 97ms 352ms 11.4s 0 transport_latency_assumed best_bid_ask h 10,462,473 79,327 17ms 23ms 138ms 52.9s 0 transport_latency_assumed best_bid_ask i 10,462,814 37,614 20ms 26ms 104ms 14.8s 0 transport_latency_assumed best_bid_ask k 10,462,804 326,020 13ms 21ms 129ms 1.1min 0 transport_latency_assumed best_bid_ask m 10,462,436 10,020,074 4ms 9ms 55ms 5.5s 0 transport_latency_assumed book g 115,009 15,413 90ms 4.7min 7.0d 107.6d 0 book_staleness book h 106,449 8,832 21ms 206ms 23.0h 107.6d 0 book_staleness book i 111,342 13,319 23ms 15.0s 3.8d 107.6d 0 book_staleness book k 119,042 24,076 18ms 31.0min 20.4d 107.5d 0 book_staleness book m 113,241 105,837 7ms 1.0min 4.1d 55.4d 0 book_staleness last_trade_price g 48,784 31 84ms 298ms 4.3s 11.3s 0 transport_latency_assumed last_trade_price h 48,618 620 19ms 39ms 358ms 47.5s 0 transport_latency_assumed last_trade_price i 48,763 493 22ms 45ms 352ms 4.3s 0 transport_latency_assumed last_trade_price k 48,762 2,152 15ms 33ms 273ms 11.2s 0 transport_latency_assumed last_trade_price m 48,740 45,543 6ms 15ms 169ms 3.0s 0 transport_latency_assumed market_resolved g 2,134 21 82ms 420ms 53.7s 55.5s 0 transport_latency_assumed market_resolved h 2,134 82 18ms 770ms 48.9s 51.7s 0 transport_latency_assumed market_resolved i 2,134 229 22ms 23.9s 52.7s 1.0min 0 transport_latency_assumed market_resolved k 2,134 65 14ms 23.9s 53.4s 1.4min 0 transport_latency_assumed market_resolved m 2,134 1,858 5ms 24.3s 53.4s 55.9s 0 transport_latency_assumed new_market g 830 105 353ms 15.0s 12.1min 15.4min 0 transport_latency_assumed new_market h 830 267 156ms 26.2s 10.4min 12.4min 0 transport_latency_assumed new_market i 830 197 134ms 18.2s 45.7s 10.3min 0 transport_latency_assumed new_market k 830 171 216ms 20.6s 47.1s 1.5min 0 transport_latency_assumed new_market m 830 658 49ms 21.4s 53.3s 10.4min 0 transport_latency_assumed price_change g 97,692,654 11,202 80ms 104ms 631ms 11.6s 0 transport_latency_assumed price_change h 97,828,598 827,250 17ms 25ms 206ms 53.0s 0 transport_latency_assumed price_change i 97,818,108 438,732 20ms 28ms 191ms 14.9s 0 transport_latency_assumed price_change k 97,823,718 3,169,362 13ms 23ms 176ms 1.1min 0 transport_latency_assumed price_change m 97,794,010 93,410,702 5ms 10ms 65ms 5.7s 0 transport_latency_assumed tick_size_change g 3,992 not meas. 80ms 96ms 215ms 610ms 0 transport_latency_assumed tick_size_change h 3,992 12 17ms 24ms 57ms 270ms 0 transport_latency_assumed tick_size_change i 3,992 8 20ms 26ms 86ms 348ms 0 transport_latency_assumed tick_size_change k 3,992 137 13ms 20ms 105ms 435ms 0 transport_latency_assumed tick_size_change m 3,992 3,835 4ms 9ms 30ms 51ms 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-10-02/23/2026-10-02T23.parquet sha256sum 2026-10-02T23.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.