Hour audit: 2026-09-27T21
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-27T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T21:00:00.000466513+00:00 · last event 2026-09-27T21:59:59.999999046+00:00
VOLUME 123,907,604 rows · 1,399,021,569 bytes (1.30 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 121,270,900 · h: 121,222,604 · g: 121,124,219 · i: 118,262,443 · c: 90,119,398 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 25,171,402 (20.31%) · h: 4,351,984 (3.51%) · g: 13,139 (0.01%) · i: 12,377,161 (9.99%) · c: 81,993,918 (66.17%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 84615ea7e3e54ed6b5f6b85d57f44820a0222cbb9af39a128522488658b27bbb
the corpus checksum ledger names this file with the same digest
joined 123,912,051 to merged 123,907,604, minus 4,447 (minus 0.0036%)
boundary drops 4,447 · 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-28T00:09:48Z 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 13,206,579 152,719,375 0-50 b24ef0854baa03bf7d7a82dca11e8a3ec21b3c03ca2fa0e052dc1f8574036506 book 2,686,454 86,115,920 51-61 a911c90bdcd78d096a723f420820ada45e148c7193b26f9e85188c7ee37cc392 last_trade_price 48,356 2,838,896 62-62 3007eb3fb94171a4bfa014b68d8cad787b8ed1c63c0ea94542dd248bf537a19f market_resolved 15,637 975,166 63-63 559b435265162719f66fdae1c2736a3e59b49ca753ff1865f41e022c75fc8a01 new_market 5,860 283,873 64-64 33cf5ec35fd1300cd4ae0dee6751b17766731c424d6abc8cabb97886ab272a83 price_change 107,937,766 1,154,422,252 65-476 972a75128ef7640c53d181cb5db014a65f396d48bc19fc67e3922ead0771ef21 tick_size_change 6,952 255,430 477-477 d3c026871fe738d17fbe5b6a57462b88a7ed9bf7f72d703937e777a636e495e4 EVENT MIX count share price_change 107,937,766 87.11% best_bid_ask 13,206,579 10.66% book 2,686,454 2.17% last_trade_price 48,356 0.04% market_resolved 15,637 0.01% tick_size_change 6,952 <0.01% new_market 5,860 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,206,862 13,206,579 283 5,738 FULL book 2,686,472 2,686,454 18 210,382 FULL last_trade_price 48,356 48,356 0 650 FULL market_resolved 15,651 15,637 14 423 FULL new_market 5,862 5,860 2 225 FULL price_change 107,941,896 107,937,766 4,130 4,526 FULL tick_size_change 6,952 6,952 0 471 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,640,125 8,757,537 5ms 12ms 147ms 6.9s 0 transport_latency_assumed best_bid_ask g 13,201,098 1,305 83ms 119ms 661ms 29.8s 0 transport_latency_assumed best_bid_ask h 13,203,416 438,035 18ms 24ms 254ms 45.7s 0 transport_latency_assumed best_bid_ask i 12,887,280 1,362,067 16ms 41ms 111ms 5.4s 0 transport_latency_assumed best_bid_ask k 13,204,053 2,647,635 13ms 22ms 189ms 19.7s 0 transport_latency_assumed book c 2,651,781 2,641,449 2.2h 5.0d 46.1d 121.0d 0 book_staleness book g 101,304 1,621 91ms 2.9s 12.1h 102.4d 0 book_staleness book h 104,929 7,950 22ms 204ms 17.7h 102.5d 0 book_staleness book i 109,354 15,472 25ms 4.2s 6.1d 102.5d 0 book_staleness book k 102,481 19,962 17ms 134ms 11.1h 102.5d 0 book_staleness last_trade_price c 34,321 30,590 6ms 22ms 313ms 1.3s 0 transport_latency_assumed last_trade_price g 47,661 27 93ms 1.2s 16.0s 29.7s 0 transport_latency_assumed last_trade_price h 48,177 2,513 19ms 45ms 546ms 21.1s 0 transport_latency_assumed last_trade_price i 47,802 5,010 20ms 77ms 1.1s 5.4s 0 transport_latency_assumed last_trade_price k 48,164 10,216 14ms 48ms 489ms 9.1s 0 transport_latency_assumed market_resolved c 13,909 13,237 9.9min 32.2min 44.2min 47.5min 0 transport_latency_assumed market_resolved g 5,120 201 84ms 260ms 52.9s 58.6s 0 transport_latency_assumed market_resolved h 5,120 764 18ms 26.3s 53.0s 56.9s 0 transport_latency_assumed market_resolved i 5,057 526 20ms 26.5s 54.8s 2.5min 0 transport_latency_assumed market_resolved k 5,120 909 13ms 19.1s 51.8s 56.9s 0 transport_latency_assumed new_market c 5,503 4,469 14.6min 37.5min 57.0min 57.3min 0 transport_latency_assumed new_market g 1,381 133 356ms 28.6s 51.3s 1.2min 0 transport_latency_assumed new_market h 1,381 381 150ms 24.2s 56.5s 1.5min 0 transport_latency_assumed new_market i 1,381 535 112ms 22.9s 50.2s 1.7min 0 transport_latency_assumed new_market k 1,381 342 188ms 20.9s 53.9s 1.7min 0 transport_latency_assumed price_change c 77,768,563 70,541,853 5ms 13ms 154ms 6.9s 0 transport_latency_assumed price_change g 107,760,703 9,848 83ms 154ms 2.2s 29.8s 0 transport_latency_assumed price_change h 107,852,629 3,902,009 18ms 26ms 286ms 45.7s 0 transport_latency_assumed price_change i 105,204,829 10,992,854 17ms 43ms 179ms 5.4s 0 transport_latency_assumed price_change k 107,902,749 22,491,202 13ms 24ms 209ms 19.7s 0 transport_latency_assumed tick_size_change c 5,196 4,783 5ms 11ms 56ms 134ms 0 transport_latency_assumed tick_size_change g 6,952 4 83ms 125ms 365ms 1.0s 0 transport_latency_assumed tick_size_change h 6,952 332 18ms 32ms 170ms 1.3s 0 transport_latency_assumed tick_size_change i 6,740 697 16ms 40ms 77ms 169ms 0 transport_latency_assumed tick_size_change k 6,952 1,136 13ms 24ms 139ms 1.9s 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-27/21/2026-09-27T21.parquet sha256sum 2026-09-27T21.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.