Hour audit: 2026-09-10T12
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-10T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T12:00:00.000000770+00:00 · last event 2026-09-10T12:59:59.999754343+00:00
VOLUME 120,958,194 rows · 1,302,994,567 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 119,343,696 · f: 119,309,029 · e: 119,264,432 · g: 119,175,588 · c: 100,038,711 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 23,561,591 (19.48%) · f: 311,960 (0.26%) · e: 1,388,057 (1.15%) · g: 29,873 (0.02%) · c: 95,666,713 (79.09%) (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 120,958,194 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 024b6a736a9b75eda01cfbdaadb0ec2b278ffa5afd46e9bf0746605cca8d8f55
the corpus checksum ledger names this file with the same digest
joined 120,960,106 to merged 120,958,194, minus 1,912 (minus 0.0016%)
boundary drops 1,912 · 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-10T14:00:38Z 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,275,548 127,575,105 0-43 0012680ccf5951765dbc2b96bc730485d8afcf01ace63b5859e75ec9001a1efe book 1,760,118 89,307,456 44-50 a17db2c3e19ef4c19eda126b6a8644d860abbd3c3b0fb651e906f76bda5f4f66 last_trade_price 81,132 4,559,922 51-51 cd2575f7cafd0a661c9a8c3948b24095212190f9d520137bf783e96a38d0d217 market_resolved 1,092 145,403 52-52 8e0c8a77431b309718ac7dce43c7874ca533d3c6a488ed056c7914ef0128c032 new_market 1,056 111,226 53-53 5b43733abe9e97a9ab04190e3e257f43053860b56498b75c57100c3a3140cbfb price_change 107,835,956 1,079,796,025 54-465 da4645bdcfa19442ed79aa44301a61c4c842554cb3a524ca0c290146bdbf2adb tick_size_change 3,292 121,909 466-466 6ff700306a49fb7f8dd81fafc240cf4a79809f544848cfc159eb717acd529f06 EVENT MIX count share price_change 107,835,956 89.15% best_bid_ask 11,275,548 9.32% book 1,760,118 1.46% last_trade_price 81,132 0.07% tick_size_change 3,292 <0.01% market_resolved 1,092 <0.01% new_market 1,056 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,275,790 11,275,548 242 2,033 FULL book 1,760,134 1,760,118 16 192,723 FULL last_trade_price 81,134 81,132 2 346 FULL market_resolved 1,092 1,092 0 32 FULL new_market 1,056 1,056 0 0 FULL price_change 107,837,608 107,835,956 1,652 1,358 FULL tick_size_change 3,292 3,292 0 81 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,342,692 8,938,442 5ms 12ms 99ms 3.2s 0 transport_latency_assumed best_bid_ask e 11,271,848 126,795 40ms 50ms 188ms 11.3s 0 transport_latency_assumed best_bid_ask f 11,273,017 27,560 47ms 61ms 227ms 9.2s 0 transport_latency_assumed best_bid_ask g 11,270,540 2,089 79ms 112ms 434ms 24.3s 0 transport_latency_assumed best_bid_ask h 11,274,596 2,180,662 18ms 29ms 156ms 25.3s 0 transport_latency_assumed book c 1,725,734 1,714,798 16.5min 1.1d 32.6d 103.6d 0 book_staleness book e 170,921 5,037 43ms 226ms 3.7min 85.0d 0 book_staleness book f 171,425 1,934 50ms 293ms 18.9s 84.9d 0 book_staleness book g 177,167 5,195 89ms 1.5s 8.7h 85.0d 0 book_staleness book h 170,599 33,154 23ms 72ms 1.7s 85.0d 0 book_staleness last_trade_price c 67,157 63,636 11ms 46ms 273ms 5.0s 0 transport_latency_assumed last_trade_price e 80,381 1,152 52ms 201ms 3.4s 11.3s 0 transport_latency_assumed last_trade_price f 80,815 325 60ms 251ms 3.7s 9.2s 0 transport_latency_assumed last_trade_price g 80,283 37 96ms 452ms 8.7s 24.3s 0 transport_latency_assumed last_trade_price h 80,985 15,982 25ms 83ms 683ms 19.2s 0 transport_latency_assumed market_resolved c 963 910 6ms 5.6min 9.4min 9.9min 0 transport_latency_assumed market_resolved e 891 23 41ms 186ms 57.1s 1.0min 0 transport_latency_assumed market_resolved f 891 1 48ms 195ms 57.7s 1.0min 0 transport_latency_assumed market_resolved g 891 15 84ms 242ms 853ms 2.0s 0 transport_latency_assumed market_resolved h 891 143 19ms 77ms 58.5s 1.0min 0 transport_latency_assumed new_market c 784 536 81ms 4.6min 6.9min 6.9min 0 transport_latency_assumed new_market e 719 93 178ms 13.9s 22.3s 1.0min 0 transport_latency_assumed new_market f 719 86 192ms 10.8s 22.3s 56.5s 0 transport_latency_assumed new_market g 719 81 314ms 13.7s 23.0s 1.0min 0 transport_latency_assumed new_market h 719 260 124ms 16.9s 24.5s 1.4min 0 transport_latency_assumed price_change c 88,898,413 84,945,587 5ms 13ms 108ms 3.6s 0 transport_latency_assumed price_change e 107,736,380 1,254,924 40ms 57ms 344ms 11.4s 0 transport_latency_assumed price_change f 107,778,870 282,042 47ms 70ms 419ms 9.3s 0 transport_latency_assumed price_change g 107,642,696 22,456 80ms 132ms 899ms 24.4s 0 transport_latency_assumed price_change h 107,812,614 21,330,947 19ms 32ms 179ms 28.3s 0 transport_latency_assumed tick_size_change c 2,968 2,804 5ms 16ms 256ms 466ms 0 transport_latency_assumed tick_size_change e 3,292 33 40ms 97ms 359ms 845ms 0 transport_latency_assumed tick_size_change f 3,292 12 47ms 58ms 397ms 723ms 0 transport_latency_assumed tick_size_change g 3,292 not meas. 80ms 116ms 617ms 12.9s 0 transport_latency_assumed tick_size_change h 3,292 443 19ms 40ms 363ms 1.1s 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-10/12/2026-09-10T12.parquet sha256sum 2026-09-10T12.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.