Hour audit: 2026-09-19T15
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-19T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T15:00:00.000035090+00:00 · last event 2026-09-19T15:59:59.999932661+00:00
VOLUME 154,303,063 rows · 1,762,729,630 bytes (1.64 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 149,545,641 · e: 143,468,077 · g: 115,431,160 · f: 107,216,662 · c: 97,374,555 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 54,978,720 (35.63%) · e: 4,500,886 (2.92%) · g: 663,785 (0.43%) · f: 2,928,250 (1.90%) · c: 91,231,422 (59.12%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 427cef27f3d95813b5b0c3783d526837edfb5a20b00213196f15f14204f6e38f
the corpus checksum ledger names this file with the same digest
joined 154,322,527 to merged 154,303,063, minus 19,464 (minus 0.0126%)
boundary drops 19,464 · 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-19T17:39:44Z 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 16,913,028 197,282,410 0-64 5c5a25397015c1269a89017a326fddeb49bf74fca2ad8ee56418c9413e40013c book 4,845,078 170,179,876 65-83 897792a1104d6b7671691cb2984a6f15eb1f634a6ef9919d4923e2bf8ef663da last_trade_price 79,472 4,703,380 84-84 7fa2a94ce5acbd0a43cb2567ca6a5c0a9f24bf7b991ac18d9a3c8515e5ad3227 market_resolved 7,005 563,814 85-85 46d25a7fbe4e2eb0cc3f21ad4ddbe6ac99e33f49d2f92b70f9592c7d52ae99fb new_market 2,050 116,522 86-86 8ca68c5726086613b98c2126358b31b75f8585bb37e3f2df2729754c449db627 price_change 132,441,730 1,387,594,455 87-592 a03638885b84967566e2b8b4792e7324b8bba24f6839b9a5cfe3f07f8e0ca6a8 tick_size_change 14,700 535,428 593-593 b7745e4366e2d4e311b10883d47956f5a307b4a15090652456b06d4967480d71 EVENT MIX count share price_change 132,441,730 85.83% best_bid_ask 16,913,028 10.96% book 4,845,078 3.14% last_trade_price 79,472 0.05% tick_size_change 14,700 <0.01% market_resolved 7,005 <0.01% new_market 2,050 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 16,913,367 16,913,028 339 15,331 FULL book 4,861,879 4,845,078 16,801 200,489 FULL last_trade_price 79,472 79,472 0 2,300 FULL market_resolved 7,005 7,005 0 900 FULL new_market 2,052 2,050 2 21 FULL price_change 132,444,052 132,441,730 2,322 8,018 FULL tick_size_change 14,700 14,700 0 2,525 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,554,309 10,058,115 5ms 14ms 83ms 2.0s 0 transport_latency_assumed best_bid_ask e 16,160,614 490,510 43ms 53ms 164ms 38.3s 0 transport_latency_assumed best_bid_ask f 11,667,206 74,233 48ms 59ms 194ms 7.4s 0 transport_latency_assumed best_bid_ask g 12,886,626 6,539 79ms 96ms 287ms 15.6s 0 transport_latency_assumed best_bid_ask h 16,912,078 6,283,631 19ms 41ms 125ms 43.5s 0 transport_latency_assumed book c 3,438,182 2,031,728 5.0min 23.4h 38.8d 112.7d 0 book_staleness book e 585,860 31,445 1.5min 10.8h 28.1d 112.7d 0 book_staleness book f 2,998,548 2,159,912 4.9min 23.3h 38.8d 112.7d 0 book_staleness book g 1,595,290 563,012 4.1min 23.2h 37.9d 112.7d 0 book_staleness book h 168,530 58,981 23ms 75ms 5.6min 94.1d 0 book_staleness last_trade_price c 50,543 47,382 11ms 50ms 328ms 5.0s 0 transport_latency_assumed last_trade_price e 75,806 2,051 53ms 185ms 2.8s 18.1s 0 transport_latency_assumed last_trade_price f 55,837 513 58ms 176ms 3.2s 7.4s 0 transport_latency_assumed last_trade_price g 60,749 162 92ms 310ms 5.6s 15.6s 0 transport_latency_assumed last_trade_price h 79,355 29,364 26ms 79ms 581ms 7.4s 0 transport_latency_assumed market_resolved c 4,952 3,888 5.2min 19.8min 28.6min 29.4min 0 transport_latency_assumed market_resolved e 3,121 76 76ms 194ms 624ms 5.5min 0 transport_latency_assumed market_resolved f 3,987 1,835 199ms 14.1min 19.0min 19.3min 0 transport_latency_assumed market_resolved g 3,074 76 169ms 735ms 7.5min 9.9min 0 transport_latency_assumed market_resolved h 3,216 1,130 34ms 78ms 482ms 54.6s 0 transport_latency_assumed new_market c 1,849 1,116 6.1min 17.7min 25.1min 1.0h 0 transport_latency_assumed new_market e 643 61 189ms 23.8s 47.7s 8.5min 0 transport_latency_assumed new_market f 1,263 595 46.1s 7.2min 12.7min 1.1h 0 transport_latency_assumed new_market g 855 104 392ms 6.2min 7.3min 9.9min 0 transport_latency_assumed new_market h 643 174 103ms 18.5s 43.1s 4.7min 0 transport_latency_assumed price_change c 83,313,220 79,078,211 6ms 16ms 104ms 2.1s 0 transport_latency_assumed price_change e 126,627,497 3,976,533 43ms 61ms 407ms 44.8s 0 transport_latency_assumed price_change f 92,479,137 691,133 49ms 68ms 415ms 7.4s 0 transport_latency_assumed price_change g 100,875,710 93,888 79ms 110ms 693ms 15.7s 0 transport_latency_assumed price_change h 132,367,119 48,601,965 19ms 45ms 177ms 43.5s 0 transport_latency_assumed tick_size_change c 11,500 10,982 5ms 13ms 59ms 451ms 0 transport_latency_assumed tick_size_change e 14,536 210 42ms 50ms 130ms 1.2s 0 transport_latency_assumed tick_size_change f 10,684 29 48ms 60ms 152ms 2.3s 0 transport_latency_assumed tick_size_change g 8,856 4 79ms 95ms 214ms 2.0s 0 transport_latency_assumed tick_size_change h 14,700 3,475 19ms 38ms 99ms 1.8s 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/15/2026-09-19T15.parquet sha256sum 2026-09-19T15.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.