Hour audit: 2026-09-13T23
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-13T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T23:00:00.001674519+00:00 · last event 2026-09-13T23:59:59.999836171+00:00
VOLUME 119,123,806 rows · 1,262,105,039 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 117,642,883 · h: 117,603,752 · f: 108,023,501 · c: 104,480,663 · g: 103,494,359 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 2,079,898 (1.75%) · h: 16,856,662 (14.15%) · f: 558,607 (0.47%) · c: 98,812,247 (82.95%) · g: 816,392 (0.69%) (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 119,123,806 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 22b1db8053c3da7536679fe67bc87009a4788e7b4a7331eba3cf3ec206a9304f
the corpus checksum ledger names this file with the same digest
joined 119,134,472 to merged 119,123,806, minus 10,666 (minus 0.0090%)
boundary drops 10,666 · 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-14T01:36:36Z 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 12,607,445 136,458,795 0-48 76460106e968243a92aa7a35025815586ce3e61e1ca3b8a16772fc692e8056cc book 1,553,004 81,804,172 49-54 4c8a0e46a78493f89449e08050dd142756f7b9dc6e6c5f3791d07a83cd2f28fd last_trade_price 54,544 3,084,300 55-55 d9168d1f8ef970fce41014efbcaf7ad1f9ccf9b7cab5b4dd504abe4cbc157d27 market_resolved 3,701 416,931 56-56 9a3100bba924ae5650e8c7825005dbc43f71f2be14d80b109b504e113a12c013 new_market 1,898 142,733 57-57 e1c170f6e8ab230be589774a285dfb961dbd7281aa945e2cd07300b7e5cda723 price_change 104,897,414 1,038,632,425 58-458 cb173da176c0d8b5b943d6841e3101bb825e229ca53d676852dc64b9655203a0 tick_size_change 5,800 209,243 459-459 2130e3f3ecbb581bcfd9ebaea346fcf31807b0b583bbb865a285095c128fb0aa EVENT MIX count share price_change 104,897,414 88.06% best_bid_ask 12,607,445 10.58% book 1,553,004 1.30% last_trade_price 54,544 0.05% tick_size_change 5,800 <0.01% market_resolved 3,701 <0.01% new_market 1,898 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,607,683 12,607,445 238 3,017 FULL book 1,561,830 1,553,004 8,826 168,527 FULL last_trade_price 54,544 54,544 0 383 FULL market_resolved 3,701 3,701 0 139 FULL new_market 1,904 1,898 6 46 FULL price_change 104,899,010 104,897,414 1,596 2,384 FULL tick_size_change 5,800 5,800 0 199 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,131,459 10,649,764 5ms 11ms 100ms 7.2s 0 transport_latency_assumed best_bid_ask e 12,604,920 209,439 40ms 51ms 185ms 9.2s 0 transport_latency_assumed best_bid_ask f 11,578,246 32,129 46ms 58ms 188ms 8.4s 0 transport_latency_assumed best_bid_ask g 11,061,659 2,499 82ms 101ms 378ms 1.8min 0 transport_latency_assumed best_bid_ask h 12,604,065 1,713,614 18ms 32ms 153ms 9.0s 0 transport_latency_assumed book c 1,170,524 519,448 29.7min 2.2d 36.3d 107.0d 0 book_staleness book e 116,963 3,638 43ms 171ms 38.4min 88.5d 0 book_staleness book f 790,546 218,598 17.5min 2.1d 36.0d 107.0d 0 book_staleness book g 1,143,305 788,901 27.4min 2.2d 36.3d 107.0d 0 book_staleness book h 118,132 22,419 21ms 77ms 1.3h 88.5d 0 book_staleness last_trade_price c 46,828 43,911 10ms 48ms 273ms 5.0s 0 transport_latency_assumed last_trade_price e 54,379 1,075 48ms 145ms 1.2s 9.4s 0 transport_latency_assumed last_trade_price f 49,365 226 53ms 134ms 728ms 8.4s 0 transport_latency_assumed last_trade_price g 46,644 27 93ms 218ms 2.5s 1.8min 0 transport_latency_assumed last_trade_price h 54,301 9,305 24ms 72ms 358ms 9.1s 0 transport_latency_assumed market_resolved c 2,606 2,524 5ms 4.8min 8.3min 8.5min 0 transport_latency_assumed market_resolved e 2,420 47 41ms 122ms 365ms 22.5s 0 transport_latency_assumed market_resolved f 2,390 57 47ms 130ms 4.4min 4.5min 0 transport_latency_assumed market_resolved g 3,257 861 165ms 11.5min 16.4min 16.9min 0 transport_latency_assumed market_resolved h 2,420 212 20ms 62ms 46.9s 1.1min 0 transport_latency_assumed new_market c 885 649 99ms 3.7min 24.7min 2.1h 0 transport_latency_assumed new_market e 861 136 197ms 17.0s 30.5s 20.7min 0 transport_latency_assumed new_market f 857 139 209ms 8.0min 8.3min 2.0h 0 transport_latency_assumed new_market g 1,587 670 1.9min 38.8min 46.2min 2.6h 0 transport_latency_assumed new_market h 858 304 141ms 17.6s 28.7s 3.3h 0 transport_latency_assumed price_change c 92,123,021 87,590,859 5ms 14ms 117ms 11.3s 0 transport_latency_assumed price_change e 104,857,540 1,865,502 41ms 59ms 277ms 9.6s 0 transport_latency_assumed price_change f 95,596,513 307,430 46ms 66ms 263ms 8.4s 0 transport_latency_assumed price_change g 91,232,507 23,434 83ms 113ms 577ms 1.8min 0 transport_latency_assumed price_change h 104,818,176 15,110,189 18ms 37ms 179ms 9.2s 0 transport_latency_assumed tick_size_change c 5,340 5,092 5ms 11ms 450ms 1.0s 0 transport_latency_assumed tick_size_change e 5,800 61 40ms 48ms 392ms 785ms 0 transport_latency_assumed tick_size_change f 5,584 28 46ms 59ms 334ms 527ms 0 transport_latency_assumed tick_size_change g 5,400 not meas. 82ms 100ms 639ms 43.8s 0 transport_latency_assumed tick_size_change h 5,800 619 18ms 30ms 283ms 1.1s 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-13/23/2026-09-13T23.parquet sha256sum 2026-09-13T23.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.