Hour audit: 2026-09-19T10
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-19T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T10:00:00.000026613+00:00 · last event 2026-09-19T10:59:59.999824967+00:00
VOLUME 132,210,087 rows · 1,462,827,059 bytes (1.36 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 129,752,667 · e: 129,703,923 · g: 123,983,923 · f: 119,083,223 · c: 100,982,753 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 32,798,474 (24.81%) · e: 3,343,145 (2.53%) · g: 317,175 (0.24%) · f: 713,994 (0.54%) · c: 95,037,299 (71.88%) (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 132,210,087 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8824be7785a267fc6dde91daf153660d5b62bfc7fbe1a0486743c632d5ed5529
the corpus checksum ledger names this file with the same digest
joined 132,213,815 to merged 132,210,087, minus 3,728 (minus 0.0028%)
boundary drops 3,728 · 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-19T12:39:47Z 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 14,783,156 169,681,781 0-56 dcb91c3531959eb240493f208f249ba19db32ee43d9399130d08742703cbc776 book 2,616,704 118,713,719 57-66 fc1bab76190759ab573a3b70a3d7c53a5b68b7a4f20892c6f5e36bc44b902ad1 last_trade_price 60,170 3,512,251 67-67 c10c5de60e74e767d49c407a375975941823c4b8bee90d8d0ddb6a156b343ae5 market_resolved 737 79,272 68-68 b544cbaf95f8f332b3285941931853842a97ce04f28cb5da3ba5fbab961ea7dd new_market 3,578 283,545 69-69 f0a42160a4cbb903de2bb0fb99447ab9734f02a83f79a27d1aadc3ad10dfb6d4 price_change 114,740,198 1,168,852,367 70-507 d513616e0c2a1b634ea04f365b8666fb482fcd4dca79885295a3a09d51720e7d tick_size_change 5,544 203,272 508-508 0b2b2ee9e1ea4d52dc890ba718bb23e5d55f1870cbaa9ee04bb184e72a5807e9 EVENT MIX count share price_change 114,740,198 86.79% best_bid_ask 14,783,156 11.18% book 2,616,704 1.98% last_trade_price 60,170 0.05% tick_size_change 5,544 <0.01% new_market 3,578 <0.01% market_resolved 737 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,783,428 14,783,156 272 4,886 FULL book 2,618,174 2,616,704 1,470 171,366 FULL last_trade_price 60,172 60,170 2 793 FULL market_resolved 737 737 0 87 FULL new_market 3,578 3,578 0 20 FULL price_change 114,742,182 114,740,198 1,984 1,622 FULL tick_size_change 5,544 5,544 0 298 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,252,210 10,639,091 5ms 14ms 188ms 5.7s 0 transport_latency_assumed best_bid_ask e 14,777,201 367,743 40ms 51ms 261ms 17.4s 0 transport_latency_assumed best_bid_ask f 13,451,782 63,629 48ms 61ms 290ms 17.2s 0 transport_latency_assumed best_bid_ask g 14,097,809 12,215 77ms 100ms 526ms 24.5s 0 transport_latency_assumed best_bid_ask h 14,752,376 3,700,478 18ms 36ms 401ms 1.0min 0 transport_latency_assumed book c 2,184,739 1,934,970 4.9min 18.3h 38.4d 112.5d 0 book_staleness book e 232,397 55,413 251ms 26.5min 27.8d 112.5d 0 book_staleness book f 969,872 98,984 3.4min 16.5h 37.3d 112.5d 0 book_staleness book g 583,181 188,014 2.5min 15.1h 30.2d 112.5d 0 book_staleness book h 490,208 339,323 1.8min 11.5h 27.9d 112.5d 0 book_staleness last_trade_price c 45,563 42,357 10ms 55ms 374ms 5.0s 0 transport_latency_assumed last_trade_price e 59,600 1,778 48ms 178ms 1.6s 16.7s 0 transport_latency_assumed last_trade_price f 53,896 409 57ms 201ms 2.4s 17.1s 0 transport_latency_assumed last_trade_price g 57,079 97 90ms 346ms 6.6s 24.4s 0 transport_latency_assumed last_trade_price h 59,813 15,529 24ms 86ms 669ms 46.9s 0 transport_latency_assumed market_resolved c 516 476 7ms 11.1min 16.8min 16.8min 0 transport_latency_assumed market_resolved e 459 50 42ms 546ms 58.5s 1.0min 0 transport_latency_assumed market_resolved f 537 73 52ms 5.9min 10.3min 11.0min 0 transport_latency_assumed market_resolved g 472 11 82ms 725ms 8.8min 8.8min 0 transport_latency_assumed market_resolved h 458 127 19ms 128ms 59.9s 2.3min 0 transport_latency_assumed new_market c 2,433 1,758 416ms 11.4min 12.6min 12.8min 0 transport_latency_assumed new_market e 1,752 582 204ms 27.8s 1.0min 1.5min 0 transport_latency_assumed new_market f 1,768 250 247ms 29.4s 1.5min 6.1min 0 transport_latency_assumed new_market g 1,793 276 345ms 35.1s 1.6h 1.6h 0 transport_latency_assumed new_market h 1,752 712 173ms 27.0s 59.8s 1.9min 0 transport_latency_assumed price_change c 87,492,712 82,414,180 5ms 16ms 202ms 6.2s 0 transport_latency_assumed price_change e 114,626,982 2,917,527 40ms 62ms 426ms 17.4s 0 transport_latency_assumed price_change f 104,600,056 550,637 48ms 72ms 456ms 17.2s 0 transport_latency_assumed price_change g 109,238,261 116,562 78ms 123ms 997ms 25.0s 0 transport_latency_assumed price_change h 114,442,536 28,741,292 18ms 40ms 457ms 1.0min 0 transport_latency_assumed tick_size_change c 4,580 4,467 5ms 10ms 99ms 352ms 0 transport_latency_assumed tick_size_change e 5,532 52 40ms 49ms 279ms 489ms 0 transport_latency_assumed tick_size_change f 5,312 12 48ms 52ms 176ms 419ms 0 transport_latency_assumed tick_size_change g 5,328 not meas. 77ms 94ms 300ms 5.8s 0 transport_latency_assumed tick_size_change h 5,524 1,013 18ms 32ms 220ms 4.9s 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-19/10/2026-09-19T10.parquet sha256sum 2026-09-19T10.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.