Hour audit: 2026-09-03T22
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-03T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T22:00:00.001351922+00:00 · last event 2026-09-03T22:59:59.999848840+00:00
VOLUME 96,514,485 rows · 907,320,868 bytes (865.29 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 96,492,255 · h: 64,655,628 · e: 53,769,678 · b: 49,550,817 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 24,362,977 (25.24%) · h: 18,375,203 (19.04%) · e: 53,769,204 (55.71%) · b: 7,101 (0.01%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 96,514,485 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 3665890db2fcc897833ea2f5b63e198f9fb70a1cdd052fbd7a9e2e8c8fedc751
the corpus checksum ledger names this file with the same digest
joined 96,515,092 to merged 96,514,485, minus 607 (minus 0.0006%)
boundary drops 607 · 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-03T23:49:12Z 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 9,695,755 109,182,977 0-36 903544516346855c944feda8c17249d7897774ad4617fb75f9c902cdb3d98240 book 145,051 13,678,663 37-37 310480c39d1a4fb212e2a3f65664cec56c3dae4d168bcfbe03947271288805e4 last_trade_price 61,320 3,408,596 38-38 64011de64019e594917cde4cfc2d2959e2e7c88b4760c563b7ad1fa9c4ec85d5 market_resolved 1,700 259,852 39-39 3dbaff30192c4c0c500dcd1aee49c21c364a40e75652787e316d09038e96f101 new_market 1,427 159,185 40-40 716c8e92fff17e305b8d781b596bcce356b00437cae1d7944139dc9f51785392 price_change 86,607,144 779,453,146 41-371 80a7260f441ac18c0fd70d84c9d74567532433ca5754efe862a74cda9d744fc2 tick_size_change 2,088 77,777 372-372 332a094c7216ca02ec2e1964ba8c757f23d051d7604b6c24494c106620eb1534 EVENT MIX count share price_change 86,607,144 89.73% best_bid_ask 9,695,755 10.05% book 145,051 0.15% last_trade_price 61,320 0.06% tick_size_change 2,088 <0.01% market_resolved 1,700 <0.01% new_market 1,427 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,695,862 9,695,755 107 149 FULL book 145,051 145,051 0 4,384 FULL last_trade_price 61,320 61,320 0 0 FULL market_resolved 1,700 1,700 0 0 FULL new_market 1,427 1,427 0 0 FULL price_change 86,607,644 86,607,144 500 114,210 FULL tick_size_change 2,088 2,088 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,682,865 42 51ms 76ms 596ms 24.8s 0 transport_latency_assumed best_bid_ask c 9,695,450 654 27ms 42ms 168ms 3.0s 0 transport_latency_assumed best_bid_ask e 9,677,269 9,677,179 43ms 99ms 830ms 25.2s 0 transport_latency_assumed best_bid_ask h 9,694,841 17,880 17ms 24ms 221ms 9.1s 0 transport_latency_assumed book b 126,813 6,931 127ms 7.4s 2.8h 78.5d 0 book_staleness book c 127,812 897 32ms 59ms 2.3s 70.6d 0 book_staleness book e 128,859 128,859 120ms 8.0s 6.1h 26.4d 0 book_staleness book h 127,529 8,364 32ms 451ms 3.3s 78.5d 0 book_staleness last_trade_price b 57,902 3 95ms 4.4s 15.5s 24.8s 0 transport_latency_assumed last_trade_price c 61,292 12 36ms 69ms 317ms 4.1s 0 transport_latency_assumed last_trade_price e 57,661 57,661 87ms 3.7s 14.8s 25.1s 0 transport_latency_assumed last_trade_price h 61,264 3,644 29ms 430ms 2.7s 5.9s 0 transport_latency_assumed market_resolved b 1,613 not meas. 53ms 371ms 57.2s 58.5s 0 transport_latency_assumed market_resolved c 1,613 86 29ms 42ms 89ms 605ms 0 transport_latency_assumed market_resolved e 1,613 1,613 44ms 392ms 53.9s 1.0min 0 transport_latency_assumed market_resolved h 1,613 1 18ms 145ms 53.1s 1.0min 0 transport_latency_assumed new_market b 1,022 79 256ms 15.2s 43.4s 1.1min 0 transport_latency_assumed new_market c 1,022 74 85ms 11.1s 27.8s 1.1min 0 transport_latency_assumed new_market e 1,022 1,022 206ms 12.8s 45.1s 1.1min 0 transport_latency_assumed new_market h 1,022 252 147ms 14.1s 31.0s 1.2min 0 transport_latency_assumed price_change b 39,678,514 46 52ms 222ms 8.3s 24.9s 0 transport_latency_assumed price_change c 86,602,978 24,361,254 28ms 43ms 193ms 3.3s 0 transport_latency_assumed price_change e 43,901,166 43,900,782 44ms 242ms 6.9s 25.2s 0 transport_latency_assumed price_change h 54,767,271 18,345,062 18ms 36ms 571ms 9.8s 0 transport_latency_assumed tick_size_change b 2,088 not meas. 51ms 64ms 172ms 447ms 0 transport_latency_assumed tick_size_change c 2,088 not meas. 28ms 43ms 71ms 269ms 0 transport_latency_assumed tick_size_change e 2,088 2,088 43ms 103ms 139ms 543ms 0 transport_latency_assumed tick_size_change h 2,088 not meas. 18ms 23ms 62ms 1.4s 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-03/22/2026-09-03T22.parquet sha256sum 2026-09-03T22.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.