Hour audit: 2026-09-19T05
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-19T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T05:00:00.000000122+00:00 · last event 2026-09-19T05:59:59.999972760+00:00
VOLUME 101,270,192 rows · 997,089,061 bytes (950.90 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 101,126,960 · h: 101,044,400 · e: 101,019,968 · f: 101,008,549 · g: 100,943,263 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 97,915,203 (96.69%) · h: 2,879,702 (2.84%) · e: 269,700 (0.27%) · f: 154,165 (0.15%) · g: 51,422 (0.05%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 101,270,192 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8d9f1c075548bf03b0a54f5a97fc51bfe68161fd56afcf01f7681fde43e53291
the corpus checksum ledger names this file with the same digest
joined 101,272,090 to merged 101,270,192, minus 1,898 (minus 0.0019%)
boundary drops 1,898 · 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-19T06:56:32Z as cefgh
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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,976,285 116,781,218 0-41 83b2593d46529771e67cd1cde25462639615ed30cf012dec4b01260303aa1be7 book 255,815 25,483,353 42-42 263f1489ff8af29eff190220d46a1c6d2ad40ad3514b05bebf58cfc3039bbf1d last_trade_price 44,271 2,583,223 43-43 cda1850f3a97e9f778f7dc1421b1d0d1d5253de96fc30b5260aa50c0f493f37d market_resolved 971 157,989 44-44 d8929e5e680132b3dbbf26b1a899f57fbcd33552b1f6a8de46711f180c0b8137 new_market 940 96,597 45-45 4e79642def0996378c3d186497e867fbfebe413254e9165e4fe474f2e6efb5ff price_change 89,989,274 850,735,954 46-389 7de68ffb7122a0d924c3671e98360510b2e619bce60aac4bffc4127d41aacb55 tick_size_change 2,636 97,093 390-390 a9cfcbbef7d454b0cec8686e9a34ab2104d7bad7100090e1e6ea639398d9513b EVENT MIX count share price_change 89,989,274 88.86% best_bid_ask 10,976,285 10.84% book 255,815 0.25% last_trade_price 44,271 0.04% tick_size_change 2,636 <0.01% market_resolved 971 <0.01% new_market 940 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,976,488 10,976,285 203 93 FULL book 255,821 255,815 6 70,943 FULL last_trade_price 44,272 44,271 1 0 FULL market_resolved 971 971 0 0 FULL new_market 940 940 0 0 FULL price_change 89,990,962 89,989,274 1,688 63 FULL tick_size_change 2,636 2,636 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,975,850 10,666,935 4ms 8ms 68ms 5.2s 0 transport_latency_assumed best_bid_ask e 10,974,050 21,557 41ms 46ms 128ms 9.2s 0 transport_latency_assumed best_bid_ask f 10,974,234 9,468 47ms 52ms 143ms 12.1s 0 transport_latency_assumed best_bid_ask g 10,973,921 1,106 78ms 91ms 238ms 28.0s 0 transport_latency_assumed best_bid_ask h 10,974,318 277,219 18ms 23ms 105ms 14.0s 0 transport_latency_assumed book c 141,108 131,669 8ms 13.6h 16.9d 112.3d 0 book_staleness book e 126,879 32,337 45ms 11.3h 11.8d 112.3d 0 book_staleness book f 130,692 34,309 52ms 12.0h 13.6d 112.3d 0 book_staleness book g 133,355 36,014 88ms 12.6h 13.7d 93.8d 0 book_staleness book h 111,275 21,486 21ms 28.8min 8.8d 94.2d 0 book_staleness last_trade_price c 44,158 42,001 9ms 43ms 236ms 5.0s 0 transport_latency_assumed last_trade_price e 44,033 210 48ms 111ms 740ms 9.2s 0 transport_latency_assumed last_trade_price f 44,099 73 54ms 116ms 790ms 12.1s 0 transport_latency_assumed last_trade_price g 43,997 29 86ms 197ms 1.0s 26.7s 0 transport_latency_assumed last_trade_price h 44,005 1,958 23ms 65ms 323ms 5.5s 0 transport_latency_assumed market_resolved c 971 949 4ms 7ms 183ms 55.0s 0 transport_latency_assumed market_resolved e 971 not meas. 44ms 164ms 498ms 45.4s 0 transport_latency_assumed market_resolved f 971 not meas. 52ms 153ms 541ms 49.8s 0 transport_latency_assumed market_resolved g 971 not meas. 88ms 240ms 798ms 1.0min 0 transport_latency_assumed market_resolved h 971 22 20ms 56ms 338ms 45.4s 0 transport_latency_assumed new_market c 633 431 65ms 19.2s 1.6min 1.8min 0 transport_latency_assumed new_market e 633 147 141ms 39.0s 1.6min 1.8min 0 transport_latency_assumed new_market f 633 50 144ms 54.6s 1.7min 1.8min 0 transport_latency_assumed new_market g 633 71 251ms 49.5s 1.6min 1.8min 0 transport_latency_assumed new_market h 633 241 117ms 42.7s 1.5min 1.7min 0 transport_latency_assumed price_change c 89,961,604 87,070,666 4ms 9ms 88ms 5.2s 0 transport_latency_assumed price_change e 89,870,766 215,444 41ms 49ms 220ms 9.3s 0 transport_latency_assumed price_change f 89,855,284 110,254 47ms 56ms 234ms 12.1s 0 transport_latency_assumed price_change g 89,787,750 14,202 78ms 95ms 363ms 28.0s 0 transport_latency_assumed price_change h 89,910,562 2,578,708 18ms 25ms 159ms 17.2s 0 transport_latency_assumed tick_size_change c 2,636 2,552 5ms 8ms 96ms 242ms 0 transport_latency_assumed tick_size_change e 2,636 5 41ms 46ms 180ms 537ms 0 transport_latency_assumed tick_size_change f 2,636 11 47ms 53ms 217ms 445ms 0 transport_latency_assumed tick_size_change g 2,636 not meas. 78ms 93ms 365ms 614ms 0 transport_latency_assumed tick_size_change h 2,636 68 18ms 26ms 135ms 337ms 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-19/05/2026-09-19T05.parquet sha256sum 2026-09-19T05.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.