Hour audit: 2026-09-07T01
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-07T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T01:00:00.000033564+00:00 · last event 2026-09-07T01:59:59.999974969+00:00
VOLUME 106,880,108 rows · 1,053,161,071 bytes (1004.37 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 106,860,282 · f: 106,848,822 · g: 106,822,548 · h: 106,658,010 · e: 106,656,228 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 103,660,767 (96.99%) · f: 108,440 (0.10%) · g: 22,497 (0.02%) · h: 2,777,163 (2.60%) · e: 311,241 (0.29%) (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 106,880,108 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 94001632ea9b5469d83395b6c31d41cfca9b627f12f68260c3a6c4e50f36018b
the corpus checksum ledger names this file with the same digest
joined 106,882,225 to merged 106,880,108, minus 2,117 (minus 0.0020%)
boundary drops 2,117 · 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-07T04:00:30Z 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 11,775,661 125,829,959 0-44 a913245d988946288190c6f7cec19f37aa172d241603b64bf3e6916b44d3814c book 124,182 12,120,168 45-45 bcedea7d35caeafeff3a3042f5babfa44d8a94013d4de07e0f69f4aecb4b2c55 last_trade_price 51,581 2,882,409 46-46 61cc7182bb2186d44c2b958ed678a4b941461bd6adbf128ee5b8d18cd281e7cb market_resolved 1,662 260,470 47-47 569dc933f0eff0fadf9c05e9dc57912bd0295d81febf8d69cec0bc92fac775b6 new_market 1,168 125,917 48-48 e079457e07efaa56de79c04f40649cde56b5a1ea167642624b499a8d5083d5e2 price_change 94,922,882 910,615,844 49-411 7daf50f3a1cadab73773fdab788beb77da63ca1d82a32a02dcc417e83c2f7821 tick_size_change 2,972 108,556 412-412 f69545e24c54cc24bd6ca53c795dfa0a394892abbba6a763cf2222fe4b0b0513 EVENT MIX count share price_change 94,922,882 88.81% best_bid_ask 11,775,661 11.02% book 124,182 0.12% last_trade_price 51,581 0.05% tick_size_change 2,972 <0.01% market_resolved 1,662 <0.01% new_market 1,168 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,775,898 11,775,661 237 221 FULL book 124,190 124,182 8 6,674 FULL last_trade_price 51,583 51,581 2 0 FULL market_resolved 1,662 1,662 0 0 FULL new_market 1,168 1,168 0 0 FULL price_change 94,924,752 94,922,882 1,870 682 FULL tick_size_change 2,972 2,972 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,775,159 11,443,832 4ms 8ms 83ms 3.7s 0 transport_latency_assumed best_bid_ask e 11,774,344 31,655 41ms 46ms 135ms 2.6s 0 transport_latency_assumed best_bid_ask f 11,774,046 10,646 48ms 54ms 155ms 2.3s 0 transport_latency_assumed best_bid_ask g 11,773,213 1,416 81ms 98ms 284ms 9.3s 0 transport_latency_assumed best_bid_ask h 11,772,409 288,112 17ms 26ms 134ms 43.4s 0 transport_latency_assumed book c 110,032 104,584 6ms 29ms 1.8h 81.6d 0 book_staleness book e 107,106 1,216 43ms 88ms 1.1s 13.0s 0 book_staleness book f 107,474 1,159 50ms 116ms 2.2s 81.6d 0 book_staleness book g 115,895 9,242 90ms 672ms 15.7h 81.6d 0 book_staleness book h 109,841 7,981 21ms 75ms 1.1h 81.6d 0 book_staleness last_trade_price c 51,530 49,339 10ms 40ms 258ms 5.0s 0 transport_latency_assumed last_trade_price e 51,552 311 47ms 89ms 541ms 5.0s 0 transport_latency_assumed last_trade_price f 51,499 91 54ms 105ms 742ms 5.0s 0 transport_latency_assumed last_trade_price g 51,485 13 94ms 180ms 1.8s 6.2s 0 transport_latency_assumed last_trade_price h 51,217 1,827 23ms 65ms 365ms 8.5s 0 transport_latency_assumed market_resolved c 1,644 1,609 4ms 10ms 72ms 1.0min 0 transport_latency_assumed market_resolved e 1,644 24 44ms 128ms 40.5s 53.9s 0 transport_latency_assumed market_resolved f 1,644 3 51ms 136ms 721ms 55.3s 0 transport_latency_assumed market_resolved g 1,644 1 90ms 252ms 1.4s 1.7min 0 transport_latency_assumed market_resolved h 1,644 25 21ms 67ms 44.7s 58.2s 0 transport_latency_assumed new_market c 811 542 81ms 14.9s 33.0s 3.8h 0 transport_latency_assumed new_market e 811 144 162ms 13.2s 29.8s 42.5s 0 transport_latency_assumed new_market f 811 153 182ms 13.0s 26.2s 3.6h 0 transport_latency_assumed new_market g 811 70 267ms 14.5s 31.1s 2.5h 0 transport_latency_assumed new_market h 811 259 147ms 17.6s 32.5s 3.8h 0 transport_latency_assumed price_change c 94,918,134 92,058,028 5ms 9ms 102ms 3.9s 0 transport_latency_assumed price_change e 94,717,799 277,871 42ms 49ms 175ms 2.6s 0 transport_latency_assumed price_change f 94,910,376 96,379 49ms 57ms 192ms 2.3s 0 transport_latency_assumed price_change g 94,876,528 11,755 82ms 100ms 343ms 9.9s 0 transport_latency_assumed price_change h 94,719,116 2,478,849 18ms 29ms 162ms 43.6s 0 transport_latency_assumed tick_size_change c 2,972 2,833 5ms 11ms 116ms 385ms 0 transport_latency_assumed tick_size_change e 2,972 20 42ms 51ms 154ms 226ms 0 transport_latency_assumed tick_size_change f 2,972 9 49ms 65ms 208ms 407ms 0 transport_latency_assumed tick_size_change g 2,972 not meas. 82ms 106ms 328ms 414ms 0 transport_latency_assumed tick_size_change h 2,972 110 18ms 33ms 317ms 2.4s 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/01/2026-09-07T01.parquet sha256sum 2026-09-07T01.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.