Hour audit: 2026-09-18T09
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-18T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T09:00:00.000019654+00:00 · last event 2026-09-18T09:59:59.999966045+00:00
VOLUME 110,268,216 rows · 1,175,684,786 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 109,553,434 · h: 109,454,127 · g: 109,382,646 · e: 109,273,985 · f: 105,063,353 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 103,767,423 (94.10%) · h: 4,957,998 (4.50%) · g: 199,559 (0.18%) · e: 581,919 (0.53%) · f: 761,317 (0.69%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 110,268,216 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fcf903212618b9f14cc2cfc797194d2421f6e7de10bb2d74450be82064277ccf
the corpus checksum ledger names this file with the same digest
joined 110,270,902 to merged 110,268,216, minus 2,686 (minus 0.0024%)
boundary drops 2,686 · 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-18T11:00:05Z 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 9,620,770 112,713,382 0-36 f7709f2c82ff7750cea73819735919ef7a4e561f4bd0242e32f03737d64ba668 book 817,555 68,039,705 37-40 87fc47bf3f7ae85334a48a733521217a6cfd5480b2c203c4a76de6f56f077a5c last_trade_price 59,298 3,460,247 41-41 532491dd369b3856dfaa0e99faccfdab149d4f38c21e6285049d6deffe1189e4 market_resolved 518 81,027 42-42 7fbda63007c46af3d59bbd2ddf34f24c4a4948d15101e4ef8f02ce901ec67829 new_market 2,090 207,292 43-43 82a2c44ca0110ae75d76a0c71372f11dfb11e3c4a617af6ece2a06809b974d6a price_change 99,765,253 989,825,627 44-424 10cc2d761eeb2a35650580acc70fe58fb221c523f127ed7618c774d2f9cb40d7 tick_size_change 2,732 100,447 425-425 04864599ce2abd6cccf5602e97ceb984baa450b8ded09e84a0cfb632c85e75a3 EVENT MIX count share price_change 99,765,253 90.48% best_bid_ask 9,620,770 8.72% book 817,555 0.74% last_trade_price 59,298 0.05% tick_size_change 2,732 <0.01% new_market 2,090 <0.01% market_resolved 518 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,620,972 9,620,770 202 904 FULL book 817,593 817,555 38 190,345 FULL last_trade_price 59,300 59,298 2 198 FULL market_resolved 518 518 0 0 FULL new_market 2,090 2,090 0 0 FULL price_change 99,767,697 99,765,253 2,444 562 FULL tick_size_change 2,732 2,732 0 18 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,615,232 9,134,521 5ms 13ms 135ms 13.4s 0 transport_latency_assumed best_bid_ask e 9,611,842 43,264 41ms 51ms 223ms 16.2s 0 transport_latency_assumed best_bid_ask f 9,168,324 19,904 47ms 60ms 248ms 13.8s 0 transport_latency_assumed best_bid_ask g 9,599,613 3,771 78ms 99ms 375ms 34.2s 0 transport_latency_assumed best_bid_ask h 9,615,839 419,310 18ms 29ms 204ms 8.6s 0 transport_latency_assumed book c 175,522 166,708 9ms 15.4min 12.8d 111.4d 0 book_staleness book e 130,186 7,423 44ms 708ms 34.7min 92.9d 0 book_staleness book f 645,156 485,900 3.3min 7.7h 36.3d 111.5d 0 book_staleness book g 322,681 145,677 36.9s 3.4h 26.8d 111.5d 0 book_staleness book h 130,862 11,847 22ms 228ms 52.2min 92.9d 0 book_staleness last_trade_price c 59,076 55,693 11ms 51ms 288ms 12.9s 0 transport_latency_assumed last_trade_price e 58,452 535 50ms 205ms 6.3s 15.9s 0 transport_latency_assumed last_trade_price f 55,467 320 57ms 215ms 5.9s 11.0s 0 transport_latency_assumed last_trade_price g 58,564 106 92ms 354ms 9.0s 34.2s 0 transport_latency_assumed last_trade_price h 58,815 2,644 25ms 116ms 621ms 8.3s 0 transport_latency_assumed market_resolved c 494 468 5ms 15ms 130ms 9.5s 0 transport_latency_assumed market_resolved e 494 11 43ms 195ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 494 18 49ms 290ms 4.2min 5.2min 0 transport_latency_assumed market_resolved g 494 not meas. 81ms 331ms 888ms 1.4s 0 transport_latency_assumed market_resolved h 494 21 19ms 87ms 1.0min 1.0min 0 transport_latency_assumed new_market c 1,345 974 85ms 18.3s 29.6s 39.9s 0 transport_latency_assumed new_market e 1,345 264 174ms 17.4s 30.5s 44.4s 0 transport_latency_assumed new_market f 1,353 252 192ms 20.0s 38.0s 5.5min 0 transport_latency_assumed new_market g 1,345 159 281ms 18.6s 27.4s 1.0min 0 transport_latency_assumed new_market h 1,345 441 144ms 18.7s 27.5s 31.1s 0 transport_latency_assumed price_change c 99,699,033 94,406,462 5ms 15ms 156ms 13.6s 0 transport_latency_assumed price_change e 99,468,934 530,414 42ms 62ms 537ms 16.2s 0 transport_latency_assumed price_change f 95,189,895 254,923 48ms 72ms 454ms 13.9s 0 transport_latency_assumed price_change g 99,397,221 49,846 79ms 115ms 1.2s 34.3s 0 transport_latency_assumed price_change h 99,644,040 4,523,608 18ms 36ms 289ms 9.5s 0 transport_latency_assumed tick_size_change c 2,732 2,597 5ms 11ms 187ms 1.4s 0 transport_latency_assumed tick_size_change e 2,732 8 42ms 53ms 177ms 722ms 0 transport_latency_assumed tick_size_change f 2,664 not meas. 47ms 56ms 174ms 405ms 0 transport_latency_assumed tick_size_change g 2,728 not meas. 78ms 98ms 370ms 943ms 0 transport_latency_assumed tick_size_change h 2,732 127 18ms 30ms 66ms 152ms 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-18/09/2026-09-18T09.parquet sha256sum 2026-09-18T09.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.