Hour audit: 2026-09-27T15
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-27T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T15:00:00.000105136+00:00 · last event 2026-09-27T15:59:59.999478235+00:00
VOLUME 111,348,532 rows · 1,250,732,619 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 109,135,263 · k: 109,130,672 · h: 109,108,274 · g: 108,529,198 · c: 86,794,821 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 22,699,031 (20.39%) · k: 11,405,074 (10.24%) · h: 1,718,441 (1.54%) · g: 44,340 (0.04%) · c: 75,481,646 (67.79%) (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 111,348,532 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 29f98f4498e905e2a1c88324446bca0cf47b425df41a1802bc448ab80f2c9105
the corpus checksum ledger names this file with the same digest
joined 111,356,932 to merged 111,348,532, minus 8,400 (minus 0.0075%)
boundary drops 8,400 · 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-27T18:21:18Z 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,801,380 128,283,936 0-41 c130d4127f4aa26b52b3da6f3b2ab70173a60628820cc3702687bbd61d7beee3 book 2,331,267 89,495,784 42-50 7ea7af8c814db63a99ddb55ac3c2ee869f1d813d51f5c6bdbfb987ebc355458d last_trade_price 73,497 4,138,924 51-51 5c55e45802968fa1b66a837ad672a1ceb0736c1f2d75c7c0a0e1837c7880da31 market_resolved 2,098 181,661 52-52 47edc88c564602543c26ed50105f2c9d71c7fac07f37d18392eed53f62dc5d0b new_market 5,809 430,375 53-53 1916760833b8704a0af104fca79363dbaa9e01750e5aee373e71f9f53ca66715 price_change 98,131,821 1,026,835,018 54-428 b946b2832f3004e8ab67b3ac0faa8e126563f6d322e5c01d089c5ebbee5de64e tick_size_change 2,660 98,176 429-429 61c235c897e9f3067051d74003a2920a1723a7f57bad2907c5b03b50187079c0 EVENT MIX count share price_change 98,131,821 88.13% best_bid_ask 10,801,380 9.70% book 2,331,267 2.09% last_trade_price 73,497 0.07% new_market 5,809 <0.01% tick_size_change 2,660 <0.01% market_resolved 2,098 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,801,565 10,801,380 185 3,970 FULL book 2,337,833 2,331,267 6,566 202,328 FULL last_trade_price 73,497 73,497 0 448 FULL market_resolved 2,136 2,098 38 176 FULL new_market 5,818 5,809 9 9 FULL price_change 98,133,423 98,131,821 1,602 2,375 FULL tick_size_change 2,660 2,660 0 152 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,337,436 7,285,199 5ms 18ms 220ms 8.7s 0 transport_latency_assumed best_bid_ask g 10,780,720 1,618 80ms 159ms 879ms 35.0s 0 transport_latency_assumed best_bid_ask h 10,799,732 143,959 19ms 34ms 331ms 54.9s 0 transport_latency_assumed best_bid_ask i 10,799,719 2,361,210 12ms 23ms 145ms 5.7s 0 transport_latency_assumed best_bid_ask k 10,799,668 1,009,394 13ms 25ms 198ms 26.9s 0 transport_latency_assumed book c 2,297,456 2,266,632 1.3h 4.7d 45.9d 120.7d 0 book_staleness book g 156,631 7,962 95ms 11.6s 2.8d 102.2d 0 book_staleness book h 154,354 4,853 25ms 270ms 16.5min 102.2d 0 book_staleness book i 155,014 28,086 18ms 448ms 12.5min 102.2d 0 book_staleness book k 153,891 23,734 17ms 102ms 1.3min 102.2d 0 book_staleness last_trade_price c 56,609 48,451 6ms 36ms 325ms 2.4s 0 transport_latency_assumed last_trade_price g 68,983 72 93ms 2.4s 16.9s 33.5s 0 transport_latency_assumed last_trade_price h 73,300 1,443 20ms 150ms 819ms 16.3s 0 transport_latency_assumed last_trade_price i 73,348 11,603 15ms 230ms 1.7s 5.7s 0 transport_latency_assumed last_trade_price k 73,307 11,928 14ms 58ms 358ms 8.7s 0 transport_latency_assumed market_resolved c 1,975 1,795 5.8min 21.4min 32.0min 34.5min 0 transport_latency_assumed market_resolved g 943 22 84ms 618ms 46.8s 48.7s 0 transport_latency_assumed market_resolved h 943 85 20ms 15.7s 50.8s 50.8s 0 transport_latency_assumed market_resolved i 943 98 15ms 22.4s 54.8s 54.8s 0 transport_latency_assumed market_resolved k 943 98 14ms 16.7s 50.6s 50.6s 0 transport_latency_assumed new_market c 5,235 3,702 4.3min 16.5min 17.5min 30.1min 0 transport_latency_assumed new_market g 2,622 120 289ms 1.5s 2.9min 4.7min 0 transport_latency_assumed new_market h 2,622 527 121ms 10.8s 2.7min 4.7min 0 transport_latency_assumed new_market i 2,622 1,074 87ms 8.7s 2.8min 4.7min 0 transport_latency_assumed new_market k 2,622 386 136ms 600ms 3.0min 4.7min 0 transport_latency_assumed price_change c 76,094,058 65,874,008 5ms 22ms 265ms 8.7s 0 transport_latency_assumed price_change g 97,516,639 34,546 81ms 234ms 4.3s 35.1s 0 transport_latency_assumed price_change h 98,074,663 1,567,550 19ms 43ms 469ms 57.9s 0 transport_latency_assumed price_change i 98,100,957 20,296,435 12ms 35ms 391ms 5.7s 0 transport_latency_assumed price_change k 98,097,581 10,359,282 13ms 30ms 249ms 27.9s 0 transport_latency_assumed tick_size_change c 2,052 1,859 5ms 13ms 77ms 136ms 0 transport_latency_assumed tick_size_change g 2,660 not meas. 79ms 98ms 243ms 585ms 0 transport_latency_assumed tick_size_change h 2,660 24 19ms 33ms 221ms 467ms 0 transport_latency_assumed tick_size_change i 2,660 525 12ms 21ms 63ms 235ms 0 transport_latency_assumed tick_size_change k 2,660 252 13ms 22ms 80ms 171ms 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/15/2026-09-27T15.parquet sha256sum 2026-09-27T15.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.