Hour audit: 2026-09-28T09
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-28T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T09:00:00.000003369+00:00 · last event 2026-09-28T09:59:59.999996760+00:00
VOLUME 107,294,569 rows · 1,180,105,989 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 106,637,583 · i: 106,135,678 · g: 106,075,395 · h: 103,839,500 · c: 101,938,184 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 12,724,929 (11.86%) · i: 1,358,030 (1.27%) · g: 11,088 (0.01%) · h: 2,338,282 (2.18%) · c: 90,862,240 (84.68%) (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 107,294,569 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b55a93766764eb5bacac1d0f850f0c35dfc1ceefbb99b4ae1e69839cedbe97ec
the corpus checksum ledger names this file with the same digest
joined 107,296,410 to merged 107,294,569, minus 1,841 (minus 0.0017%)
boundary drops 1,841 · 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-28T11:40:54Z 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,152,686 116,552,727 0-38 83ec3a9ac60c425918a0c99dd1da61341c3bb237624e76ea965ef218dbd45e33 book 699,884 62,753,131 39-41 dee716f79d59df370bcb7dc5e8d55c5e6b82f4bddef10ef68bddd0d575277afd last_trade_price 52,439 2,998,429 42-42 9554a49cc2d09c3f860afd399965edb758fef32e4896b0cc4004269c66d44b8d market_resolved 713 100,333 43-43 364fc2a66d387e02a01c95f555c8e734462980cee70da9248d16ea94ee0a1736 new_market 1,147 108,561 44-44 b46ee89b81e6f5885d0e4ea2fceaa0c1c81387b4bbb57067e6f56827652dfb41 price_change 96,384,640 996,257,168 45-412 1f088b905d42ba14cc9ada33dd1161bd233299437fec8aaede0a34ed74dc27bc tick_size_change 3,060 113,392 413-413 b339fb8fbdab6db5b91504db71397a2e3cdc6faf8bcbc2286244e13589ee46b8 EVENT MIX count share price_change 96,384,640 89.83% best_bid_ask 10,152,686 9.46% book 699,884 0.65% last_trade_price 52,439 0.05% tick_size_change 3,060 <0.01% new_market 1,147 <0.01% market_resolved 713 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,152,853 10,152,686 167 829 FULL book 699,974 699,884 90 198,127 FULL last_trade_price 52,439 52,439 0 178 FULL market_resolved 713 713 0 16 FULL new_market 1,147 1,147 0 0 FULL price_change 96,386,224 96,384,640 1,584 867 FULL tick_size_change 3,060 3,060 0 64 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,673,775 8,700,102 5ms 16ms 116ms 5.4s 0 transport_latency_assumed best_bid_ask g 10,141,983 463 78ms 101ms 558ms 38.5s 0 transport_latency_assumed best_bid_ask h 9,835,984 165,464 18ms 29ms 159ms 54.2s 0 transport_latency_assumed best_bid_ask i 10,111,273 114,981 21ms 29ms 114ms 7.4s 0 transport_latency_assumed best_bid_ask k 10,151,440 1,171,676 13ms 22ms 110ms 39.8s 0 transport_latency_assumed book c 517,637 246,424 1.1h 3.5d 36.9d 121.5d 0 book_staleness book g 113,158 6,252 89ms 9.7s 3.5d 103.0d 0 book_staleness book h 532,320 425,067 47.4min 3.5d 36.9d 121.5d 0 book_staleness book i 120,111 7,954 24ms 1.3min 8.8d 121.4d 0 book_staleness book k 112,509 14,187 16ms 108ms 1.2d 103.0d 0 book_staleness last_trade_price c 49,965 44,334 7ms 26ms 220ms 1.7s 0 transport_latency_assumed last_trade_price g 50,537 2 87ms 943ms 10.9s 31.3s 0 transport_latency_assumed last_trade_price h 50,950 1,108 20ms 73ms 420ms 8.8s 0 transport_latency_assumed last_trade_price i 51,993 645 22ms 89ms 609ms 7.4s 0 transport_latency_assumed last_trade_price k 52,318 6,350 14ms 42ms 280ms 7.3s 0 transport_latency_assumed market_resolved c 657 523 7ms 3.5min 9.5min 9.5min 0 transport_latency_assumed market_resolved g 603 1 80ms 39.2s 48.1s 48.7s 0 transport_latency_assumed market_resolved h 595 9 20ms 40.3s 3.3min 4.4min 0 transport_latency_assumed market_resolved i 603 106 22ms 20.9s 55.6s 1.4min 0 transport_latency_assumed market_resolved k 603 74 14ms 22.8s 31.0s 31.4s 0 transport_latency_assumed new_market c 706 352 139ms 47.0s 5.5min 5.6min 0 transport_latency_assumed new_market g 703 96 348ms 43.1s 1.2min 1.5min 0 transport_latency_assumed new_market h 703 279 176ms 1.0min 1.2min 1.6min 0 transport_latency_assumed new_market i 703 248 132ms 30.3s 45.6s 1.6min 0 transport_latency_assumed new_market k 703 172 186ms 45.7s 1.3min 1.6min 0 transport_latency_assumed price_change c 91,692,508 81,867,855 6ms 19ms 138ms 5.8s 0 transport_latency_assumed price_change g 95,765,351 4,274 78ms 140ms 3.5s 38.5s 0 transport_latency_assumed price_change h 93,416,020 1,746,299 19ms 35ms 241ms 56.5s 0 transport_latency_assumed price_change i 95,847,935 1,234,084 21ms 36ms 251ms 7.4s 0 transport_latency_assumed price_change k 96,316,950 11,532,128 13ms 26ms 143ms 40.8s 0 transport_latency_assumed tick_size_change c 2,936 2,650 6ms 15ms 49ms 108ms 0 transport_latency_assumed tick_size_change g 3,060 not meas. 77ms 92ms 221ms 996ms 0 transport_latency_assumed tick_size_change h 2,928 56 18ms 26ms 70ms 367ms 0 transport_latency_assumed tick_size_change i 3,060 12 21ms 28ms 76ms 162ms 0 transport_latency_assumed tick_size_change k 3,060 342 13ms 21ms 60ms 160ms 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-28/09/2026-09-28T09.parquet sha256sum 2026-09-28T09.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.