Hour audit: 2026-10-03T15
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-03T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T15:00:00.000030630+00:00 · last event 2026-10-03T15:59:59.999952553+00:00
VOLUME 129,018,761 rows · 1,440,595,954 bytes (1.34 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 128,196,758 · h: 128,168,735 · i: 127,926,559 · k: 122,513,601 · g: 122,325,806 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 118,484,059 (91.83%) · h: 2,374,700 (1.84%) · i: 1,018,571 (0.79%) · k: 6,598,810 (5.11%) · g: 542,621 (0.42%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 a2c8b8a8885584e6b00fd4421889d61fb10111bdb27f239ce4b6cc848a505bfb
the corpus checksum ledger names this file with the same digest
joined 129,021,093 to merged 129,018,761, minus 2,332 (minus 0.0018%)
boundary drops 2,332 · 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-03T17:49:58Z 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 11,040,547 136,815,733 0-42 972942c420effa99dfaceddddbd32a3c9e4e5ef5335547f5b183fdbbb53e4851 book 860,976 74,467,132 43-46 ef9ac9f387a1db94b5e7229cc58b3d92b088a47f15d08e427b58d391ae65cb4a last_trade_price 60,025 3,576,048 47-47 66dea95d33faf94b3db62ae338c8362c1dd27d46deb271eb1a3f8ad4aef1adc0 market_resolved 1,326 180,009 48-48 2d31f5ed2e7f734f502d94de524fe3566332bd3176adaa111c04d8434229b589 new_market 4,061 368,772 49-49 f17a3bc0cc5ce9c3edfe504c9e39461b2d92cad9fc7fc7345f0a6d54218a5595 price_change 117,039,750 1,223,281,627 50-496 3ba918a2aae720fe020fa5f1712e275ea081f335a096e4225df761eb871b4bf8 tick_size_change 12,076 435,880 497-497 1ed6131b51788660b2d7148424d9944310eb3073194e093275e9e66ff86f0661 EVENT MIX count share price_change 117,039,750 90.72% best_bid_ask 11,040,547 8.56% book 860,976 0.67% last_trade_price 60,025 0.05% tick_size_change 12,076 <0.01% new_market 4,061 <0.01% market_resolved 1,326 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,040,778 11,040,547 231 1,630 FULL book 861,010 860,976 34 236,138 FULL last_trade_price 60,026 60,025 1 285 FULL market_resolved 1,326 1,326 0 0 FULL new_market 4,061 4,061 0 55 FULL price_change 117,041,816 117,039,750 2,066 1,336 FULL tick_size_change 12,076 12,076 0 231 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,517,022 1,766 80ms 116ms 654ms 34.5s 0 transport_latency_assumed best_bid_ask h 11,038,635 196,116 18ms 32ms 519ms 58.8s 0 transport_latency_assumed best_bid_ask i 11,031,584 81,001 22ms 34ms 266ms 49.6s 0 transport_latency_assumed best_bid_ask k 10,520,461 533,562 14ms 29ms 276ms 55.0s 0 transport_latency_assumed best_bid_ask m 11,039,354 10,228,102 5ms 14ms 123ms 5.3s 0 transport_latency_assumed book g 639,446 519,421 7.2min 1.6d 42.1d 126.7d 0 book_staleness book h 127,280 5,329 24ms 208ms 49.8min 108.2d 0 book_staleness book i 127,677 6,315 25ms 262ms 5.0h 105.2d 0 book_staleness book k 614,630 217,542 8.0min 1.6d 42.1d 126.7d 0 book_staleness book m 126,210 112,369 8ms 42ms 1.3min 65.0d 0 book_staleness last_trade_price g 56,688 9 84ms 374ms 5.7s 29.7s 0 transport_latency_assumed last_trade_price h 59,768 1,225 20ms 62ms 874ms 39.9s 0 transport_latency_assumed last_trade_price i 59,114 599 23ms 62ms 1.2s 10.2s 0 transport_latency_assumed last_trade_price k 57,086 4,083 15ms 40ms 412ms 9.1s 0 transport_latency_assumed last_trade_price m 59,936 54,109 6ms 21ms 197ms 4.0s 0 transport_latency_assumed market_resolved g 1,107 67 86ms 39.4s 5.6min 5.6min 0 transport_latency_assumed market_resolved h 1,107 48 20ms 110ms 58.3s 58.8s 0 transport_latency_assumed market_resolved i 1,107 92 24ms 180ms 47.2s 47.3s 0 transport_latency_assumed market_resolved k 1,107 173 17ms 1.2min 4.2min 5.8min 0 transport_latency_assumed market_resolved m 1,107 946 6ms 139ms 48.1s 48.2s 0 transport_latency_assumed new_market g 2,363 306 328ms 1.7min 5.3min 5.5min 0 transport_latency_assumed new_market h 2,339 642 183ms 1.3min 2.4min 3.1min 0 transport_latency_assumed new_market i 2,339 637 144ms 1.1min 2.3min 3.2min 0 transport_latency_assumed new_market k 2,284 836 178ms 1.8min 7.3min 7.6min 0 transport_latency_assumed new_market m 2,339 1,640 80ms 1.3min 2.7min 3.2min 0 transport_latency_assumed price_change g 111,097,572 21,044 80ms 152ms 1.6s 34.6s 0 transport_latency_assumed price_change h 116,927,530 2,171,100 19ms 36ms 631ms 58.9s 0 transport_latency_assumed price_change i 116,692,674 929,830 22ms 38ms 394ms 50.2s 0 transport_latency_assumed price_change k 111,306,401 5,842,048 14ms 32ms 304ms 55.2s 0 transport_latency_assumed price_change m 116,955,736 108,075,728 5ms 16ms 136ms 6.3s 0 transport_latency_assumed tick_size_change g 11,608 8 80ms 117ms 474ms 1.4s 0 transport_latency_assumed tick_size_change h 12,076 240 18ms 33ms 995ms 42.6s 0 transport_latency_assumed tick_size_change i 12,064 97 22ms 33ms 267ms 6.0s 0 transport_latency_assumed tick_size_change k 11,632 566 14ms 31ms 429ms 6.2s 0 transport_latency_assumed tick_size_change m 12,076 11,165 5ms 14ms 155ms 4.8s 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/15/2026-10-03T15.parquet sha256sum 2026-10-03T15.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.