Hour audit: 2026-09-04T13
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-04T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T13:00:00.022986957+00:00 · last event 2026-09-04T13:59:59.999993289+00:00
VOLUME 110,073,600 rows · 1,131,588,223 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 109,608,187 · e: 108,816,803 · c: 108,768,050 · b: 105,437,602 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 817,778 (0.74%) · e: 108,815,716 (98.86%) · c: 66,637 (0.06%) · b: 373,469 (0.34%) (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 110,073,600 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 3fb62245557c3d0503f90c42c09a27433ad12220c8563c5e07d2f8a949f024ec
the corpus checksum ledger names this file with the same digest
joined 110,075,003 to merged 110,073,600, minus 1,403 (minus 0.0013%)
boundary drops 1,403 · 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-04T16:03:22Z 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 10,087,162 112,119,457 0-38 8fa4e1e195d59526baf9fe318c54e00b27dc954904af3bbc639e3e2bfa5482ba book 623,736 63,600,052 39-41 94f3cb17f75236be983c936af6bbad2f344558fdfe2c29467328d8bd827b4b4e last_trade_price 86,696 4,711,186 42-42 254ac342fc851c111834a20a6c92648c496852725ede58a4a959455d80c24793 market_resolved 718 106,425 43-43 bfb9bc2765b744caf63cc877690498aa04360acb404f7c8b823e0bf525a1d0b6 new_market 910 104,153 44-44 42dfcc19407026ed740f141e2432ab2421061916e245c21b1ad0b305c38c27be price_change 99,271,022 949,572,107 45-423 b5cd882bdda63d694c3d27c9d4719af4fb7ea4f63aadf45eebe35ee7950b0ec1 tick_size_change 3,356 121,345 424-424 b565be97ff799eb49680a3d8feec0880874062281a0950be1b27acaa21d952af EVENT MIX count share price_change 99,271,022 90.19% best_bid_ask 10,087,162 9.16% book 623,736 0.57% last_trade_price 86,696 0.08% tick_size_change 3,356 <0.01% new_market 910 <0.01% market_resolved 718 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,087,300 10,087,162 138 1,933 FULL book 623,754 623,736 18 185,140 FULL last_trade_price 86,697 86,696 1 161 FULL market_resolved 718 718 0 9 FULL new_market 910 910 0 0 FULL price_change 99,272,268 99,271,022 1,246 2,525 FULL tick_size_change 3,356 3,356 0 31 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,696,480 8 49ms 65ms 209ms 8.7s 0 transport_latency_assumed best_bid_ask c 9,986,460 534 5ms 9ms 61ms 1.9s 0 transport_latency_assumed best_bid_ask e 10,005,192 10,005,076 39ms 53ms 233ms 7.3s 0 transport_latency_assumed best_bid_ask h 10,086,410 81,544 18ms 30ms 107ms 6.9s 0 transport_latency_assumed book b 572,219 363,593 1.0min 11.1h 27.0d 97.6d 0 book_staleness book c 241,718 61,249 8ms 19.2min 13.0d 97.7d 0 book_staleness book e 194,550 194,550 44ms 1.8s 12.0h 79.1d 0 book_staleness book h 183,097 4,344 23ms 74ms 2.7min 79.1d 0 book_staleness last_trade_price b 83,221 9 63ms 296ms 3.3s 8.8s 0 transport_latency_assumed last_trade_price c 86,478 14 10ms 39ms 216ms 5.0s 0 transport_latency_assumed last_trade_price e 86,204 86,203 49ms 256ms 2.8s 7.3s 0 transport_latency_assumed last_trade_price h 86,578 470 25ms 73ms 335ms 5.6s 0 transport_latency_assumed market_resolved b 651 55 50ms 532ms 5.1min 5.1min 0 transport_latency_assumed market_resolved c 651 6 5ms 9ms 208ms 2.1min 0 transport_latency_assumed market_resolved e 648 648 40ms 193ms 629ms 2.2min 0 transport_latency_assumed market_resolved h 653 9 19ms 97ms 201ms 1.5s 0 transport_latency_assumed new_market b 683 18 174ms 13.0s 1.7min 2.0min 0 transport_latency_assumed new_market c 683 44 46ms 315ms 57.6s 1.5min 0 transport_latency_assumed new_market e 683 683 130ms 12.9s 1.6min 2.0min 0 transport_latency_assumed new_market h 683 165 91ms 15.2s 50.7s 1.0min 0 transport_latency_assumed price_change b 95,081,060 9,786 49ms 75ms 428ms 8.8s 0 transport_latency_assumed price_change c 98,448,728 4,790 5ms 10ms 66ms 2.1s 0 transport_latency_assumed price_change e 98,526,202 98,525,232 39ms 70ms 475ms 7.4s 0 transport_latency_assumed price_change h 99,247,410 731,214 19ms 33ms 123ms 9.2s 0 transport_latency_assumed tick_size_change b 3,288 not meas. 49ms 64ms 225ms 349ms 0 transport_latency_assumed tick_size_change c 3,332 not meas. 5ms 8ms 35ms 118ms 0 transport_latency_assumed tick_size_change e 3,324 3,324 39ms 56ms 228ms 458ms 0 transport_latency_assumed tick_size_change h 3,356 32 19ms 31ms 56ms 744ms 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/13/2026-09-04T13.parquet sha256sum 2026-09-04T13.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.