Hour audit: 2026-09-27T01
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-27T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T01:00:00.000006718+00:00 · last event 2026-09-27T01:59:59.999763407+00:00
VOLUME 145,167,742 rows · 1,639,548,872 bytes (1.53 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 130,112,862 · h: 126,475,213 · k: 124,540,948 · g: 124,537,655 · c: 93,728,832 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 3,625,425 (2.50%) · h: 12,410,705 (8.55%) · k: 41,502,013 (28.59%) · g: 1,260,708 (0.87%) · c: 86,368,891 (59.50%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 d2219d36e568c7b825a2e022ae7f4585047295f0d19494715df186d292618955
the corpus checksum ledger names this file with the same digest
joined 145,172,033 to merged 145,167,742, minus 4,291 (minus 0.0030%)
boundary drops 4,291 · 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-28T16:08:12Z 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 15,968,464 181,081,401 0-60 a36309e2eb15a10fbf14475f7b4fe382f90717c6cb3eb2d4a6f4f6e43448e122 book 4,150,783 121,878,025 61-76 e3f0cb36b23ced39b63df6f4e6c682887691191c66b0ef8dbafcdf1f63aff1dd last_trade_price 44,541 2,640,044 77-77 763e58e8289988c9b7c10581cc738b95d8ed3f1752a533c1fb778acffa16b578 market_resolved 11,390 528,297 78-78 82792db3c0ddf32478d4dc64e3af911a7681552caa0a440cac5f93a5ea692de8 new_market 4,652 158,040 79-79 0d4f7049d0e211d3d3fd520c17418929892b0fce91c1a6b6d93c73dadd947569 price_change 124,975,256 1,331,159,995 80-556 70d7112e33835d3f738286e9a89a4a27034b014a2d5380406d42604300057129 tick_size_change 12,656 457,287 557-557 389028b0488b685061381dcaa358dde1f02da21a9a255b59094e70eb2f6e1f91 EVENT MIX count share price_change 124,975,256 86.09% best_bid_ask 15,968,464 11.00% book 4,150,783 2.86% last_trade_price 44,541 0.03% tick_size_change 12,656 <0.01% market_resolved 11,390 <0.01% new_market 4,652 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,968,606 15,968,464 142 9,234 FULL book 4,153,541 4,150,783 2,758 1,078 FULL last_trade_price 44,542 44,541 1 967 FULL market_resolved 11,390 11,390 0 463 FULL new_market 4,652 4,652 0 68 FULL price_change 124,976,646 124,975,256 1,390 7,630 FULL tick_size_change 12,656 12,656 0 1,202 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,186,039 9,410,567 5ms 13ms 99ms 1.9s 0 transport_latency_assumed best_bid_ask g 13,952,759 108,945 80ms 100ms 323ms 30.2s 0 transport_latency_assumed best_bid_ask h 14,179,133 1,343,900 18ms 53ms 160ms 19.5s 0 transport_latency_assumed best_bid_ask i 14,602,308 377,787 22ms 28ms 105ms 4.3s 0 transport_latency_assumed best_bid_ask k 13,951,060 4,727,265 13ms 19ms 88ms 2.6s 0 transport_latency_assumed book c 3,459,577 3,024,486 1.5h 6.2d 46.3d 120.2d 0 book_staleness book g 1,326,192 285,168 1.2h 5.2d 45.3d 120.1d 0 book_staleness book h 1,319,293 584,989 1.2h 5.3d 45.3d 120.1d 0 book_staleness book i 920,969 96,495 1.1h 5.2d 45.2d 120.1d 0 book_staleness book k 1,315,955 159,645 1.2h 5.2d 45.3d 120.1d 0 book_staleness last_trade_price c 27,241 24,381 6ms 22ms 219ms 1.7s 0 transport_latency_assumed last_trade_price g 38,564 386 84ms 178ms 1.4s 30.3s 0 transport_latency_assumed last_trade_price h 38,900 4,187 21ms 64ms 342ms 3.9s 0 transport_latency_assumed last_trade_price i 40,570 1,743 23ms 46ms 311ms 3.7s 0 transport_latency_assumed last_trade_price k 38,444 13,844 14ms 29ms 238ms 1.6s 0 transport_latency_assumed market_resolved c 10,221 9,428 15.3min 38.8min 51.8min 53.8min 0 transport_latency_assumed market_resolved g 2,959 421 83ms 3.4min 9.2min 10.3min 0 transport_latency_assumed market_resolved h 2,955 420 21ms 3.0min 6.9min 7.9min 0 transport_latency_assumed market_resolved i 3,043 89 23ms 4.5min 9.1min 10.1min 0 transport_latency_assumed market_resolved k 3,377 1,032 15ms 9.2min 14.0min 15.0min 0 transport_latency_assumed new_market c 4,366 3,582 17.2min 36.8min 51.8min 149.2d 0 transport_latency_assumed new_market g 811 116 292ms 4.9min 6.9min 8.9min 0 transport_latency_assumed new_market h 852 253 118ms 58.9s 6.1min 149.2d 0 transport_latency_assumed new_market i 897 380 53ms 3.9min 6.2min 6.2min 0 transport_latency_assumed new_market k 970 321 98ms 6.1min 11.1min 149.2d 0 transport_latency_assumed price_change c 80,032,128 73,888,300 5ms 13ms 104ms 2.0s 0 transport_latency_assumed price_change g 109,204,778 865,638 80ms 104ms 439ms 30.3s 0 transport_latency_assumed price_change h 110,922,320 10,475,762 19ms 55ms 206ms 19.9s 0 transport_latency_assumed price_change i 114,533,503 3,148,592 22ms 30ms 145ms 4.3s 0 transport_latency_assumed price_change k 109,220,122 36,596,964 13ms 20ms 106ms 2.8s 0 transport_latency_assumed tick_size_change c 9,260 8,147 5ms 21ms 374ms 557ms 0 transport_latency_assumed tick_size_change g 11,592 34 82ms 324ms 1.2s 3.5s 0 transport_latency_assumed tick_size_change h 11,760 1,194 18ms 50ms 432ms 1.3s 0 transport_latency_assumed tick_size_change i 11,572 339 22ms 30ms 209ms 467ms 0 transport_latency_assumed tick_size_change k 11,020 2,942 13ms 20ms 159ms 366ms 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/01/2026-09-27T01.parquet sha256sum 2026-09-27T01.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.