Hour audit: 2026-09-27T11
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-27T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T11:00:00.000081184+00:00 · last event 2026-09-27T11:59:59.999952940+00:00
VOLUME 105,326,694 rows · 1,125,989,246 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 103,671,063 · k: 103,661,961 · h: 103,633,421 · g: 103,334,248 · c: 87,196,695 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,084,361 (1.03%) · k: 22,163,930 (21.04%) · h: 2,822,872 (2.68%) · g: 20,102 (0.02%) · c: 79,235,429 (75.23%) (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 105,326,694 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7fc4e6844458ddfb079658d4ea98ea087e3795dd61a48170f5f1a668135a2063
the corpus checksum ledger names this file with the same digest
joined 105,328,363 to merged 105,326,694, minus 1,669 (minus 0.0016%)
boundary drops 1,669 · 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-27T16:33:09Z 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 10,729,730 120,708,398 0-40 88aa78da1307e1b5827a6c6832559e1ddbdf607038f2b635f8fce2f7ec6953f9 book 1,726,342 76,950,070 41-47 f275431d21294874ac018357522804a4120e61c412786d9dd5bb8ca687048b91 last_trade_price 50,573 2,959,290 48-48 9e5b22b0183368ffa7b14dabf39b4b50b8f8626f08eaeb8ee7a44800426711f6 market_resolved 1,413 141,957 49-49 087365884c4f05b038513f81d274064faf0a119ddecfedafd6dbbaac8eee1ff8 new_market 5,726 460,702 50-50 446debeb794d4f9784a40f7c52283ac52c18fcfa19aeba81c127e42292741585 price_change 92,810,366 923,474,066 51-405 fcccb9969702ce5a6664d7266dd3b8d1f8c627f206b88f3e948a1d7e8e513f27 tick_size_change 2,544 93,963 406-406 3ec8a52709325e2b1e8650e0001e45a12b790fa7305e1dd052ffaee407ac84e3 EVENT MIX count share price_change 92,810,366 88.12% best_bid_ask 10,729,730 10.19% book 1,726,342 1.64% last_trade_price 50,573 0.05% new_market 5,726 <0.01% tick_size_change 2,544 <0.01% market_resolved 1,413 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,729,922 10,729,730 192 2,271 FULL book 1,726,350 1,726,342 8 197,102 FULL last_trade_price 50,573 50,573 0 355 FULL market_resolved 1,413 1,413 0 119 FULL new_market 5,729 5,726 3 28 FULL price_change 92,811,832 92,810,366 1,466 1,461 FULL tick_size_change 2,544 2,544 0 148 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,845,915 8,049,501 5ms 14ms 282ms 8.8s 0 transport_latency_assumed best_bid_ask g 10,718,188 1,608 78ms 131ms 919ms 36.3s 0 transport_latency_assumed best_bid_ask h 10,725,614 279,368 18ms 26ms 493ms 2.0min 0 transport_latency_assumed best_bid_ask i 10,726,070 108,846 43ms 51ms 188ms 7.6s 0 transport_latency_assumed best_bid_ask k 10,725,948 2,290,407 12ms 19ms 238ms 36.4s 0 transport_latency_assumed book c 1,700,689 1,685,829 1.6h 4.7d 45.9d 120.6d 0 book_staleness book g 116,138 6,151 91ms 13.1s 5.6d 120.5d 0 book_staleness book h 109,258 6,276 23ms 255ms 6.9h 102.0d 0 book_staleness book i 107,372 3,540 47ms 175ms 6.9s 102.0d 0 book_staleness book k 108,841 24,546 16ms 157ms 4.7h 102.0d 0 book_staleness last_trade_price c 41,462 36,784 6ms 29ms 332ms 4.5s 0 transport_latency_assumed last_trade_price g 49,319 12 88ms 573ms 11.0s 36.7s 0 transport_latency_assumed last_trade_price h 50,308 1,793 19ms 77ms 673ms 1.9min 0 transport_latency_assumed last_trade_price i 50,410 642 45ms 101ms 618ms 3.0s 0 transport_latency_assumed last_trade_price k 50,325 11,342 13ms 43ms 395ms 36.3s 0 transport_latency_assumed market_resolved c 1,281 1,139 38.1s 18.5min 26.6min 27.6min 0 transport_latency_assumed market_resolved g 773 3 89ms 49.5s 55.4s 55.5s 0 transport_latency_assumed market_resolved h 773 174 20ms 27.1s 35.1s 49.7s 0 transport_latency_assumed market_resolved i 773 9 48ms 47.2s 52.3s 55.9s 0 transport_latency_assumed market_resolved k 773 88 15ms 33.4s 41.8s 54.6s 0 transport_latency_assumed new_market c 4,371 2,752 413ms 14.1min 15.9min 23.7min 0 transport_latency_assumed new_market g 2,798 338 350ms 31.0s 1.0min 1.6min 0 transport_latency_assumed new_market h 2,798 923 189ms 30.6s 1.0min 1.6min 0 transport_latency_assumed new_market i 2,798 718 173ms 30.6s 53.6s 1.6min 0 transport_latency_assumed new_market k 2,798 995 193ms 31.4s 1.0min 1.5min 0 transport_latency_assumed price_change c 76,601,025 69,457,770 5ms 15ms 288ms 9.1s 0 transport_latency_assumed price_change g 92,444,488 11,990 79ms 177ms 2.6s 37.1s 0 transport_latency_assumed price_change h 92,742,126 2,534,230 18ms 30ms 534ms 2.0min 0 transport_latency_assumed price_change i 92,781,096 970,570 44ms 53ms 253ms 7.6s 0 transport_latency_assumed price_change k 92,770,732 19,835,806 12ms 21ms 252ms 37.1s 0 transport_latency_assumed tick_size_change c 1,952 1,654 5ms 32ms 183ms 273ms 0 transport_latency_assumed tick_size_change g 2,544 not meas. 78ms 160ms 747ms 1.2s 0 transport_latency_assumed tick_size_change h 2,544 108 18ms 31ms 861ms 3.2s 0 transport_latency_assumed tick_size_change i 2,544 36 44ms 53ms 183ms 571ms 0 transport_latency_assumed tick_size_change k 2,544 746 12ms 25ms 233ms 555ms 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/11/2026-09-27T11.parquet sha256sum 2026-09-27T11.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.