Hour audit: 2026-09-19T23
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-19T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T23:00:00.000018277+00:00 · last event 2026-09-19T23:59:59.999979261+00:00
VOLUME 141,777,240 rows · 1,590,562,644 bytes (1.48 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 139,512,933 · e: 139,492,316 · c: 122,954,477 · f: 117,962,216 · g: 117,891,670 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 23,155,094 (16.33%) · e: 1,874,615 (1.32%) · c: 114,428,753 (80.71%) · f: 1,485,569 (1.05%) · g: 833,209 (0.59%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 660d5c3624cc37b779261b3aafc1077309e38b29dbdd0e07ee61e5290a62e18f
the corpus checksum ledger names this file with the same digest
joined 141,780,076 to merged 141,777,240, minus 2,836 (minus 0.0020%)
boundary drops 2,836 · 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-20T01:40:55Z 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 17,038,308 193,737,817 0-64 cc70c4f4e981a794da2dc110932e013421bce7b0fd4cc32d44b8fccb5f892edb book 2,451,826 105,051,523 65-74 2691ca48d53ff24295386f8be88f279ddd7286f98bdbd55a5f68a1fe5ddeb020 last_trade_price 58,209 3,379,122 75-75 97203b7a0884ec3efe203beeda150561d7c2ec454dd8b87ec6e06c1baf27e24b market_resolved 5,563 709,770 76-76 fe6798b2d2bcfd7ba74ea2fdf4daac9368b3e07cc9b512d741742a0908115168 new_market 2,072 194,773 77-77 f8c4912ab02a85bb3e413aa6815a9e7964c3c6c1c12d8222ccde38a7ddeff9ca price_change 122,212,890 1,285,571,880 78-544 879bf4852574d46f31b60a67c132344cb9eddd1ddddac41229172229155e8a7c tick_size_change 8,372 308,034 545-545 4aa3cee987938744d1948e916f31627bf2fbd03f06d21d934362fbe32e0c1c6e EVENT MIX count share price_change 122,212,890 86.20% best_bid_ask 17,038,308 12.02% book 2,451,826 1.73% last_trade_price 58,209 0.04% tick_size_change 8,372 <0.01% market_resolved 5,563 <0.01% new_market 2,072 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 17,038,662 17,038,308 354 4,611 FULL book 2,451,900 2,451,826 74 154,446 FULL last_trade_price 58,211 58,209 2 619 FULL market_resolved 5,563 5,563 0 562 FULL new_market 2,072 2,072 0 4 FULL price_change 122,215,296 122,212,890 2,406 2,767 FULL tick_size_change 8,372 8,372 0 640 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 14,885,229 14,015,871 5ms 15ms 160ms 6.3s 0 transport_latency_assumed best_bid_ask e 17,034,278 213,002 43ms 55ms 224ms 13.1s 0 transport_latency_assumed best_bid_ask f 14,264,771 35,590 47ms 63ms 281ms 18.3s 0 transport_latency_assumed best_bid_ask g 14,244,371 5,293 80ms 104ms 505ms 28.4s 0 transport_latency_assumed best_bid_ask h 17,034,938 2,768,552 18ms 34ms 235ms 50.9s 0 transport_latency_assumed book c 1,339,484 334,763 5.4min 1.3d 39.2d 113.1d 0 book_staleness book e 263,862 64,162 13.3s 4.1h 28.4d 113.1d 0 book_staleness book f 1,658,958 1,168,559 6.0min 1.3d 39.2d 113.1d 0 book_staleness book g 1,641,969 781,288 6.6min 1.3d 39.2d 113.1d 0 book_staleness book h 314,659 103,054 41.2s 8.5h 28.4d 113.1d 0 book_staleness last_trade_price c 50,114 45,787 6ms 32ms 320ms 3.6s 0 transport_latency_assumed last_trade_price e 57,696 1,000 45ms 123ms 1.5s 12.7s 0 transport_latency_assumed last_trade_price f 48,595 176 50ms 178ms 2.7s 18.4s 0 transport_latency_assumed last_trade_price g 47,324 139 84ms 282ms 5.7s 28.4s 0 transport_latency_assumed last_trade_price h 57,936 11,107 19ms 58ms 478ms 49.5s 0 transport_latency_assumed market_resolved c 4,257 3,818 5ms 338ms 5.7min 6.2min 0 transport_latency_assumed market_resolved e 4,335 49 103ms 193ms 620ms 1.6min 0 transport_latency_assumed market_resolved f 4,283 614 118ms 4.6min 12.0min 12.8min 0 transport_latency_assumed market_resolved g 4,468 484 203ms 4.7min 11.0min 12.4min 0 transport_latency_assumed market_resolved h 4,336 598 35ms 70ms 521ms 1.6min 0 transport_latency_assumed new_market c 1,255 747 108ms 1.0min 4.7min 6.0h 0 transport_latency_assumed new_market e 1,188 402 186ms 22.4s 1.1min 1.3min 0 transport_latency_assumed new_market f 1,305 316 230ms 1.6min 56.4min 2.1h 0 transport_latency_assumed new_market g 1,252 109 290ms 48.6s 58.6min 3.9h 0 transport_latency_assumed new_market h 1,188 498 162ms 21.5s 1.2min 1.6min 0 transport_latency_assumed price_change c 106,667,170 100,021,134 5ms 18ms 177ms 6.6s 0 transport_latency_assumed price_change e 122,122,585 1,595,928 43ms 63ms 328ms 13.1s 0 transport_latency_assumed price_change f 101,977,228 280,286 48ms 71ms 417ms 18.4s 0 transport_latency_assumed price_change g 101,944,774 45,892 81ms 117ms 755ms 28.4s 0 transport_latency_assumed price_change h 122,091,508 20,269,650 18ms 37ms 262ms 51.5s 0 transport_latency_assumed tick_size_change c 6,968 6,633 5ms 11ms 57ms 242ms 0 transport_latency_assumed tick_size_change e 8,372 72 43ms 49ms 93ms 3.3s 0 transport_latency_assumed tick_size_change f 7,076 28 47ms 54ms 128ms 236ms 0 transport_latency_assumed tick_size_change g 7,512 4 80ms 93ms 170ms 338ms 0 transport_latency_assumed tick_size_change h 8,368 1,635 18ms 26ms 81ms 197ms 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/23/2026-09-19T23.parquet sha256sum 2026-09-19T23.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.