Hour audit: 2026-10-03T13
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-03T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T13:00:00.000012588+00:00 · last event 2026-10-03T13:59:59.999982804+00:00
VOLUME 118,001,618 rows · 1,291,188,208 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 117,256,095 · h: 117,251,868 · i: 117,048,516 · k: 112,246,171 · g: 111,911,589 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 109,297,808 (92.62%) · h: 1,399,531 (1.19%) · i: 750,275 (0.64%) · k: 6,034,344 (5.11%) · g: 519,660 (0.44%) (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 118,001,618 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fec59ef7dee1d8d9015a33a9a2ab703293919b4a823d4f6b13c4d9efaa169a3d
the corpus checksum ledger names this file with the same digest
joined 118,003,748 to merged 118,001,618, minus 2,130 (minus 0.0018%)
boundary drops 2,130 · 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-03T15:48:16Z 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,860,326 120,690,329 0-37 af93d0a86b49bb018ec654e4b609c2ba96aaae625e9b954b4aefd9ac8ebbea52 book 750,548 69,880,332 38-40 880409554c9cc2cf5930f964aa6b76b4a46ca257540a1ec1936e0a0e36412a73 last_trade_price 57,265 3,372,437 41-41 3485e369fe0d30c4c966ba3695300e26b0d4e1cfc863481b1a5669c127f10110 market_resolved 981 157,988 42-42 8b9b2ae8b6336c1c5a039a6f142927e7907bb3e1c0fc478cf6f10c9465425561 new_market 3,770 340,964 43-43 488bce3746e8dfb4303dea788863d9f625fcffd4f28055e28fca7ec78556638f price_change 107,323,660 1,095,218,266 44-453 6fbb48c8ff6ffbb68a9b5a94322149c998261fc47a3c0061f35451a8a4a2bb5c tick_size_change 5,068 183,316 454-454 7f9f0f794b6925011ca1b7b69bbf11ed9fe3acfe77ee9eb28f1c4c51c0ad8ad6 EVENT MIX count share price_change 107,323,660 90.95% best_bid_ask 9,860,326 8.36% book 750,548 0.64% last_trade_price 57,265 0.05% tick_size_change 5,068 <0.01% new_market 3,770 <0.01% market_resolved 981 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,860,520 9,860,326 194 762 FULL book 750,566 750,548 18 233,738 FULL last_trade_price 57,265 57,265 0 171 FULL market_resolved 981 981 0 16 FULL new_market 3,770 3,770 0 378 FULL price_change 107,325,578 107,323,660 1,918 915 FULL tick_size_change 5,068 5,068 0 54 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,414,476 1,498 79ms 101ms 549ms 19.3s 0 transport_latency_assumed best_bid_ask h 9,858,865 107,852 18ms 29ms 469ms 1.2min 0 transport_latency_assumed best_bid_ask i 9,852,533 57,844 21ms 31ms 277ms 8.5s 0 transport_latency_assumed best_bid_ask k 9,424,100 475,298 13ms 24ms 215ms 32.9s 0 transport_latency_assumed best_bid_ask m 9,859,162 9,217,834 5ms 12ms 126ms 5.6s 0 transport_latency_assumed book g 606,740 492,360 7.4min 1.5d 42.0d 126.6d 0 book_staleness book h 121,856 5,164 23ms 139ms 2.6h 108.1d 0 book_staleness book i 131,626 11,539 25ms 5.2s 1.5d 108.1d 0 book_staleness book k 604,213 129,753 7.3min 1.5d 42.0d 126.6d 0 book_staleness book m 128,803 111,732 7ms 2.0s 1.0d 126.6d 0 book_staleness last_trade_price g 53,734 57 82ms 229ms 3.6s 19.5s 0 transport_latency_assumed last_trade_price h 57,198 931 20ms 48ms 660ms 51.6s 0 transport_latency_assumed last_trade_price i 56,553 477 23ms 58ms 745ms 6.3s 0 transport_latency_assumed last_trade_price k 53,752 3,826 14ms 32ms 289ms 8.2s 0 transport_latency_assumed last_trade_price m 57,098 51,974 6ms 18ms 200ms 4.3s 0 transport_latency_assumed market_resolved g 912 not meas. 82ms 419ms 45.3s 5.0min 0 transport_latency_assumed market_resolved h 928 29 20ms 88ms 46.1s 46.1s 0 transport_latency_assumed market_resolved i 928 116 22ms 15.6s 56.1s 1.1min 0 transport_latency_assumed market_resolved k 928 83 14ms 18.0s 3.3min 5.3min 0 transport_latency_assumed market_resolved m 928 753 6ms 15.6s 49.2s 57.3s 0 transport_latency_assumed new_market g 2,018 481 338ms 5.1min 5.8min 6.0min 0 transport_latency_assumed new_market h 2,141 687 263ms 1.1min 1.5min 1.7min 0 transport_latency_assumed new_market i 2,132 831 185ms 1.1min 1.5min 1.7min 0 transport_latency_assumed new_market k 1,877 682 209ms 1.2min 5.9min 6.3min 0 transport_latency_assumed new_market m 2,132 1,089 134ms 1.1min 1.5min 1.7min 0 transport_latency_assumed price_change g 101,828,797 25,264 79ms 117ms 945ms 19.5s 0 transport_latency_assumed price_change h 107,205,812 1,284,810 19ms 32ms 569ms 1.2min 0 transport_latency_assumed price_change i 106,999,676 679,460 21ms 35ms 384ms 8.6s 0 transport_latency_assumed price_change k 102,156,449 5,424,488 13ms 25ms 239ms 35.3s 0 transport_latency_assumed price_change m 107,202,904 99,909,638 5ms 13ms 136ms 6.9s 0 transport_latency_assumed tick_size_change g 4,912 not meas. 79ms 94ms 192ms 2.5s 0 transport_latency_assumed tick_size_change h 5,068 58 18ms 26ms 356ms 14.7s 0 transport_latency_assumed tick_size_change i 5,068 8 21ms 29ms 199ms 4.2s 0 transport_latency_assumed tick_size_change k 4,852 214 13ms 20ms 38ms 657ms 0 transport_latency_assumed tick_size_change m 5,068 4,788 5ms 11ms 46ms 278ms 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-03/13/2026-10-03T13.parquet sha256sum 2026-10-03T13.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.