Hour audit: 2026-09-14T00
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-14T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T00:00:00.000001219+00:00 · last event 2026-09-14T00:59:59.999983087+00:00
VOLUME 108,523,383 rows · 1,080,547,783 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 108,410,153 · g: 108,398,649 · f: 108,393,910 · e: 108,382,143 · h: 108,283,646 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 104,946,448 (96.70%) · g: 39,168 (0.04%) · f: 95,166 (0.09%) · e: 194,257 (0.18%) · h: 3,248,344 (2.99%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 108,523,383 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f31cc8e982c8b07ed766999d949c89762aefaeb90724f81632f743867fbd0927
the corpus checksum ledger names this file with the same digest
joined 108,526,263 to merged 108,523,383, minus 2,880 (minus 0.0027%)
boundary drops 2,880 · 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-14T02:01:33Z 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 12,542,673 131,902,740 0-47 dfd9f7b3455a7dc4375638aa8d04fab739ff5e7dbbda740b587abb705872d48e book 226,123 23,097,504 48-48 8d18177ab81ebd93996c27495eda19f3f773403f516e3f92d2fe240986830cf6 last_trade_price 49,844 2,793,097 49-49 1bed60bfd3ff654681b585262d1fbcb46b11ae164d9df840c738ce2bd1d46650 market_resolved 1,933 313,840 50-50 ef3041d0b66300f0f9e076491befa1511e457f310b0da7b025a3e7c1ad36fa8d new_market 418 47,596 51-51 6d181eb7ee2f4999d81f3c1615c056690e04f9eaddc6a4526b12511b04b6e797 price_change 95,699,300 921,045,905 52-417 7eb3871bc618bee8475b13e75498c379304294a9b935ed9e5849eba9325e35c4 tick_size_change 3,092 111,879 418-418 2303a9f8aa4d4898daafe953e86bc5bef3cc6c6a35fe5a56f962d360af5dc8a2 EVENT MIX count share price_change 95,699,300 88.18% best_bid_ask 12,542,673 11.56% book 226,123 0.21% last_trade_price 49,844 0.05% tick_size_change 3,092 <0.01% market_resolved 1,933 <0.01% new_market 418 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,543,086 12,542,673 413 103 FULL book 226,172 226,123 49 53,158 FULL last_trade_price 49,848 49,844 4 4 FULL market_resolved 1,933 1,933 0 0 FULL new_market 418 418 0 0 FULL price_change 95,701,714 95,699,300 2,414 187 FULL tick_size_change 3,092 3,092 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,542,503 12,191,792 5ms 8ms 51ms 2.0s 0 transport_latency_assumed best_bid_ask e 12,541,569 16,250 40ms 44ms 99ms 3.2s 0 transport_latency_assumed best_bid_ask f 12,540,784 6,042 46ms 51ms 109ms 10.0s 0 transport_latency_assumed best_bid_ask g 12,539,055 251 81ms 96ms 191ms 12.7s 0 transport_latency_assumed best_bid_ask h 12,536,365 328,338 17ms 21ms 70ms 7.7s 0 transport_latency_assumed book c 124,432 118,657 7ms 11.0min 6.5d 88.6d 0 book_staleness book e 119,869 15,775 42ms 1.9min 5.2d 107.1d 0 book_staleness book f 131,641 24,945 49ms 1.4h 6.6d 107.1d 0 book_staleness book g 144,561 34,601 91ms 3.6h 11.2d 107.1d 0 book_staleness book h 133,281 32,145 21ms 51.0min 6.6d 88.6d 0 book_staleness last_trade_price c 49,800 47,578 10ms 43ms 196ms 5.0s 0 transport_latency_assumed last_trade_price e 49,757 164 46ms 95ms 293ms 5.0s 0 transport_latency_assumed last_trade_price f 49,793 65 53ms 104ms 342ms 8.5s 0 transport_latency_assumed last_trade_price g 49,803 9 92ms 167ms 378ms 7.0s 0 transport_latency_assumed last_trade_price h 49,474 2,028 22ms 57ms 205ms 7.6s 0 transport_latency_assumed market_resolved c 1,928 1,892 5ms 8ms 43ms 411ms 0 transport_latency_assumed market_resolved e 1,928 1 41ms 115ms 268ms 513ms 0 transport_latency_assumed market_resolved f 1,928 not meas. 47ms 121ms 287ms 552ms 0 transport_latency_assumed market_resolved g 1,928 not meas. 85ms 220ms 443ms 1.0min 0 transport_latency_assumed market_resolved h 1,928 40 18ms 39ms 106ms 1.0min 0 transport_latency_assumed new_market c 298 212 35ms 14.3s 36.9min 2.0h 0 transport_latency_assumed new_market e 298 67 70ms 14.5s 39.9min 2.6h 0 transport_latency_assumed new_market f 298 18 75ms 11.4s 20.2s 1.4h 0 transport_latency_assumed new_market g 298 29 109ms 13.6s 20.1s 2.2h 0 transport_latency_assumed new_market h 298 92 51ms 12.7s 18.2s 21.3min 0 transport_latency_assumed price_change c 95,688,100 92,583,350 5ms 9ms 63ms 2.0s 0 transport_latency_assumed price_change e 95,665,630 162,000 40ms 46ms 126ms 3.8s 0 transport_latency_assumed price_change f 95,666,374 64,096 46ms 54ms 143ms 10.2s 0 transport_latency_assumed price_change g 95,659,912 4,278 82ms 99ms 236ms 13.4s 0 transport_latency_assumed price_change h 95,559,208 2,885,576 17ms 23ms 85ms 8.0s 0 transport_latency_assumed tick_size_change c 3,092 2,967 5ms 9ms 103ms 132ms 0 transport_latency_assumed tick_size_change e 3,092 not meas. 40ms 44ms 130ms 175ms 0 transport_latency_assumed tick_size_change f 3,092 not meas. 46ms 50ms 86ms 204ms 0 transport_latency_assumed tick_size_change g 3,092 not meas. 80ms 94ms 193ms 323ms 0 transport_latency_assumed tick_size_change h 3,092 125 17ms 21ms 64ms 135ms 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-14/00/2026-09-14T00.parquet sha256sum 2026-09-14T00.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.