Hour audit: 2026-09-04T19
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-09-04T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T19:00:00.020976765+00:00 · last event 2026-09-04T19:59:59.999904649+00:00
VOLUME 111,192,775 rows · 1,180,550,432 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 110,064,341 · h: 110,040,309 · e: 109,941,270 · b: 96,429,944 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 11,320 (0.01%) · h: 128,210 (0.12%) · e: 109,940,239 (98.87%) · b: 1,113,006 (1.00%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 111,192,775 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 0a21e67574c17c7158042c87e9411273e133e03d14f04dc61d656b8a7046d84a
the corpus checksum ledger names this file with the same digest
joined 111,194,096 to merged 111,192,775, minus 1,321 (minus 0.0012%)
boundary drops 1,321 · 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-04T20:55:03Z as bceh
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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,878,069 132,798,039 0-45 b0d8522655e130dae92127640f55176a2cef1a0aa8d5e31f3e1afd41c5efc3a9 book 1,241,553 73,135,394 46-50 b7dbf0e14dd9b203d824921b3bd2836dea680d7e2ba4edea0711e03b797a711d last_trade_price 65,278 3,723,715 51-51 e021c5736a4592751317ade696b88da92b55478973bc4f5625eb2eafbf4ac124 market_resolved 1,372 159,122 52-52 c7a9c96004be6d684316b002bf532f1af2dcf407ad587f1002a6e1ad069f4c7d new_market 5,983 494,408 53-53 ca184153926efb4b53739237a44b8f7097b9bee3e3edf66475ccbcabbc3acd39 price_change 97,993,436 968,717,481 54-427 f518a255fbd749ec982ac3010692a59f654ced14d6d3ae4a0ae1d8e332acf64b tick_size_change 7,084 257,643 428-428 15ce316080ad823f36d28aee8049e1feccfc921545ec72bed30ee0a862817e73 EVENT MIX count share price_change 97,993,436 88.13% best_bid_ask 11,878,069 10.68% book 1,241,553 1.12% last_trade_price 65,278 0.06% tick_size_change 7,084 <0.01% new_market 5,983 <0.01% market_resolved 1,372 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,878,277 11,878,069 208 1,980 FULL book 1,241,581 1,241,553 28 191,166 FULL last_trade_price 65,279 65,278 1 393 FULL market_resolved 1,372 1,372 0 9 FULL new_market 5,983 5,983 0 0 FULL price_change 97,994,520 97,993,436 1,084 997 FULL tick_size_change 7,084 7,084 0 128 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,294,057 14 50ms 72ms 407ms 4.5s 0 transport_latency_assumed best_bid_ask c 11,877,669 635 5ms 11ms 246ms 9.0s 0 transport_latency_assumed best_bid_ask e 11,870,837 11,870,677 41ms 83ms 551ms 23.3s 0 transport_latency_assumed best_bid_ask h 11,875,319 6,743 18ms 38ms 733ms 53.3s 0 transport_latency_assumed book b 1,216,332 1,097,072 3.0min 13.8h 33.2d 97.9d 0 book_staleness book c 139,882 1,342 7ms 62ms 4.4s 79.3d 0 book_staleness book e 140,069 140,069 44ms 702ms 12.7s 1.5d 0 book_staleness book h 140,438 3,070 23ms 191ms 27.0s 79.4d 0 book_staleness last_trade_price b 55,049 1 60ms 190ms 1.7s 5.0s 0 transport_latency_assumed last_trade_price c 65,243 11 10ms 52ms 446ms 5.1s 0 transport_latency_assumed last_trade_price e 64,987 64,986 50ms 335ms 3.6s 23.0s 0 transport_latency_assumed last_trade_price h 65,171 280 25ms 102ms 1.2s 39.6s 0 transport_latency_assumed market_resolved b 1,199 400 58ms 8.8min 14.1min 16.4min 0 transport_latency_assumed market_resolved c 954 11 5ms 19ms 60.0s 1.0min 0 transport_latency_assumed market_resolved e 954 954 41ms 341ms 59.9s 1.0min 0 transport_latency_assumed market_resolved h 954 7 19ms 157ms 58.3s 1.0min 0 transport_latency_assumed new_market b 4,874 1,697 1.0min 9.6min 11.5min 12.0min 0 transport_latency_assumed new_market c 2,961 417 119ms 1.2min 3.8min 3.8min 0 transport_latency_assumed new_market e 2,961 2,961 247ms 34.7s 1.5min 3.8min 0 transport_latency_assumed new_market h 2,961 908 196ms 1.1min 3.8min 3.8min 0 transport_latency_assumed price_change b 84,851,861 13,822 51ms 82ms 482ms 5.0s 0 transport_latency_assumed price_change c 97,970,548 8,904 5ms 12ms 259ms 9.6s 0 transport_latency_assumed price_change e 97,854,378 97,853,508 41ms 102ms 908ms 23.3s 0 transport_latency_assumed price_change h 97,948,382 117,202 18ms 41ms 739ms 53.4s 0 transport_latency_assumed tick_size_change b 6,572 not meas. 50ms 73ms 397ms 939ms 0 transport_latency_assumed tick_size_change c 7,084 not meas. 5ms 8ms 218ms 679ms 0 transport_latency_assumed tick_size_change e 7,084 7,084 41ms 109ms 447ms 18.1s 0 transport_latency_assumed tick_size_change h 7,084 not meas. 18ms 33ms 420ms 3.3s 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-04/19/2026-09-04T19.parquet sha256sum 2026-09-04T19.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.