Hour audit: 2026-09-07T23
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-07T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T23:00:00.000161244+00:00 · last event 2026-09-07T23:59:59.999976530+00:00
VOLUME 90,848,017 rows · 899,200,889 bytes (857.54 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 90,823,132 · h: 90,821,757 · f: 90,790,771 · e: 90,788,044 · g: 90,768,745 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 85,103,292 (93.68%) · h: 5,383,982 (5.93%) · f: 107,408 (0.12%) · e: 239,140 (0.26%) · g: 14,195 (0.02%) (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 90,848,017 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 23f8d700815828fdf2a1a8c13577d45b9b36c83dda77dbc412e74b0dd4b98cb3
the corpus checksum ledger names this file with the same digest
joined 90,850,849 to merged 90,848,017, minus 2,832 (minus 0.0031%)
boundary drops 2,832 · 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-08T00:54:06Z 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,996,822 106,431,353 0-38 e6a7665b5dee17a841f6134cc42c7e72c085a83ca120b12906dfb0b23be0b5c2 book 128,500 12,722,418 39-39 5821ace0576580e3dec65a73f25178a6911b9dd30b8995cab26ec4d3516b3bea last_trade_price 53,263 2,993,292 40-40 5e8a4424e9f367aeab7641a19c8431d8776108eac5822c96671cf404b475d77f market_resolved 1,165 191,785 41-41 fd7c634202d6f2776412c524a5ed552b8072822a160da066827f3db60c22e539 new_market 1,787 172,212 42-42 faa400143e4fcbe5e9ad2ad1a8be0507b660e771dd126bb177c23ed39b112ea4 price_change 80,664,208 775,567,556 43-350 ede37332231755731f776cb180cfff2a9a108a2e75c5f55a935a8cd4d03e362d tick_size_change 2,272 83,849 351-351 05e892f4b56d9b916f1e46d5a989e671ed1bc26d8bfb58030eb5d571e7ac5d73 EVENT MIX count share price_change 80,664,208 88.79% best_bid_ask 9,996,822 11.00% book 128,500 0.14% last_trade_price 53,263 0.06% tick_size_change 2,272 <0.01% new_market 1,787 <0.01% market_resolved 1,165 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,997,040 9,996,822 218 272 FULL book 128,500 128,500 0 7,601 FULL last_trade_price 53,263 53,263 0 0 FULL market_resolved 1,165 1,165 0 0 FULL new_market 1,787 1,787 0 0 FULL price_change 80,666,822 80,664,208 2,614 166 FULL tick_size_change 2,272 2,272 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,996,104 9,398,266 5ms 9ms 99ms 3.9s 0 transport_latency_assumed best_bid_ask e 9,994,220 24,071 38ms 43ms 152ms 7.9s 0 transport_latency_assumed best_bid_ask f 9,994,320 10,865 45ms 52ms 170ms 5.7s 0 transport_latency_assumed best_bid_ask g 9,993,336 628 83ms 102ms 366ms 17.0s 0 transport_latency_assumed best_bid_ask h 9,995,784 562,992 11ms 15ms 114ms 51.4s 0 transport_latency_assumed book c 112,726 103,159 7ms 28ms 7.3min 82.5d 0 book_staleness book e 112,188 2,485 40ms 154ms 2.6min 82.4d 0 book_staleness book f 111,712 1,617 48ms 141ms 3.2s 101.1d 0 book_staleness book g 119,856 9,589 92ms 1.1s 13.1h 82.5d 0 book_staleness book h 113,838 11,650 15ms 52ms 2.6h 82.5d 0 book_staleness last_trade_price c 53,241 49,025 10ms 40ms 205ms 5.0s 0 transport_latency_assumed last_trade_price e 53,095 160 45ms 124ms 823ms 7.9s 0 transport_latency_assumed last_trade_price f 53,196 68 52ms 125ms 974ms 5.7s 0 transport_latency_assumed last_trade_price g 53,098 2 99ms 260ms 1.9s 17.0s 0 transport_latency_assumed last_trade_price h 53,184 4,008 16ms 50ms 462ms 51.4s 0 transport_latency_assumed market_resolved c 1,163 1,129 5ms 8ms 149ms 444ms 0 transport_latency_assumed market_resolved e 1,163 4 40ms 122ms 510ms 59.9s 0 transport_latency_assumed market_resolved f 1,163 1 47ms 148ms 622ms 59.9s 0 transport_latency_assumed market_resolved g 1,163 not meas. 86ms 322ms 921ms 1.5s 0 transport_latency_assumed market_resolved h 1,163 31 12ms 35ms 247ms 4.7s 0 transport_latency_assumed new_market c 1,098 508 115ms 24.5s 41.5s 46.8s 0 transport_latency_assumed new_market e 1,098 338 149ms 26.4s 41.2s 20.7min 0 transport_latency_assumed new_market f 1,098 221 204ms 25.2s 44.2s 6.6min 0 transport_latency_assumed new_market g 1,098 140 314ms 25.9s 41.4s 17.8min 0 transport_latency_assumed new_market h 1,098 580 120ms 25.2s 40.5s 29.7min 0 transport_latency_assumed price_change c 80,656,528 75,549,076 5ms 11ms 121ms 10.5s 0 transport_latency_assumed price_change e 80,624,008 212,082 39ms 48ms 263ms 7.9s 0 transport_latency_assumed price_change f 80,627,010 94,632 46ms 57ms 271ms 5.8s 0 transport_latency_assumed price_change g 80,597,922 3,836 84ms 113ms 576ms 17.1s 0 transport_latency_assumed price_change h 80,654,418 4,804,582 11ms 17ms 152ms 1.0min 0 transport_latency_assumed tick_size_change c 2,272 2,129 5ms 9ms 253ms 381ms 0 transport_latency_assumed tick_size_change e 2,272 not meas. 38ms 43ms 131ms 1.1s 0 transport_latency_assumed tick_size_change f 2,272 4 46ms 52ms 189ms 1.4s 0 transport_latency_assumed tick_size_change g 2,272 not meas. 83ms 100ms 417ms 6.9s 0 transport_latency_assumed tick_size_change h 2,272 139 12ms 15ms 62ms 94ms 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-07/23/2026-09-07T23.parquet sha256sum 2026-09-07T23.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.