Hour audit: 2026-09-23T06
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-23T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T06:00:00.000013252+00:00 · last event 2026-09-23T06:59:59.999718946+00:00
VOLUME 116,034,875 rows · 1,229,501,997 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured k: 114,548,617 · i: 114,403,721 · h: 113,814,361 · c: 109,471,833 · f: 109,190,245 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 11,655,163 (10.04%) · i: 1,311,997 (1.13%) · h: 1,574,272 (1.36%) · c: 101,269,471 (87.28%) · f: 223,972 (0.19%) (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 116,034,875 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1c8e68f087b5628fcfef299b0abe6111042d438cc568c2330776311ebe0667c0
the corpus checksum ledger names this file with the same digest
joined 116,036,260 to merged 116,034,875, minus 1,385 (minus 0.0012%)
boundary drops 1,385 · 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-23T09:07:06Z as cfhik
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 11,481,189 131,368,708 0-43 f728584087afb6a9c7e7929cccd5420486eab790c22e3f5f0c879fe49f45a1c8 book 2,134,795 94,300,524 44-52 2b79a8fa00c1b50659beb27d03f3d4ffc888643cef30b9c878c0dcb12feea21b last_trade_price 50,229 2,834,791 53-53 78b8c1b7bc1894d2e45064b06e6fef743b22d00b4f7a7da3c0b2c663ced6bb59 market_resolved 606 87,134 54-54 98ed5a5c0cba3cbacc20f2b3a0d6ea3e6b72895b1291b44d02a00dfe1fda1459 new_market 612 63,418 55-55 348600948cc9da99072e2b89d220b81c67ee7c63367be7948a4430b7ccf9e48d price_change 102,365,588 999,457,206 56-446 8cc8cc0b1db1255e1b142b4bc49fd6b7de368e1abfa696ffda367d60e1284ccc tick_size_change 1,856 68,026 447-447 35e262a9fccbd2a68dcb2e004894429b7a763a5e3bf5d83459a8e3b19971c153 EVENT MIX count share price_change 102,365,588 88.22% best_bid_ask 11,481,189 9.89% book 2,134,795 1.84% last_trade_price 50,229 0.04% tick_size_change 1,856 <0.01% new_market 612 <0.01% market_resolved 606 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,481,299 11,481,189 110 702 FULL book 2,134,817 2,134,795 22 188,022 FULL last_trade_price 50,230 50,229 1 113 FULL market_resolved 606 606 0 6 FULL new_market 612 612 0 0 FULL price_change 102,366,840 102,365,588 1,252 264 FULL tick_size_change 1,856 1,856 0 36 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,977,272 10,236,622 5ms 10ms 77ms 3.2s 0 transport_latency_assumed best_bid_ask f 10,972,218 2,651 48ms 58ms 160ms 8.7s 0 transport_latency_assumed best_bid_ask h 11,476,504 138,010 18ms 26ms 97ms 21.7s 0 transport_latency_assumed best_bid_ask i 11,429,483 72,836 20ms 28ms 95ms 10.1s 0 transport_latency_assumed best_bid_ask k 11,426,641 1,031,070 12ms 18ms 75ms 5.3s 0 transport_latency_assumed book c 487,660 469,287 7.4min 2.5d 38.7d 116.3d 0 book_staleness book f 494,782 157,295 8.0min 2.5d 38.7d 116.3d 0 book_staleness book h 111,196 11,804 22ms 769ms 4.6d 97.9d 0 book_staleness book i 1,073,548 495,990 12.1min 3.7d 42.5d 116.4d 0 book_staleness book k 1,245,987 1,000,419 8.1min 3.7d 42.5d 116.4d 0 book_staleness last_trade_price c 47,370 42,426 6ms 24ms 182ms 1.5s 0 transport_latency_assumed last_trade_price f 47,589 187 50ms 140ms 1.8s 3.6s 0 transport_latency_assumed last_trade_price h 49,706 1,087 19ms 57ms 320ms 4.7s 0 transport_latency_assumed last_trade_price i 49,886 472 23ms 95ms 515ms 1.9s 0 transport_latency_assumed last_trade_price k 49,654 6,057 13ms 33ms 203ms 1.2s 0 transport_latency_assumed market_resolved c 522 488 5ms 14ms 38.0s 5.1min 0 transport_latency_assumed market_resolved f 536 36 52ms 8.5s 5.7min 5.7min 0 transport_latency_assumed market_resolved h 525 8 20ms 147ms 1.0min 1.0min 0 transport_latency_assumed market_resolved i 522 46 28ms 257ms 1.0min 1.0min 0 transport_latency_assumed market_resolved k 525 28 14ms 58ms 1.0min 1.0min 0 transport_latency_assumed new_market c 403 212 68ms 19.5s 5.9min 5.9min 0 transport_latency_assumed new_market f 405 73 141ms 16.5s 4.4min 4.8min 0 transport_latency_assumed new_market h 402 79 77ms 12.4s 29.6s 1.5min 0 transport_latency_assumed new_market i 402 105 76ms 11.8s 27.9s 1.2min 0 transport_latency_assumed new_market k 402 143 59ms 14.9s 31.4s 34.7s 0 transport_latency_assumed price_change c 97,956,838 90,518,774 5ms 13ms 96ms 3.2s 0 transport_latency_assumed price_change f 97,672,895 63,730 48ms 65ms 271ms 8.7s 0 transport_latency_assumed price_change h 102,174,192 1,423,256 18ms 31ms 146ms 21.7s 0 transport_latency_assumed price_change i 101,848,024 742,540 21ms 33ms 166ms 10.6s 0 transport_latency_assumed price_change k 101,823,552 9,617,288 12ms 21ms 104ms 5.3s 0 transport_latency_assumed tick_size_change c 1,768 1,662 5ms 8ms 62ms 178ms 0 transport_latency_assumed tick_size_change f 1,820 not meas. 48ms 57ms 114ms 221ms 0 transport_latency_assumed tick_size_change h 1,836 28 18ms 26ms 82ms 227ms 0 transport_latency_assumed tick_size_change i 1,856 8 21ms 28ms 97ms 211ms 0 transport_latency_assumed tick_size_change k 1,856 158 12ms 18ms 75ms 185ms 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-23/06/2026-09-23T06.parquet sha256sum 2026-09-23T06.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.