Hour audit: 2026-09-19T22
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-19T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T22:00:00.000048587+00:00 · last event 2026-09-19T22:59:59.999972194+00:00
VOLUME 131,548,869 rows · 1,442,115,341 bytes (1.34 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 129,602,546 · e: 129,601,306 · g: 124,094,917 · f: 114,783,301 · c: 112,230,692 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 22,098,817 (16.80%) · e: 1,571,994 (1.19%) · g: 204,059 (0.16%) · f: 725,330 (0.55%) · c: 106,948,669 (81.30%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 131,548,869 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 63bc6771461681f9d4c0eb0af688712289868e06c16348e4bc410c4281b713ee
the corpus checksum ledger names this file with the same digest
joined 131,553,775 to merged 131,548,869, minus 4,906 (minus 0.0037%)
boundary drops 4,906 · 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-20T00:02:23Z 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 15,659,940 174,105,081 0-59 c6be0b2be773c903606eff6ba26a6c7e10e3c219257ef0ece0c6fb54023bc508 book 2,001,427 89,828,927 60-67 e3bbda0e4b25fe780a7d7f9942178e73c63ddf19e751ad220b0a5ef86ac20512 last_trade_price 50,986 2,961,308 68-68 4ac26882b6ea314743208eedfdbfce76f6551889c4d693dffb1983debe6c6749 market_resolved 4,897 612,709 69-69 c768e5cd9a574944899a5d73d01777cf03da1bd969d2e685987717719da10bfc new_market 1,070 109,898 70-70 ec6287510d0b773eac0ae665e5b825d37e891ed5f984c1591c869354e4aa8899 price_change 113,824,141 1,172,768,907 71-505 92571d2dac87b54ab4807aa011d600f535b8bdb1319163ea3a1675eba6cf2037 tick_size_change 6,408 233,507 506-506 63023cfe8c3e283af017cdc48e049d546f635852a28a17a5b850d14a2d4a632d EVENT MIX count share price_change 113,824,141 86.53% best_bid_ask 15,659,940 11.90% book 2,001,427 1.52% last_trade_price 50,986 0.04% tick_size_change 6,408 <0.01% market_resolved 4,897 <0.01% new_market 1,070 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,660,192 15,659,940 252 4,883 FULL book 2,004,192 2,001,427 2,765 192,655 FULL last_trade_price 50,986 50,986 0 522 FULL market_resolved 4,900 4,897 3 326 FULL new_market 1,070 1,070 0 45 FULL price_change 113,826,027 113,824,141 1,886 3,012 FULL tick_size_change 6,408 6,408 0 305 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,316,591 12,768,948 5ms 10ms 77ms 1.4s 0 transport_latency_assumed best_bid_ask e 15,658,770 188,925 41ms 49ms 146ms 5.5s 0 transport_latency_assumed best_bid_ask f 13,689,879 21,929 47ms 56ms 166ms 4.8s 0 transport_latency_assumed best_bid_ask g 14,989,998 2,832 79ms 95ms 279ms 38.0s 0 transport_latency_assumed best_bid_ask h 15,659,062 2,677,306 18ms 28ms 103ms 14.5s 0 transport_latency_assumed book c 1,669,339 1,296,017 7.0min 1.3d 39.1d 113.0d 0 book_staleness book e 105,248 2,421 43ms 186ms 9.8min 94.4d 0 book_staleness book f 1,293,038 506,175 5.3min 1.3d 39.1d 113.0d 0 book_staleness book g 519,477 178,618 3.0min 22.0h 35.5d 113.0d 0 book_staleness book h 105,633 18,196 22ms 72ms 16.1min 94.5d 0 book_staleness last_trade_price c 43,979 41,505 6ms 19ms 173ms 1.0s 0 transport_latency_assumed last_trade_price e 50,863 768 43ms 139ms 1.2s 5.1s 0 transport_latency_assumed last_trade_price f 45,241 234 49ms 150ms 1.2s 3.4s 0 transport_latency_assumed last_trade_price g 47,969 16 83ms 316ms 6.5s 38.1s 0 transport_latency_assumed last_trade_price h 50,834 8,463 19ms 48ms 270ms 7.0s 0 transport_latency_assumed market_resolved c 3,919 3,227 5ms 5.8min 10.1min 10.6min 0 transport_latency_assumed market_resolved e 3,627 63 43ms 123ms 317ms 865ms 0 transport_latency_assumed market_resolved f 4,092 659 97ms 5.9min 10.1min 10.4min 0 transport_latency_assumed market_resolved g 3,671 245 88ms 344ms 5.4min 5.7min 0 transport_latency_assumed market_resolved h 3,627 703 24ms 60ms 185ms 3.1s 0 transport_latency_assumed new_market c 666 466 50ms 225ms 34.8min 2.9h 0 transport_latency_assumed new_market e 700 83 124ms 15.3s 1.1min 43.5min 0 transport_latency_assumed new_market f 757 137 157ms 4.4min 14.5min 2.9h 0 transport_latency_assumed new_market g 701 114 244ms 16.7s 1.2min 1.6h 0 transport_latency_assumed new_market h 700 270 99ms 15.3s 1.4min 2.7h 0 transport_latency_assumed price_change c 97,190,658 92,833,212 5ms 12ms 90ms 1.7s 0 transport_latency_assumed price_change e 113,775,690 1,379,650 41ms 55ms 274ms 5.8s 0 transport_latency_assumed price_change f 99,744,462 196,196 48ms 64ms 304ms 4.8s 0 transport_latency_assumed price_change g 108,526,961 22,234 79ms 105ms 640ms 38.1s 0 transport_latency_assumed price_change h 113,776,282 19,392,849 18ms 32ms 129ms 15.2s 0 transport_latency_assumed tick_size_change c 5,540 5,294 5ms 10ms 51ms 204ms 0 transport_latency_assumed tick_size_change e 6,408 84 41ms 49ms 117ms 195ms 0 transport_latency_assumed tick_size_change f 5,832 not meas. 47ms 58ms 169ms 280ms 0 transport_latency_assumed tick_size_change g 6,140 not meas. 79ms 93ms 192ms 307ms 0 transport_latency_assumed tick_size_change h 6,408 1,030 18ms 28ms 78ms 420ms 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/22/2026-09-19T22.parquet sha256sum 2026-09-19T22.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.