Hour audit: 2026-09-06T22
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-06T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T22:00:00.000017591+00:00 · last event 2026-09-06T22:59:59.999906124+00:00
VOLUME 112,216,386 rows · 1,153,693,985 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 111,784,293 · g: 111,756,628 · h: 111,636,806 · e: 111,595,968 · c: 107,414,408 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 217,491 (0.19%) · g: 23,595 (0.02%) · h: 7,698,955 (6.86%) · e: 846,381 (0.75%) · c: 103,429,964 (92.17%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 112,216,386 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c91b052b771dcfcb7298e58aceddd9f7850ecc4e1670575d0ac54dca869a4438
the corpus checksum ledger names this file with the same digest
joined 112,218,857 to merged 112,216,386, minus 2,471 (minus 0.0022%)
boundary drops 2,471 · 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-07T02:42:50Z as cefgh
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,910,402 130,153,803 0-45 0c4ea04db0f350ee3e8e767717d43897ce7bd943d339c26c0e63a14b21756375 book 524,615 50,886,150 46-48 7a93a4109890c18d45ae6431970dfb7acbc3b5595e1b9012376831357ce0ffa1 last_trade_price 53,271 3,039,286 49-49 c3acd7cf476ae47f84b56512cec14111f18c321ded1f248f3a0b7a4be20d1b9b market_resolved 3,022 497,541 50-50 0fafe309f632ca22683fd76bedd41478837a1c3bbeffa9cf4e89e99dd737d223 new_market 1,345 137,816 51-51 5d75a8e9198f9237d5708ad4eb866d88e5202c4277a72810ab29537ec7918057 price_change 99,719,085 967,530,670 52-432 b757d1c656df5feacad46b0522eb8eda9a623ff4742ffb41c8a78d0874f2b195 tick_size_change 4,646 169,197 433-433 c26e305d8c29871d08e857ac78561ef680b3c47c3378944e57a1799d32a5c424 EVENT MIX count share price_change 99,719,085 88.86% best_bid_ask 11,910,402 10.61% book 524,615 0.47% last_trade_price 53,271 0.05% tick_size_change 4,646 <0.01% market_resolved 3,022 <0.01% new_market 1,345 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,910,631 11,910,402 229 596 FULL book 524,619 524,615 4 172,662 FULL last_trade_price 53,273 53,271 2 69 FULL market_resolved 3,022 3,022 0 228 FULL new_market 1,345 1,345 0 0 FULL price_change 99,721,321 99,719,085 2,236 886 FULL tick_size_change 4,646 4,646 0 151 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,406,039 10,994,567 5ms 9ms 109ms 4.9s 0 transport_latency_assumed best_bid_ask e 11,908,907 87,671 39ms 45ms 168ms 4.4s 0 transport_latency_assumed best_bid_ask f 11,908,792 18,550 47ms 54ms 185ms 3.0s 0 transport_latency_assumed best_bid_ask g 11,907,424 1,441 82ms 99ms 370ms 21.9s 0 transport_latency_assumed best_bid_ask h 11,909,498 808,173 17ms 25ms 157ms 43.1s 0 transport_latency_assumed book c 501,955 495,379 2.0min 17.1h 34.2d 100.0d 0 book_staleness book e 111,073 2,912 41ms 164ms 3.2s 43.3d 0 book_staleness book f 120,391 6,876 50ms 718ms 20.9h 81.5d 0 book_staleness book g 126,057 9,699 92ms 38.1s 1.4d 100.0d 0 book_staleness book h 111,719 9,749 21ms 88ms 37.2s 81.4d 0 book_staleness last_trade_price c 50,374 47,935 10ms 43ms 281ms 5.0s 0 transport_latency_assumed last_trade_price e 53,184 678 45ms 140ms 1.4s 5.0s 0 transport_latency_assumed last_trade_price f 53,172 318 53ms 119ms 829ms 5.0s 0 transport_latency_assumed last_trade_price g 53,027 16 95ms 328ms 3.3s 21.9s 0 transport_latency_assumed last_trade_price h 53,234 4,324 23ms 80ms 633ms 6.7s 0 transport_latency_assumed market_resolved c 2,784 2,723 5ms 9ms 84ms 2.0min 0 transport_latency_assumed market_resolved e 3,012 28 43ms 137ms 351ms 530ms 0 transport_latency_assumed market_resolved f 3,012 4 51ms 133ms 360ms 755ms 0 transport_latency_assumed market_resolved g 3,012 1 92ms 247ms 550ms 1.0s 0 transport_latency_assumed market_resolved h 3,012 266 30ms 64ms 151ms 663ms 0 transport_latency_assumed new_market c 867 581 88ms 14.3s 25.5s 2.0h 0 transport_latency_assumed new_market e 867 182 212ms 20.6s 29.3s 2.6h 0 transport_latency_assumed new_market f 867 152 167ms 16.1s 27.8s 25.5min 0 transport_latency_assumed new_market g 867 96 293ms 13.9s 27.6s 2.7h 0 transport_latency_assumed new_market h 867 334 154ms 14.5s 30.3s 1.5h 0 transport_latency_assumed price_change c 95,448,345 91,884,858 5ms 10ms 117ms 6.1s 0 transport_latency_assumed price_change e 99,514,279 754,865 39ms 48ms 216ms 4.4s 0 transport_latency_assumed price_change f 99,693,413 191,588 47ms 57ms 218ms 3.1s 0 transport_latency_assumed price_change g 99,661,595 12,342 82ms 103ms 467ms 21.9s 0 transport_latency_assumed price_change h 99,553,830 6,875,432 17ms 28ms 179ms 43.6s 0 transport_latency_assumed tick_size_change c 4,044 3,921 5ms 8ms 163ms 865ms 0 transport_latency_assumed tick_size_change e 4,646 45 39ms 43ms 221ms 507ms 0 transport_latency_assumed tick_size_change f 4,646 3 47ms 51ms 219ms 580ms 0 transport_latency_assumed tick_size_change g 4,646 not meas. 81ms 95ms 387ms 1.0s 0 transport_latency_assumed tick_size_change h 4,646 677 17ms 25ms 181ms 1.2s 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-06/22/2026-09-06T22.parquet sha256sum 2026-09-06T22.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.