Hour audit: 2026-09-28T11
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-28T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T11:00:00.000001623+00:00 · last event 2026-09-28T11:59:59.999923105+00:00
VOLUME 102,337,528 rows · 1,081,027,587 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 102,269,114 · c: 102,258,536 · k: 102,246,483 · i: 102,223,084 · g: 101,603,502 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,679,244 (1.64%) · c: 91,943,008 (89.84%) · k: 7,841,293 (7.66%) · i: 855,684 (0.84%) · g: 18,299 (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 102,337,528 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ce5eaac15f3e9b6c8163679715d4e5f8664ce486a9c3c29434b678539a288f42
the corpus checksum ledger names this file with the same digest
joined 102,339,826 to merged 102,337,528, minus 2,298 (minus 0.0022%)
boundary drops 2,298 · 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-28T13:39:38Z 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,284,120 107,741,170 0-35 dde2706912718f47d8cd283dfe899c404f26b70d727f3c1da758b2adb3b7db42 book 142,337 14,519,525 36-36 f122c9adebb929a5d89de636cc647cb310822bbf03d133937b83271714ba36cf last_trade_price 57,171 3,222,784 37-37 0efac62365c79b9ec40fa7460e5b6219fae910a2a53845c82f5157b0c12cc871 market_resolved 792 130,541 38-38 ce32fe89f1ed08dc2a7d7f266da69aee77d01aed0a2707db548190c43d76fe85 new_market 1,512 147,968 39-39 52da1277652b3f8b05ab276fd40be15e36e3265c178d44afa97f616a08575b69 price_change 92,848,484 953,982,340 40-394 35de14a52bb3dbbb29bd17700662bdd848d13bfc41362274de5bf1453a2d942c tick_size_change 3,112 114,411 395-395 99bd98331c34f11ce98782c2b93b8243189ccbdf51605b1b510692da20dbe99f EVENT MIX count share price_change 92,848,484 90.73% best_bid_ask 9,284,120 9.07% book 142,337 0.14% last_trade_price 57,171 0.06% tick_size_change 3,112 <0.01% new_market 1,512 <0.01% market_resolved 792 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,284,341 9,284,120 221 125 FULL book 142,355 142,337 18 6,908 FULL last_trade_price 57,174 57,171 3 0 FULL market_resolved 792 792 0 0 FULL new_market 1,512 1,512 0 0 FULL price_change 92,850,540 92,848,484 2,056 302 FULL tick_size_change 3,112 3,112 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,282,928 8,405,456 5ms 14ms 129ms 4.8s 0 transport_latency_assumed best_bid_ask g 9,272,677 777 79ms 108ms 653ms 31.9s 0 transport_latency_assumed best_bid_ask h 9,282,806 139,555 17ms 26ms 181ms 52.6s 0 transport_latency_assumed best_bid_ask i 9,282,548 70,658 20ms 28ms 164ms 20.4s 0 transport_latency_assumed best_bid_ask k 9,282,884 667,674 12ms 20ms 130ms 58.4s 0 transport_latency_assumed book c 122,412 107,877 8ms 72ms 23.0h 103.0d 0 book_staleness book g 118,931 6,623 89ms 7.4s 1.3d 103.0d 0 book_staleness book h 122,645 7,553 22ms 223ms 22.4h 103.0d 0 book_staleness book i 120,495 5,681 23ms 241ms 14.2h 102.9d 0 book_staleness book k 121,653 14,603 15ms 100ms 17.6h 103.0d 0 book_staleness last_trade_price c 56,918 50,493 7ms 24ms 220ms 2.1s 0 transport_latency_assumed last_trade_price g 54,390 7 89ms 1.7s 15.7s 31.8s 0 transport_latency_assumed last_trade_price h 56,977 988 18ms 81ms 549ms 26.4s 0 transport_latency_assumed last_trade_price i 56,908 499 22ms 117ms 689ms 3.0s 0 transport_latency_assumed last_trade_price k 57,003 5,184 13ms 42ms 281ms 2.9s 0 transport_latency_assumed market_resolved c 778 655 6ms 76ms 41.9s 45.3s 0 transport_latency_assumed market_resolved g 778 not meas. 82ms 416ms 43.2s 47.5s 0 transport_latency_assumed market_resolved h 778 9 18ms 101ms 40.4s 44.7s 0 transport_latency_assumed market_resolved i 778 82 22ms 365ms 42.4s 51.8s 0 transport_latency_assumed market_resolved k 778 46 13ms 182ms 52.0s 56.1s 0 transport_latency_assumed new_market c 936 439 188ms 27.4s 42.2s 1.4min 0 transport_latency_assumed new_market g 936 74 367ms 25.8s 42.0s 55.9s 0 transport_latency_assumed new_market h 936 402 181ms 33.8s 53.8s 1.6min 0 transport_latency_assumed new_market i 936 211 181ms 25.2s 41.6s 1.8min 0 transport_latency_assumed new_market k 936 386 185ms 24.5s 45.3s 58.8s 0 transport_latency_assumed price_change c 92,791,452 83,375,328 6ms 16ms 150ms 7.8s 0 transport_latency_assumed price_change g 92,152,678 10,818 80ms 176ms 5.2s 31.9s 0 transport_latency_assumed price_change h 92,801,860 1,530,680 17ms 34ms 273ms 53.2s 0 transport_latency_assumed price_change i 92,758,307 778,516 20ms 38ms 319ms 20.4s 0 transport_latency_assumed price_change k 92,780,117 7,153,142 12ms 24ms 162ms 58.9s 0 transport_latency_assumed tick_size_change c 3,112 2,760 6ms 16ms 80ms 175ms 0 transport_latency_assumed tick_size_change g 3,112 not meas. 79ms 97ms 201ms 739ms 0 transport_latency_assumed tick_size_change h 3,112 57 17ms 27ms 136ms 308ms 0 transport_latency_assumed tick_size_change i 3,112 37 20ms 32ms 92ms 318ms 0 transport_latency_assumed tick_size_change k 3,112 258 12ms 21ms 91ms 535ms 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/11/2026-09-28T11.parquet sha256sum 2026-09-28T11.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.