Hour audit: 2026-10-04T12
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-04T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T12:00:00.000242011+00:00 · last event 2026-10-04T12:59:59.999943715+00:00
VOLUME 106,773,669 rows · 1,190,732,869 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 106,689,396 · o: 106,687,522 · i: 106,660,183 · h: 106,633,446 · n: 106,622,712 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 54,974,514 (51.49%) · o: 50,829,607 (47.61%) · i: 308,763 (0.29%) · h: 590,828 (0.55%) · n: 69,957 (0.07%) (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 106,773,669 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a1fd0c08d97d4aa12fb0098637f6624f509d7bab9a2e2d63678c4066b631f250
the corpus checksum ledger names this file with the same digest
joined 106,774,633 to merged 106,773,669, minus 964 (minus 0.0009%)
boundary drops 964 · 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-04T13:59:56Z 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 8,727,762 111,905,043 0-33 98a83614684169456a29ac411b2acd430367d29c6061ddc13cf8aed1a552d9f6 book 142,421 15,223,757 34-34 84282524a1d272e98fa65d01be652c83ede13e7dc8305a23df246bfa0c1e82b9 last_trade_price 59,916 3,452,386 35-35 cebc89b00036e51268fbe422e794bc3c22b275cfe45edfc37594785da0e98316 market_resolved 857 138,447 36-36 7180ec2085f24927f30b8d9aded7abe594cc482f710a230984fbc573209ef83b new_market 3,035 280,578 37-37 6ceec2e121f85bffa927fa3d0257ae61ef026ddd9f656460037bd400b6e4c69c price_change 97,835,874 1,058,371,095 38-411 c40d438bab81e3441045aecb11563421b631e52dc8b32ee3cc734c345362e5cb tick_size_change 3,804 141,203 412-412 17b86f0769184dfc3d7d0caaa5c61ec4e08c19c6dc9085139807e02e626dee2a EVENT MIX count share price_change 97,835,874 91.63% best_bid_ask 8,727,762 8.17% book 142,421 0.13% last_trade_price 59,916 0.06% tick_size_change 3,804 <0.01% new_market 3,035 <0.01% market_resolved 857 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,727,848 8,727,762 86 211 FULL book 142,421 142,421 0 7,615 FULL last_trade_price 59,916 59,916 0 0 FULL market_resolved 857 857 0 0 FULL new_market 3,035 3,035 0 0 FULL price_change 97,836,752 97,835,874 878 948 FULL tick_size_change 3,804 3,804 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 8,725,259 44,388 18ms 28ms 426ms 60.0s 0 transport_latency_assumed best_bid_ask i 8,726,051 23,180 22ms 31ms 222ms 10.8s 0 transport_latency_assumed best_bid_ask m 8,726,504 4,490,019 5ms 12ms 112ms 7.2s 0 transport_latency_assumed best_bid_ask n 8,724,340 4,921 46ms 61ms 355ms 16.6s 0 transport_latency_assumed best_bid_ask o 8,726,596 4,165,254 5ms 12ms 125ms 8.3s 0 transport_latency_assumed book h 133,229 11,737 24ms 1.0s 2.0d 127.6d 0 book_staleness book i 124,997 2,829 25ms 146ms 1.2min 109.0d 0 book_staleness book m 125,065 65,074 7ms 31ms 3.3min 109.0d 0 book_staleness book n 126,591 3,839 51ms 900ms 53.8min 109.1d 0 book_staleness book o 124,668 58,942 7ms 32ms 22.2s 127.6d 0 book_staleness last_trade_price h 59,782 438 20ms 58ms 929ms 52.8s 0 transport_latency_assumed last_trade_price i 59,861 195 24ms 78ms 1.2s 3.3s 0 transport_latency_assumed last_trade_price m 59,793 31,063 6ms 17ms 215ms 2.8s 0 transport_latency_assumed last_trade_price n 59,550 61 50ms 305ms 5.5s 16.6s 0 transport_latency_assumed last_trade_price o 59,847 28,159 6ms 19ms 234ms 5.1s 0 transport_latency_assumed market_resolved h 811 45 21ms 50ms 630ms 57.2s 0 transport_latency_assumed market_resolved i 811 4 24ms 77ms 52.6s 54.4s 0 transport_latency_assumed market_resolved m 811 422 6ms 21ms 47.9s 54.0s 0 transport_latency_assumed market_resolved n 811 not meas. 49ms 169ms 53.2s 57.1s 0 transport_latency_assumed market_resolved o 811 386 6ms 27ms 48.6s 55.0s 0 transport_latency_assumed new_market h 1,812 407 193ms 41.0s 2.1min 2.5min 0 transport_latency_assumed new_market i 1,812 479 188ms 47.3s 2.0min 2.3min 0 transport_latency_assumed new_market m 1,812 992 79ms 41.5s 2.1min 2.5min 0 transport_latency_assumed new_market n 1,812 112 242ms 40.6s 2.1min 2.4min 0 transport_latency_assumed new_market o 1,812 1,045 91ms 47.6s 2.1min 2.3min 0 transport_latency_assumed price_change h 97,708,749 533,804 19ms 32ms 555ms 1.0min 0 transport_latency_assumed price_change i 97,742,847 282,060 23ms 35ms 363ms 11.4s 0 transport_latency_assumed price_change m 97,771,607 50,385,031 5ms 13ms 127ms 8.0s 0 transport_latency_assumed price_change n 97,705,804 61,024 47ms 74ms 876ms 16.6s 0 transport_latency_assumed price_change o 97,769,984 46,573,955 5ms 13ms 141ms 8.3s 0 transport_latency_assumed tick_size_change h 3,804 9 19ms 28ms 204ms 9.2s 0 transport_latency_assumed tick_size_change i 3,804 16 22ms 31ms 115ms 1.5s 0 transport_latency_assumed tick_size_change m 3,804 1,913 5ms 11ms 71ms 126ms 0 transport_latency_assumed tick_size_change n 3,804 not meas. 46ms 57ms 217ms 1.4s 0 transport_latency_assumed tick_size_change o 3,804 1,866 5ms 11ms 51ms 239ms 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-04/12/2026-10-04T12.parquet sha256sum 2026-10-04T12.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.