Hour audit: 2026-09-02T11
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-02T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T11:00:00.035153278+00:00 · last event 2026-09-02T11:59:59.999925838+00:00
VOLUME 106,668,267 rows · 1,143,387,697 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 105,730,771 · h: 105,688,071 · e: 105,508,553 · b: 63,580,563 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 240,401 (0.23%) · h: 519,581 (0.49%) · e: 105,507,173 (98.91%) · b: 401,112 (0.38%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 106,668,267 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 51d05cec56c7634acb2834d4cc3a927adbb4d2a10353eb1d2b38fb956bb07b36
the corpus checksum ledger names this file with the same digest
joined 106,670,116 to merged 106,668,267, minus 1,849 (minus 0.0017%)
boundary drops 1,849 · 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-02T13:30:54Z as bceh
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,335,737 105,225,244 0-35 ab098b9a5227dd3d0eec5334880358327bcfd47afcfff2af148451f94dc72b6f book 1,293,311 82,571,936 36-40 26c1276dd8a8e4e99879ee09fd04b56b95c527a386545074c5280eaccb0bb02f last_trade_price 71,950 3,975,726 41-41 0295c8c129b8126fdfc18372929462e96495e769816a3c310836c7caa3c7594c market_resolved 80,255 12,165,389 42-42 681ba7ca471b3ecd15bd8689b9a8445da49f0346a5c67056cfa2659365b4b3ea new_market 80,220 11,342,214 43-43 7bd73dbca02165470a8f5c7f898063629f672d0dd2bf371ac4a4f8ff6e1d39e2 price_change 95,802,330 926,736,965 44-409 29879bcd902ebe95c5ff8a8e0f949647fef9f1518cf1324eda7b917e8430b6ce tick_size_change 4,464 157,341 410-410 c82c02da858229d3e1df3bd08346f4f4d06f0555e51cf68206cc5d8a431a65a5 EVENT MIX count share price_change 95,802,330 89.81% best_bid_ask 9,335,737 8.75% book 1,293,311 1.21% market_resolved 80,255 0.08% new_market 80,220 0.08% last_trade_price 71,950 0.07% tick_size_change 4,464 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,335,827 9,335,737 90 9,507 FULL book 1,294,195 1,293,311 884 82,129 FULL last_trade_price 71,950 71,950 0 979 FULL market_resolved 80,255 80,255 0 79,586 FULL new_market 80,223 80,220 3 77,918 FULL price_change 95,803,202 95,802,330 872 4,796 FULL tick_size_change 4,464 4,464 0 381 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 5,509,197 110 53ms 86ms 2.5s 24.0s 0 transport_latency_assumed best_bid_ask c 9,332,805 1,381 5ms 9ms 125ms 2.6s 0 transport_latency_assumed best_bid_ask e 9,323,592 9,323,504 43ms 83ms 749ms 24.1s 0 transport_latency_assumed best_bid_ask h 9,331,114 10,742 18ms 28ms 252ms 10.6s 0 transport_latency_assumed book b 520,453 243,340 2.0min 11.8h 31.0d 95.6d 0 book_staleness book c 542,051 233,356 1.1min 5.4h 28.8d 95.6d 0 book_staleness book e 558,971 558,549 1.2min 6.1h 30.8d 95.6d 0 book_staleness book h 521,702 258,066 1.0min 5.2h 27.8d 95.6d 0 book_staleness last_trade_price b 36,779 1 87ms 3.9s 12.8s 23.8s 0 transport_latency_assumed last_trade_price c 71,859 9 10ms 41ms 197ms 5.0s 0 transport_latency_assumed last_trade_price e 70,509 70,509 64ms 2.5s 13.2s 23.7s 0 transport_latency_assumed last_trade_price h 71,791 1,431 26ms 211ms 1.0s 8.3s 0 transport_latency_assumed market_resolved b 79,816 79,222 3.2d 4.2d 4.5d 4.5d 0 transport_latency_assumed market_resolved c 1,032 not meas. 5ms 14ms 56.0s 58.3s 0 transport_latency_assumed market_resolved e 1,033 1,033 44ms 211ms 53.7s 55.8s 0 transport_latency_assumed market_resolved h 1,032 not meas. 18ms 106ms 55.5s 57.8s 0 transport_latency_assumed new_market b 79,282 78,273 1.8d 3.7d 4.3d 242.7d 0 transport_latency_assumed new_market c 1,364 153 68ms 16.1s 25.5s 2.4min 0 transport_latency_assumed new_market e 1,364 1,364 135ms 15.2s 29.0s 1.1min 0 transport_latency_assumed new_market h 1,364 430 161ms 15.3s 30.8s 1.7min 0 transport_latency_assumed price_change b 57,352,096 166 54ms 122ms 5.4s 24.1s 0 transport_latency_assumed price_change c 95,777,196 5,502 5ms 9ms 152ms 4.4s 0 transport_latency_assumed price_change e 95,548,620 95,547,750 44ms 122ms 3.0s 24.1s 0 transport_latency_assumed price_change h 95,756,604 248,912 18ms 33ms 321ms 31.2s 0 transport_latency_assumed tick_size_change b 2,940 not meas. 54ms 124ms 5.8s 8.4s 0 transport_latency_assumed tick_size_change c 4,464 not meas. 5ms 11ms 286ms 683ms 0 transport_latency_assumed tick_size_change e 4,464 4,464 44ms 115ms 643ms 1.9s 0 transport_latency_assumed tick_size_change h 4,464 not meas. 18ms 36ms 523ms 845ms 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-02/11/2026-09-02T11.parquet sha256sum 2026-09-02T11.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.