Hour audit: 2026-09-26T17
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: g. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-26T17 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T17:00:00.000056144+00:00 · last event 2026-09-26T17:59:59.999741817+00:00
VOLUME 133,024,273 rows · 1,517,568,368 bytes (1.41 GiB) · 7 products, all holding rows
WITNESSES chik — 4 machines contributed rows
captured i: 127,926,131 · h: 111,423,850 · k: 107,568,985 · c: 73,738,638 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 6,628,035 (4.98%) · h: 8,478,372 (6.37%) · k: 50,059,597 (37.63%) · c: 67,858,269 (51.01%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 1 contributed nothing: g
INTEGRITY sha256 c7ea4c50ddc8a27ee3929d5782d7cc769709bbffd209dc1f336e1572e6e7693d
the corpus checksum ledger names this file with the same digest
joined 133,026,873 to merged 133,024,273, minus 2,600 (minus 0.0020%)
boundary drops 2,600 · 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-09-27T01:03:19Z as chik
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,876,953 138,798,813 0-45 7ac53d1d07c2f2e0bd55eaab1db87f525c0d358218b8dfa572f7bbd42460c84d book 5,193,802 142,074,916 46-65 80729739e114ce129dc159a34cdc91ea790e00dc2194f01da279dd6d4ed18139 last_trade_price 63,661 3,640,999 66-66 06fad2e5cbdec050102c9ce9527fb6fd577f27a2beef16fbec4fd8224a2f768b market_resolved 6,562 542,557 67-67 14e23fe708c767858b073ebebfc601846e2a6550bcca043a9a805e5af73b3f84 new_market 6,215 423,202 68-68 5cce40369d03a727c76cbf5640cfc763d46550403e5b4e5cbd6da6ef01bb2055 price_change 115,872,464 1,230,404,172 69-511 76a819f51dbc7afa8073acd753e776c9fec5bf21471b2374a364b44899259e87 tick_size_change 4,616 171,300 512-512 81bfd712c7195cbe83885a1735bbcd6b4b01354ef29f496cffec7bcb2cba9692 EVENT MIX count share price_change 115,872,464 87.11% best_bid_ask 11,876,953 8.93% book 5,193,802 3.90% last_trade_price 63,661 0.05% market_resolved 6,562 <0.01% new_market 6,215 <0.01% tick_size_change 4,616 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,876,977 11,876,953 24 61,218 PARTIAL book 5,195,984 5,193,802 2,182 214,475 PARTIAL last_trade_price 63,661 63,661 0 3,772 PARTIAL market_resolved 6,562 6,562 0 3,228 PARTIAL new_market 6,221 6,215 6 2,623 PARTIAL price_change 115,872,852 115,872,464 388 97,659 PARTIAL tick_size_change 4,616 4,616 0 1,154 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,378,253 5,865,545 5ms 16ms 128ms 7.4s 0 transport_latency_assumed best_bid_ask h 10,248,867 729,875 20ms 64ms 385ms 59.1s 0 transport_latency_assumed best_bid_ask i 11,875,844 597,636 23ms 36ms 175ms 4.8s 0 transport_latency_assumed best_bid_ask k 9,921,627 4,683,897 13ms 24ms 140ms 7.4s 0 transport_latency_assumed book c 4,463,747 4,348,035 1.4h 5.1d 45.1d 119.8d 0 book_staleness book h 1,387,032 384,178 59.7min 4.9d 42.3d 119.8d 0 book_staleness book i 132,499 10,539 26ms 136ms 4.4s 101.3d 0 book_staleness book k 1,803,019 451,050 1.1h 4.9d 44.9d 119.8d 0 book_staleness last_trade_price c 33,840 30,688 6ms 26ms 251ms 1.7s 0 transport_latency_assumed last_trade_price h 54,530 3,981 26ms 90ms 534ms 47.1s 0 transport_latency_assumed last_trade_price i 63,552 3,511 25ms 86ms 679ms 4.0s 0 transport_latency_assumed last_trade_price k 52,558 25,481 14ms 41ms 302ms 3.2s 0 transport_latency_assumed market_resolved c 5,336 5,152 14.5min 40.0min 45.6min 46.3min 0 transport_latency_assumed market_resolved h 1,987 285 25ms 5.3min 13.8min 13.9min 0 transport_latency_assumed market_resolved i 1,859 367 24ms 28.1s 43.7s 52.7s 0 transport_latency_assumed market_resolved k 1,821 758 14ms 53.0s 9.2min 10.2min 0 transport_latency_assumed new_market c 5,232 4,402 7.7min 29.1min 39.1min 21.2h 0 transport_latency_assumed new_market h 2,513 539 167ms 7.2min 8.2min 20.6h 0 transport_latency_assumed new_market i 2,131 338 109ms 32.0s 3.2min 20.6h 0 transport_latency_assumed new_market k 2,407 936 96ms 4.8min 6.2min 7.9min 0 transport_latency_assumed price_change c 62,849,810 57,602,217 5ms 18ms 161ms 10.4s 0 transport_latency_assumed price_change h 99,724,697 7,359,246 20ms 68ms 469ms 59.1s 0 transport_latency_assumed price_change i 115,845,630 6,015,419 23ms 42ms 251ms 5.0s 0 transport_latency_assumed price_change k 95,783,437 44,895,582 13ms 27ms 166ms 7.7s 0 transport_latency_assumed tick_size_change c 2,420 2,230 5ms 14ms 104ms 258ms 0 transport_latency_assumed tick_size_change h 4,224 268 20ms 67ms 295ms 1.2s 0 transport_latency_assumed tick_size_change i 4,616 225 22ms 35ms 110ms 453ms 0 transport_latency_assumed tick_size_change k 4,116 1,893 13ms 27ms 118ms 445ms 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-09-26/17/2026-09-26T17.parquet sha256sum 2026-09-26T17.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.