Hour audit: 2026-09-27T06
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-27T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T06:00:00.000238169+00:00 · last event 2026-09-27T06:59:59.999895663+00:00
VOLUME 75,579,254 rows · 766,583,824 bytes (731.07 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 75,490,386 · k: 75,487,295 · h: 75,473,211 · i: 75,470,005 · g: 75,433,081 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 72,590,003 (96.04%) · k: 2,037,344 (2.70%) · h: 389,643 (0.52%) · i: 543,648 (0.72%) · g: 18,616 (0.02%) (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 75,579,254 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d9472130ff9aa2bc1e087cb5970eb5a851c2169df91ca565592fd908dfd33d83
the corpus checksum ledger names this file with the same digest
joined 75,580,643 to merged 75,579,254, minus 1,389 (minus 0.0018%)
boundary drops 1,389 · 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-27T14:26: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 9,390,608 102,117,340 0-35 21af1ce5cf34c130b53a43c14f017876d7d3b7446842bda04ea63e7e6fb788bc book 162,797 15,812,380 36-36 56dedf1866643501b0cd3bfce98d9bb58742620dcdf4aa888f03e388df0a6b97 last_trade_price 41,328 2,385,929 37-37 a24182a42b47c5ecd0385b6f62b14fe1e77f2b20ce4d4aa7e2382a2cf8b5c957 market_resolved 1,353 210,085 38-38 82ad917413523a3b60569b004ace6c79ec4a8103f870535d8c6364a6ca9d331c new_market 1,864 183,044 39-39 a7bf42c5bcb2401eda2cc8d6c2a06729cc4b8cecd334d5d589be8f9406812f8e price_change 65,979,692 644,951,888 40-291 ab2df700fa89fcb99e5766764b1a3cbd9f02957ec990b65a50f700a0fb17fa42 tick_size_change 1,612 58,909 292-292 da44963bb316b235864ff70b6c6edde0b06483a3ed419c7a55da0e245534382a EVENT MIX count share price_change 65,979,692 87.30% best_bid_ask 9,390,608 12.42% book 162,797 0.22% last_trade_price 41,328 0.05% new_market 1,864 <0.01% tick_size_change 1,612 <0.01% market_resolved 1,353 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,390,808 9,390,608 200 255 FULL book 162,801 162,797 4 36,653 FULL last_trade_price 41,329 41,328 1 0 FULL market_resolved 1,367 1,353 14 35 FULL new_market 1,864 1,864 0 0 FULL price_change 65,980,862 65,979,692 1,170 110 FULL tick_size_change 1,612 1,612 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,389,328 9,065,787 4ms 7ms 80ms 3.9s 0 transport_latency_assumed best_bid_ask g 9,387,591 526 77ms 92ms 423ms 22.8s 0 transport_latency_assumed best_bid_ask h 9,388,988 39,648 18ms 20ms 177ms 1.2min 0 transport_latency_assumed best_bid_ask i 9,388,778 57,545 20ms 23ms 82ms 4.0s 0 transport_latency_assumed best_bid_ask k 9,388,848 227,102 12ms 14ms 93ms 50.5s 0 transport_latency_assumed book c 114,498 107,991 7ms 2.3h 20.3d 120.3d 0 book_staleness book g 97,778 12,652 82ms 2.4min 10.1d 120.3d 0 book_staleness book h 92,839 8,465 21ms 716ms 2.4d 101.8d 0 book_staleness book i 107,720 22,182 22ms 1.3h 19.8d 120.3d 0 book_staleness book k 93,632 11,507 15ms 2.2s 4.5d 101.8d 0 book_staleness last_trade_price c 41,193 39,172 5ms 10ms 146ms 2.8s 0 transport_latency_assumed last_trade_price g 41,103 4 80ms 197ms 3.0s 22.9s 0 transport_latency_assumed last_trade_price h 41,310 300 19ms 28ms 283ms 23.9s 0 transport_latency_assumed last_trade_price i 41,217 291 21ms 30ms 191ms 1.2s 0 transport_latency_assumed last_trade_price k 41,287 1,561 13ms 19ms 188ms 1.5s 0 transport_latency_assumed market_resolved c 1,259 1,165 5ms 10ms 48.3s 48.3s 0 transport_latency_assumed market_resolved g 1,291 52 79ms 253ms 45.4s 53.5s 0 transport_latency_assumed market_resolved h 1,262 10 18ms 101ms 53.8s 55.7s 0 transport_latency_assumed market_resolved i 1,262 13 21ms 83ms 40.5s 56.5s 0 transport_latency_assumed market_resolved k 1,262 113 13ms 61ms 54.2s 54.3s 0 transport_latency_assumed new_market c 1,216 728 99ms 20.1s 1.4min 1.6min 0 transport_latency_assumed new_market g 1,216 68 369ms 25.1s 1.4min 1.7min 0 transport_latency_assumed new_market h 1,216 312 177ms 28.0s 57.5s 1.6min 0 transport_latency_assumed new_market i 1,216 511 126ms 43.6s 1.4min 1.5min 0 transport_latency_assumed new_market k 1,216 245 183ms 36.1s 1.3min 1.7min 0 transport_latency_assumed price_change c 65,941,280 63,373,576 4ms 7ms 106ms 9.4s 0 transport_latency_assumed price_change g 65,902,490 5,314 77ms 94ms 744ms 23.1s 0 transport_latency_assumed price_change h 65,945,984 340,904 18ms 22ms 262ms 1.4min 0 transport_latency_assumed price_change i 65,928,200 463,106 20ms 24ms 152ms 4.2s 0 transport_latency_assumed price_change k 65,959,438 1,796,792 12ms 15ms 126ms 52.6s 0 transport_latency_assumed tick_size_change c 1,612 1,584 4ms 7ms 25ms 46ms 0 transport_latency_assumed tick_size_change g 1,612 not meas. 77ms 91ms 102ms 176ms 0 transport_latency_assumed tick_size_change h 1,612 4 18ms 20ms 42ms 126ms 0 transport_latency_assumed tick_size_change i 1,612 not meas. 20ms 23ms 27ms 48ms 0 transport_latency_assumed tick_size_change k 1,612 24 12ms 14ms 26ms 76ms 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/06/2026-09-27T06.parquet sha256sum 2026-09-27T06.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.