Hour audit: 2026-10-07T03
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-07T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T03:00:00.000023083+00:00 · last event 2026-10-07T03:59:59.999977544+00:00
VOLUME 112,148,934 rows · 1,244,368,861 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 111,991,105 · h: 111,958,898 · m: 111,945,162 · i: 111,938,202 · n: 111,918,842 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 56,715,168 (50.57%) · h: 556,900 (0.50%) · m: 54,373,989 (48.48%) · i: 450,311 (0.40%) · n: 52,566 (0.05%) (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 112,148,934 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5871f7843b7d7ceba0f8c376da77bc9bbea30236fc8ccb63623e9fae4ee88f3b
the corpus checksum ledger names this file with the same digest
joined 112,149,916 to merged 112,148,934, minus 982 (minus 0.0009%)
boundary drops 982 · 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-07T05:01:07Z as himno
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,372,746 140,335,509 0-43 23e3bd916bc50210c90ab7cf0affe16ca22569b1054fb6093780df01dd12626d book 258,346 25,686,739 44-44 6c2ad8a401f18884303bbf0eca16aa11efdd16afcfc44ae0a0cf58b16000c91d last_trade_price 43,906 2,509,672 45-45 948e31608d9c117337cef30614252e3cde7fd85ab48913def06150969f098054 market_resolved 1,084 174,710 46-46 f855e3cc65ca2b3fbba0ced526bb64e54e3cce84a54afb45eee3457a18af65dc new_market 1,090 104,857 47-47 92f43b8b29cf1555ddc78d5c1d01e250db096c28ca6dd2bb99f5b22adc269ded price_change 100,469,290 1,074,186,345 48-431 f03229b55bfb2216e006ae2181934219751b32c5ae8ab358011ec2925f96767b tick_size_change 2,472 91,818 432-432 5de4c412335405d5c9e5285f28e36e59c69a2c36d55f4d341aa55f7aacdc4229 EVENT MIX count share price_change 100,469,290 89.59% best_bid_ask 11,372,746 10.14% book 258,346 0.23% last_trade_price 43,906 0.04% tick_size_change 2,472 <0.01% new_market 1,090 <0.01% market_resolved 1,084 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,372,836 11,372,746 90 63 FULL book 258,346 258,346 0 73,096 FULL last_trade_price 43,906 43,906 0 0 FULL market_resolved 1,084 1,084 0 0 FULL new_market 1,090 1,090 0 0 FULL price_change 100,470,182 100,469,290 892 38 FULL tick_size_change 2,472 2,472 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,371,757 49,697 18ms 26ms 175ms 36.3s 0 transport_latency_assumed best_bid_ask i 11,370,932 35,790 21ms 28ms 96ms 4.1s 0 transport_latency_assumed best_bid_ask m 11,371,207 5,514,138 4ms 11ms 66ms 5.8s 0 transport_latency_assumed best_bid_ask n 11,371,500 2,432 43ms 53ms 153ms 4.8s 0 transport_latency_assumed best_bid_ask o 11,372,004 5,770,689 4ms 11ms 66ms 8.4s 0 transport_latency_assumed book h 101,184 11,734 22ms 51.6s 5.1d 111.7d 0 book_staleness book i 139,670 49,426 31ms 9.9h 31.5d 130.2d 0 book_staleness book m 138,793 85,925 10ms 9.9h 31.6d 130.2d 0 book_staleness book n 113,483 22,590 47ms 2.4h 27.8d 130.2d 0 book_staleness book o 134,689 88,671 9ms 8.6h 29.7d 111.7d 0 book_staleness last_trade_price h 43,849 308 19ms 46ms 361ms 35.0s 0 transport_latency_assumed last_trade_price i 43,742 224 22ms 58ms 541ms 1.7s 0 transport_latency_assumed last_trade_price m 43,758 19,874 6ms 17ms 125ms 1.7s 0 transport_latency_assumed last_trade_price n 43,849 29 46ms 101ms 451ms 2.5s 0 transport_latency_assumed last_trade_price o 43,798 23,471 5ms 17ms 155ms 1.7s 0 transport_latency_assumed market_resolved h 1,036 2 20ms 127ms 51.3s 57.9s 0 transport_latency_assumed market_resolved i 1,036 69 22ms 85ms 48.3s 54.9s 0 transport_latency_assumed market_resolved m 1,036 504 5ms 38ms 48.4s 54.9s 0 transport_latency_assumed market_resolved n 1,036 16 45ms 119ms 40.6s 40.6s 0 transport_latency_assumed market_resolved o 1,036 493 5ms 17ms 46.5s 47.4s 0 transport_latency_assumed new_market h 672 119 173ms 13.7s 53.6s 1.8min 0 transport_latency_assumed new_market i 672 162 78ms 31.2s 48.6s 1.3min 0 transport_latency_assumed new_market m 672 388 70ms 17.6s 56.6s 1.7min 0 transport_latency_assumed new_market n 672 129 205ms 30.4s 57.7s 1.8min 0 transport_latency_assumed new_market o 672 292 68ms 32.9s 50.4s 1.7min 0 transport_latency_assumed price_change h 100,437,928 495,032 18ms 29ms 246ms 36.5s 0 transport_latency_assumed price_change i 100,379,678 364,636 21ms 31ms 175ms 4.2s 0 transport_latency_assumed price_change m 100,387,224 48,751,934 4ms 12ms 74ms 6.4s 0 transport_latency_assumed price_change n 100,385,830 27,370 44ms 57ms 269ms 5.1s 0 transport_latency_assumed price_change o 100,436,434 50,830,318 4ms 12ms 75ms 8.4s 0 transport_latency_assumed tick_size_change h 2,472 8 18ms 26ms 84ms 133ms 0 transport_latency_assumed tick_size_change i 2,472 4 21ms 28ms 111ms 135ms 0 transport_latency_assumed tick_size_change m 2,472 1,226 4ms 10ms 37ms 93ms 0 transport_latency_assumed tick_size_change n 2,472 not meas. 43ms 51ms 80ms 299ms 0 transport_latency_assumed tick_size_change o 2,472 1,234 4ms 11ms 40ms 91ms 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-07/03/2026-10-07T03.parquet sha256sum 2026-10-07T03.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.