Hour audit: 2026-09-24T00
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-24T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T00:00:00.000002987+00:00 · last event 2026-09-24T00:59:59.998079925+00:00
VOLUME 118,832,894 rows · 1,259,394,908 bytes (1.17 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 118,361,709 · k: 118,011,425 · g: 117,940,574 · h: 117,833,418 · c: 112,741,930 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,603,621 (1.35%) · k: 10,309,538 (8.68%) · g: 21,091 (0.02%) · h: 2,212,225 (1.86%) · c: 104,686,419 (88.10%) (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 118,832,894 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 eb00bedbe262192e71aef9799d618c8cb7beef38bda2c8c7cfbbcce1ff242173
the corpus checksum ledger names this file with the same digest
joined 118,851,365 to merged 118,832,894, minus 18,471 (minus 0.0155%)
boundary drops 18,471 · 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-24T06:57:23Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 11,979,242 137,027,356 0-45 b463f985bdb1b5a1e301464c4dfdef9f04336399fceca34b9f504b42a56e04f9 book 877,170 63,440,463 46-49 5a4356570b0e25c5e896771d28eea008f8d7b3fd5da72e313f2d1df04f0f9b1a last_trade_price 52,220 2,921,553 50-50 2f61ca43d9aaaa4a6366e827be914e251aecc91b5b6721537f9f6fbafa801842 market_resolved 1,008 154,715 51-51 57062dfc55291e734ac6fd5df8d5426a245913c3724189805bd07ac505131e59 new_market 1,455 157,232 52-52 9f893aea37c9e7cd0dedd1b7aeff9dbb72da6d9f8f28c523d4085b147599959f price_change 105,918,795 1,054,228,812 53-457 448698c98ca8712cfd40de4fe638af3c0b1dff6148842e057f40bc726ee7a1c2 tick_size_change 3,004 110,517 458-458 d8aad4de8c9c722518829137137463aa49b019bedf0c88cd4945aca041950c8b EVENT MIX count share price_change 105,918,795 89.13% best_bid_ask 11,979,242 10.08% book 877,170 0.74% last_trade_price 52,220 0.04% tick_size_change 3,004 <0.01% new_market 1,455 <0.01% market_resolved 1,008 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,979,442 11,979,242 200 759 FULL book 893,588 877,170 16,418 196,081 FULL last_trade_price 52,220 52,220 0 69 FULL market_resolved 1,046 1,008 38 248 FULL new_market 1,457 1,455 2 2 FULL price_change 105,920,608 105,918,795 1,813 786 FULL tick_size_change 3,004 3,004 0 45 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,402,924 10,655,011 5ms 11ms 91ms 1.8s 0 transport_latency_assumed best_bid_ask g 11,975,912 923 83ms 108ms 335ms 19.4s 0 transport_latency_assumed best_bid_ask h 11,970,372 206,537 17ms 30ms 130ms 7.1s 0 transport_latency_assumed best_bid_ask i 11,974,718 125,097 21ms 31ms 113ms 4.1s 0 transport_latency_assumed best_bid_ask k 11,977,361 991,674 13ms 21ms 110ms 11.5s 0 transport_latency_assumed book c 622,634 591,312 7.1min 3.3d 39.4d 117.1d 0 book_staleness book g 110,160 3,219 89ms 777ms 1.1d 98.6d 0 book_staleness book h 120,335 16,141 22ms 48.3s 2.2d 98.6d 0 book_staleness book i 475,754 248,772 3.4min 2.3d 34.8d 117.1d 0 book_staleness book k 114,897 17,726 16ms 241ms 3.1d 117.1d 0 book_staleness last_trade_price c 48,753 43,614 6ms 30ms 231ms 1.0s 0 transport_latency_assumed last_trade_price g 51,613 81 88ms 299ms 6.3s 19.3s 0 transport_latency_assumed last_trade_price h 51,350 1,240 19ms 72ms 416ms 4.0s 0 transport_latency_assumed last_trade_price i 52,034 909 23ms 86ms 446ms 3.8s 0 transport_latency_assumed last_trade_price k 51,944 6,376 14ms 45ms 268ms 2.1s 0 transport_latency_assumed market_resolved c 991 875 6ms 5.2min 6.3min 6.3min 0 transport_latency_assumed market_resolved g 757 not meas. 85ms 387ms 50.8s 53.0s 0 transport_latency_assumed market_resolved h 757 8 18ms 117ms 40.3s 41.7s 0 transport_latency_assumed market_resolved i 757 52 22ms 159ms 40.0s 41.6s 0 transport_latency_assumed market_resolved k 757 73 13ms 81ms 46.2s 48.1s 0 transport_latency_assumed new_market c 1,020 547 58ms 25.7s 4.3min 5.6min 0 transport_latency_assumed new_market g 1,018 108 189ms 23.0s 1.3min 1.6min 0 transport_latency_assumed new_market h 1,018 323 60ms 19.8s 1.3min 1.6min 0 transport_latency_assumed new_market i 1,018 269 70ms 16.3s 1.3min 1.5min 0 transport_latency_assumed new_market k 1,018 208 99ms 20.5s 1.3min 1.8min 0 transport_latency_assumed price_change c 100,662,784 93,392,501 5ms 14ms 104ms 1.8s 0 transport_latency_assumed price_change g 105,798,110 16,760 83ms 120ms 477ms 19.4s 0 transport_latency_assumed price_change h 105,686,582 1,987,932 18ms 34ms 162ms 7.5s 0 transport_latency_assumed price_change i 105,854,424 1,228,506 21ms 35ms 145ms 4.3s 0 transport_latency_assumed price_change k 105,862,444 9,293,096 13ms 25ms 128ms 11.5s 0 transport_latency_assumed tick_size_change c 2,824 2,559 5ms 13ms 96ms 312ms 0 transport_latency_assumed tick_size_change g 3,004 not meas. 82ms 99ms 219ms 296ms 0 transport_latency_assumed tick_size_change h 3,004 44 18ms 28ms 58ms 120ms 0 transport_latency_assumed tick_size_change i 3,004 16 21ms 28ms 75ms 137ms 0 transport_latency_assumed tick_size_change k 3,004 385 13ms 21ms 76ms 160ms 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-24/00/2026-09-24T00.parquet sha256sum 2026-09-24T00.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.