Hour audit: 2026-09-19T21
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-19T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T21:00:00.000039057+00:00 · last event 2026-09-19T21:59:59.999877967+00:00
VOLUME 127,709,593 rows · 1,405,927,671 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 126,484,569 · e: 126,412,720 · g: 121,552,774 · f: 121,448,485 · c: 114,694,680 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 17,612,463 (13.79%) · e: 793,597 (0.62%) · g: 213,804 (0.17%) · f: 720,592 (0.56%) · c: 108,369,137 (84.86%) (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 127,709,593 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ed4d752490025f75810b05bddff5b222793e7293a74e0c695c573218b12ce029
the corpus checksum ledger names this file with the same digest
joined 127,720,346 to merged 127,709,593, minus 10,753 (minus 0.0084%)
boundary drops 10,753 · 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-19T23:01:56Z 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,917,814 169,611,579 0-56 72f49d0ac44cf38e950d49c0f0b589e0284cdc67cc617082dff498c427bf7424 book 1,305,305 78,522,382 57-61 7d51f1ef1ed61d2144781aa7b11acbf66bc516b20906ea8f35e82f10ab581be8 last_trade_price 58,614 3,401,906 62-62 9c5b8f958fa2c27d0fb1250ecdd23f0149547346613cc27e1bf86e4edfcf5353 market_resolved 4,308 595,032 63-63 97d76e96141dad1da172a605ebf258d304d5fd6ecb4a40a5686e650f682910c0 new_market 2,680 254,735 64-64 fcef88a5b7d73b937583595f04053d5eb509a3e65f9083f284fb89a5bcdbbbf8 price_change 111,413,692 1,151,833,555 65-490 ded9abb7eb8c8aad416d0c42b883965a5322982392b64c8b5746ca31edcaff82 tick_size_change 7,180 257,328 491-491 522ca689a1e0954603789da01b0b81fe415f365ec0f71a0fa4ae81892cc9d86d EVENT MIX count share price_change 111,413,692 87.24% best_bid_ask 14,917,814 11.68% book 1,305,305 1.02% last_trade_price 58,614 0.05% tick_size_change 7,180 <0.01% market_resolved 4,308 <0.01% new_market 2,680 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,918,018 14,917,814 204 3,114 FULL book 1,314,157 1,305,305 8,852 193,787 FULL last_trade_price 58,615 58,614 1 422 FULL market_resolved 4,308 4,308 0 357 FULL new_market 2,680 2,680 0 1 FULL price_change 111,415,388 111,413,692 1,696 1,457 FULL tick_size_change 7,180 7,180 0 303 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,441,659 12,751,041 5ms 14ms 147ms 6.8s 0 transport_latency_assumed best_bid_ask e 14,912,766 90,648 41ms 53ms 228ms 15.4s 0 transport_latency_assumed best_bid_ask f 14,260,929 37,082 47ms 62ms 266ms 17.2s 0 transport_latency_assumed best_bid_ask g 14,317,733 3,926 78ms 104ms 493ms 28.0s 0 transport_latency_assumed best_bid_ask h 14,915,365 2,035,117 18ms 31ms 263ms 48.5s 0 transport_latency_assumed book c 960,899 705,051 4.3min 1.2d 38.3d 113.0d 0 book_staleness book e 130,538 9,183 45ms 4.2s 1.2d 112.9d 0 book_staleness book f 513,702 385,861 1.9min 16.7h 34.7d 113.0d 0 book_staleness book g 515,359 182,983 3.1min 16.9h 35.1d 113.0d 0 book_staleness book h 122,797 22,227 22ms 103ms 12.7min 94.4d 0 book_staleness last_trade_price c 51,831 48,107 6ms 28ms 267ms 1.2s 0 transport_latency_assumed last_trade_price e 58,136 505 44ms 284ms 7.3s 15.4s 0 transport_latency_assumed last_trade_price f 55,342 250 50ms 289ms 7.8s 17.2s 0 transport_latency_assumed last_trade_price g 54,228 17 85ms 683ms 12.5s 28.0s 0 transport_latency_assumed last_trade_price h 58,355 9,735 19ms 57ms 393ms 26.1s 0 transport_latency_assumed market_resolved c 3,538 3,406 5ms 149ms 5.1min 5.7min 0 transport_latency_assumed market_resolved e 3,711 20 44ms 173ms 487ms 1.1min 0 transport_latency_assumed market_resolved f 3,556 31 51ms 167ms 494ms 2.5min 0 transport_latency_assumed market_resolved g 3,762 270 88ms 438ms 5.0min 6.1min 0 transport_latency_assumed market_resolved h 3,711 581 23ms 65ms 294ms 44.8s 0 transport_latency_assumed new_market c 1,660 1,103 96ms 29.3s 3.0min 1.8h 0 transport_latency_assumed new_market e 1,661 302 164ms 28.1s 2.6min 3.5min 0 transport_latency_assumed new_market f 1,661 362 195ms 29.2s 3.2min 2.7h 0 transport_latency_assumed new_market g 1,785 318 320ms 1.5min 2.8min 2.2h 0 transport_latency_assumed new_market h 1,661 595 151ms 27.6s 2.9min 51.4min 0 transport_latency_assumed price_change c 100,228,685 94,854,390 5ms 15ms 156ms 6.8s 0 transport_latency_assumed price_change e 111,298,728 692,912 41ms 62ms 424ms 15.4s 0 transport_latency_assumed price_change f 106,606,467 296,990 47ms 71ms 405ms 17.3s 0 transport_latency_assumed price_change g 106,652,879 26,290 78ms 128ms 1.2s 28.1s 0 transport_latency_assumed price_change h 111,375,500 15,543,110 18ms 35ms 272ms 50.8s 0 transport_latency_assumed tick_size_change c 6,408 6,039 5ms 11ms 137ms 271ms 0 transport_latency_assumed tick_size_change e 7,180 27 41ms 48ms 245ms 640ms 0 transport_latency_assumed tick_size_change f 6,828 16 47ms 53ms 311ms 543ms 0 transport_latency_assumed tick_size_change g 7,028 not meas. 77ms 90ms 496ms 3.5s 0 transport_latency_assumed tick_size_change h 7,180 1,098 18ms 27ms 238ms 926ms 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/21/2026-09-19T21.parquet sha256sum 2026-09-19T21.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.