Hour audit: 2026-09-27T19
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-27T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T19:00:00.000023788+00:00 · last event 2026-09-27T19:59:59.999954660+00:00
VOLUME 139,859,602 rows · 1,660,136,228 bytes (1.55 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 135,893,498 · h: 135,806,449 · i: 132,450,002 · g: 124,102,231 · c: 86,769,462 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 39,514,142 (28.25%) · h: 6,714,009 (4.80%) · i: 19,094,139 (13.65%) · g: 234,886 (0.17%) · c: 74,302,426 (53.13%) (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 139,859,602 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d2c6e9ee3b724d1184669bdf5de1f77b8e96406dbb3b056c0ee237e5ec718ed1
the corpus checksum ledger names this file with the same digest
joined 139,865,597 to merged 139,859,602, minus 5,995 (minus 0.0043%)
boundary drops 5,995 · 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-27T22:17:01Z 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,381,591 184,946,429 0-58 45c5971344cdcc35c67f2f3f88c0c852b97d72979f4beddec6f1bd9c918a91a8 book 4,082,102 109,576,164 59-74 cb24295dfa038a56b77bbb146cbb548fb4d2a990de6b0708e12373ed1b23ca75 last_trade_price 65,841 3,799,079 75-75 c45a277ce86bd24437f9fe35c8c3a82cb2bb0a8c391c751152c3789b2d7e4bbf market_resolved 7,649 496,644 76-76 570f35fc8c31bbd09b176e6a2474dcae7aaab2ab4e66e6f741cb0e75b6854cc2 new_market 12,611 602,125 77-77 0b5134481925a9bcead843a82a88fec4c06ec6ef6e1a5529bc5f8026ca48199d price_change 120,303,364 1,358,890,594 78-536 c4a878fd216bd0c91478afc60042281348c4711db23d4ecaafa4af01820709f2 tick_size_change 6,444 237,956 537-537 ee1161230d60e5bc648df226bf11ecea8dd3347b31463ab3ef4500f9f0838ea6 EVENT MIX count share price_change 120,303,364 86.02% best_bid_ask 15,381,591 11.00% book 4,082,102 2.92% last_trade_price 65,841 0.05% new_market 12,611 <0.01% market_resolved 7,649 <0.01% tick_size_change 6,444 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,381,983 15,381,591 392 8,575 FULL book 4,085,172 4,082,102 3,070 209,719 FULL last_trade_price 65,841 65,841 0 1,045 FULL market_resolved 7,649 7,649 0 907 FULL new_market 12,612 12,611 1 206 FULL price_change 120,305,896 120,303,364 2,532 7,836 FULL tick_size_change 6,444 6,444 0 814 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,470,118 8,087,521 6ms 23ms 361ms 24.0s 0 transport_latency_assumed best_bid_ask g 14,008,243 3,129 81ms 167ms 1.4s 44.1s 0 transport_latency_assumed best_bid_ask h 15,376,338 736,496 18ms 33ms 750ms 1.8min 0 transport_latency_assumed best_bid_ask i 14,994,031 2,127,653 18ms 27ms 222ms 7.4s 0 transport_latency_assumed best_bid_ask k 15,377,783 4,426,792 13ms 29ms 411ms 1.0min 0 transport_latency_assumed book c 3,891,674 3,794,890 1.3h 4.9d 46.0d 120.9d 0 book_staleness book g 994,215 197,852 47.6min 2.9d 42.0d 120.9d 0 book_staleness book h 147,394 13,989 23ms 1.2s 15.7h 120.9d 0 book_staleness book i 157,147 28,868 23ms 2.6min 8.2d 102.4d 0 book_staleness book k 161,248 46,503 20ms 10.3min 9.2d 102.4d 0 book_staleness last_trade_price c 37,647 32,226 7ms 35ms 463ms 21.7s 0 transport_latency_assumed last_trade_price g 57,365 25 89ms 821ms 16.0s 36.5s 0 transport_latency_assumed last_trade_price h 65,747 3,749 19ms 91ms 1.3s 1.1min 0 transport_latency_assumed last_trade_price i 65,168 8,604 21ms 87ms 860ms 4.2s 0 transport_latency_assumed last_trade_price k 65,713 21,237 14ms 67ms 731ms 1.0min 0 transport_latency_assumed market_resolved c 6,831 6,342 14.9min 35.0min 43.7min 44.2min 0 transport_latency_assumed market_resolved g 2,131 212 84ms 5.2min 11.5min 11.8min 0 transport_latency_assumed market_resolved h 1,954 293 18ms 17.4s 47.5s 57.5s 0 transport_latency_assumed market_resolved i 1,914 314 18ms 226ms 51.5s 2.3min 0 transport_latency_assumed market_resolved k 1,954 488 13ms 19.3s 49.4s 55.3s 0 transport_latency_assumed new_market c 12,226 9,289 9.2min 22.2min 30.8min 40.6min 0 transport_latency_assumed new_market g 3,280 460 709ms 1.3min 4.7min 9.3min 0 transport_latency_assumed new_market h 3,208 830 262ms 1.3min 1.4min 1.7min 0 transport_latency_assumed new_market i 3,208 1,211 221ms 1.3min 1.4min 1.7min 0 transport_latency_assumed new_market k 3,208 821 298ms 1.3min 1.4min 1.6min 0 transport_latency_assumed price_change c 73,347,334 62,369,022 6ms 26ms 373ms 24.0s 0 transport_latency_assumed price_change g 109,031,245 33,208 81ms 213ms 3.2s 45.3s 0 transport_latency_assumed price_change h 120,205,364 5,958,354 18ms 39ms 869ms 1.8min 0 transport_latency_assumed price_change i 117,222,242 16,926,485 19ms 33ms 292ms 7.4s 0 transport_latency_assumed price_change k 120,277,148 35,016,295 13ms 33ms 451ms 1.0min 0 transport_latency_assumed tick_size_change c 3,632 3,136 6ms 22ms 314ms 809ms 0 transport_latency_assumed tick_size_change g 5,752 not meas. 80ms 126ms 1.1s 4.5s 0 transport_latency_assumed tick_size_change h 6,444 298 18ms 37ms 871ms 21.4s 0 transport_latency_assumed tick_size_change i 6,292 1,004 19ms 29ms 281ms 847ms 0 transport_latency_assumed tick_size_change k 6,444 2,006 13ms 30ms 380ms 26.0s 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/19/2026-09-27T19.parquet sha256sum 2026-09-27T19.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.