Hour audit: 2026-09-19T01
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-19T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T01:00:00.000001004+00:00 · last event 2026-09-19T01:59:59.997574822+00:00
VOLUME 124,493,107 rows · 1,314,943,749 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 123,583,366 · e: 123,525,928 · f: 118,681,002 · c: 118,338,914 · g: 117,842,628 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 11,132,173 (8.94%) · e: 654,462 (0.53%) · f: 734,702 (0.59%) · c: 111,739,614 (89.76%) · g: 232,156 (0.19%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 1ad81364a71eca22edd7d5e2fc876a6cdda8990f7181152c837f7b7944c62fa8
the corpus checksum ledger names this file with the same digest
joined 124,500,043 to merged 124,493,107, minus 6,936 (minus 0.0056%)
boundary drops 6,936 · 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-19T04:14:19Z 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 13,725,794 149,615,435 0-52 b19fd7a9e0058ab7e7a08f46d29c061692411337b10cf9f72fdf9d4ee81b3a1a book 982,988 70,002,637 53-56 2e114551a779d6b4f894d970a0f2d761c8f58418cf82dcb21420e15a0cd1fc50 last_trade_price 50,621 2,951,734 57-57 f05d01c4b40885da2e87843d05ae6200a92496af2ec627174ae59ef503e59173 market_resolved 1,649 267,446 58-58 19f45d74f00fa88195f43f4f5c48d40a87543e45b5581c2c5e59d59941896628 new_market 897 97,077 59-59 911465cbd4701f3b97406c3ef932d1f4f2b266d42c639b8a76484a6d5d6427ef price_change 109,726,390 1,090,420,245 60-478 4e21b8cd1c037a248eeb180b6dcf5b97029505641a7ce2d4cc18a6dada0c7146 tick_size_change 4,768 174,110 479-479 eb2730ae50d12e9f5b4f9c50be872879b4cc94cc233191398302edf1aac9571a EVENT MIX count share price_change 109,726,390 88.14% best_bid_ask 13,725,794 11.03% book 982,988 0.79% last_trade_price 50,621 0.04% tick_size_change 4,768 <0.01% market_resolved 1,649 <0.01% new_market 897 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,726,529 13,725,794 735 1,020 FULL book 983,020 982,988 32 209,889 FULL last_trade_price 50,622 50,621 1 186 FULL market_resolved 1,649 1,649 0 30 FULL new_market 897 897 0 8 FULL price_change 109,732,558 109,726,390 6,168 622 FULL tick_size_change 4,768 4,768 0 85 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,140,438 12,495,800 4ms 12ms 103ms 5.6s 0 transport_latency_assumed best_bid_ask e 13,723,846 66,751 41ms 49ms 157ms 8.2s 0 transport_latency_assumed best_bid_ask f 13,112,889 22,304 47ms 56ms 163ms 7.8s 0 transport_latency_assumed best_bid_ask g 13,099,074 2,478 80ms 98ms 304ms 10.3s 0 transport_latency_assumed best_bid_ask h 13,723,957 1,138,461 18ms 28ms 128ms 50.5s 0 transport_latency_assumed book c 659,115 269,682 17.3min 10.0h 34.4d 112.1d 0 book_staleness book e 110,897 3,917 43ms 223ms 9.7h 93.6d 0 book_staleness book f 600,992 487,354 12.0min 9.8h 31.3d 112.1d 0 book_staleness book g 592,616 206,967 13.3min 9.9h 31.3d 112.1d 0 book_staleness book h 110,241 15,068 21ms 75ms 7.9h 93.6d 0 book_staleness last_trade_price c 47,843 44,465 10ms 52ms 286ms 5.0s 0 transport_latency_assumed last_trade_price e 50,554 342 48ms 139ms 1.2s 5.0s 0 transport_latency_assumed last_trade_price f 48,608 229 55ms 131ms 957ms 7.8s 0 transport_latency_assumed last_trade_price g 47,641 29 92ms 216ms 1.4s 8.5s 0 transport_latency_assumed last_trade_price h 50,545 5,556 24ms 71ms 383ms 15.9s 0 transport_latency_assumed market_resolved c 1,599 1,540 5ms 11ms 102ms 4.9min 0 transport_latency_assumed market_resolved e 1,603 2 46ms 134ms 367ms 2.3s 0 transport_latency_assumed market_resolved f 1,577 10 53ms 132ms 365ms 2.5min 0 transport_latency_assumed market_resolved g 1,625 34 92ms 261ms 5.8min 6.2min 0 transport_latency_assumed market_resolved h 1,603 63 23ms 59ms 138ms 954ms 0 transport_latency_assumed new_market c 619 472 41ms 14.9s 5.5min 5.6min 0 transport_latency_assumed new_market e 614 106 132ms 11.2s 46.0s 58.4s 0 transport_latency_assumed new_market f 608 125 129ms 24.6s 4.6min 4.6min 0 transport_latency_assumed new_market g 614 60 231ms 19.4s 1.3min 4.9min 0 transport_latency_assumed new_market h 614 134 123ms 21.0s 57.2s 1.4min 0 transport_latency_assumed price_change c 104,484,660 98,923,438 5ms 13ms 117ms 6.0s 0 transport_latency_assumed price_change e 109,633,646 583,320 41ms 55ms 264ms 8.4s 0 transport_latency_assumed price_change f 104,911,724 224,652 47ms 62ms 250ms 7.8s 0 transport_latency_assumed price_change g 104,096,442 22,580 80ms 105ms 451ms 10.9s 0 transport_latency_assumed price_change h 109,691,638 9,972,400 18ms 31ms 160ms 50.6s 0 transport_latency_assumed tick_size_change c 4,640 4,217 5ms 29ms 365ms 1.2s 0 transport_latency_assumed tick_size_change e 4,768 24 41ms 63ms 392ms 654ms 0 transport_latency_assumed tick_size_change f 4,604 28 47ms 77ms 449ms 1.0s 0 transport_latency_assumed tick_size_change g 4,616 8 81ms 103ms 534ms 1.3s 0 transport_latency_assumed tick_size_change h 4,768 491 18ms 42ms 502ms 1.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/01/2026-09-19T01.parquet sha256sum 2026-09-19T01.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.