Hour audit: 2026-09-07T04
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-07T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T04:00:00.000097643+00:00 · last event 2026-09-07T04:59:59.999685750+00:00
VOLUME 94,550,237 rows · 944,695,123 bytes (900.93 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 94,353,977 · f: 94,290,557 · e: 94,201,184 · g: 94,176,780 · h: 94,117,003 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 90,207,072 (95.41%) · f: 340,187 (0.36%) · e: 715,251 (0.76%) · g: 55,598 (0.06%) · h: 3,232,129 (3.42%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 94,550,237 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fe8b8b9c235c663f3916953cb5e9660e03ef8bfb8bb68896d82ede294cea915a
the corpus checksum ledger names this file with the same digest
joined 94,552,547 to merged 94,550,237, minus 2,310 (minus 0.0024%)
boundary drops 2,310 · 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-07T05:54:55Z 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,531,703 106,052,967 0-36 cf950018d90e177288af64e31a82d41150357b41bd4f1c9053d56ef42f9c010d book 305,218 30,143,212 37-38 b0991e94fb9a71c34728b818bd26fd745a4a3e2a650e698fc30a86dab6c36fcf last_trade_price 53,018 2,917,561 39-39 933f71a33306e3dd2cac3ea76bae2ddc0907071d16e067cbd51c43fe6fc5fd54 market_resolved 1,587 252,320 40-40 a80d183a9d7f46bceaea6b5c99bb3a38b66a257778ebcf778dc04f50d22272eb new_market 4,299 421,971 41-41 3bfb6dadaa438516fb909ebd49f245b91589c1dff3ff1e20f5ac06de2d18b4fc price_change 84,652,752 803,766,724 42-364 d8cb5f4a4a862a3aa2117e11ce8c0956a1309567423a1b2096796705d25fe267 tick_size_change 1,660 60,715 365-365 c9466515a394a40448b8b803442220c8bcd368ba4e871d1d25287f40b50078b8 EVENT MIX count share price_change 84,652,752 89.53% best_bid_ask 9,531,703 10.08% book 305,218 0.32% last_trade_price 53,018 0.06% new_market 4,299 <0.01% tick_size_change 1,660 <0.01% market_resolved 1,587 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,531,928 9,531,703 225 415 FULL book 305,218 305,218 0 80,247 FULL last_trade_price 53,019 53,018 1 0 FULL market_resolved 1,587 1,587 0 2 FULL new_market 4,299 4,299 0 0 FULL price_change 84,654,836 84,652,752 2,084 877 FULL tick_size_change 1,660 1,660 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,529,894 9,112,319 4ms 10ms 219ms 11.7s 0 transport_latency_assumed best_bid_ask e 9,528,374 68,299 39ms 48ms 326ms 23.0s 0 transport_latency_assumed best_bid_ask f 9,528,167 30,226 49ms 61ms 328ms 25.7s 0 transport_latency_assumed best_bid_ask g 9,525,829 2,579 83ms 132ms 790ms 28.2s 0 transport_latency_assumed best_bid_ask h 9,528,994 318,280 18ms 29ms 565ms 1.7min 0 transport_latency_assumed book c 202,689 188,733 30ms 7.2h 26.2d 100.3d 0 book_staleness book e 135,864 18,710 42ms 2.3min 5.2d 92.5d 0 book_staleness book f 176,443 57,566 80ms 4.7h 15.6d 100.3d 0 book_staleness book g 147,199 30,093 95ms 51.3min 15.6d 81.8d 0 book_staleness book h 118,626 10,116 21ms 171ms 4.4h 81.7d 0 book_staleness last_trade_price c 52,964 50,081 9ms 42ms 302ms 5.0s 0 transport_latency_assumed last_trade_price e 52,819 322 45ms 150ms 4.4s 23.0s 0 transport_latency_assumed last_trade_price f 52,805 156 56ms 159ms 2.0s 25.8s 0 transport_latency_assumed last_trade_price g 52,497 11 95ms 278ms 9.2s 26.7s 0 transport_latency_assumed last_trade_price h 52,915 2,448 23ms 64ms 567ms 35.8s 0 transport_latency_assumed market_resolved c 1,574 1,529 4ms 9ms 182ms 1.8s 0 transport_latency_assumed market_resolved e 1,574 17 40ms 160ms 627ms 57.6s 0 transport_latency_assumed market_resolved f 1,574 5 51ms 146ms 455ms 1.0min 0 transport_latency_assumed market_resolved g 1,573 not meas. 87ms 253ms 750ms 2.1s 0 transport_latency_assumed market_resolved h 1,573 36 18ms 62ms 2.3s 57.7s 0 transport_latency_assumed new_market c 2,692 1,545 174ms 37.1s 1.2min 28.2min 0 transport_latency_assumed new_market e 2,692 810 197ms 33.5s 49.6s 57.6min 0 transport_latency_assumed new_market f 2,692 447 253ms 33.9s 46.4s 3.6h 0 transport_latency_assumed new_market g 2,692 635 360ms 36.8s 1.3min 4.5h 0 transport_latency_assumed new_market h 2,692 862 197ms 36.4s 1.3min 4.3h 0 transport_latency_assumed price_change c 84,562,504 80,851,217 5ms 11ms 222ms 11.8s 0 transport_latency_assumed price_change e 84,478,201 627,093 39ms 54ms 382ms 23.2s 0 transport_latency_assumed price_change f 84,527,216 251,787 50ms 67ms 380ms 26.0s 0 transport_latency_assumed price_change g 84,445,330 22,280 84ms 145ms 932ms 28.2s 0 transport_latency_assumed price_change h 84,410,543 2,900,375 18ms 32ms 518ms 1.8min 0 transport_latency_assumed tick_size_change c 1,660 1,648 4ms 6ms 33ms 242ms 0 transport_latency_assumed tick_size_change e 1,660 not meas. 39ms 47ms 166ms 248ms 0 transport_latency_assumed tick_size_change f 1,660 not meas. 49ms 53ms 191ms 302ms 0 transport_latency_assumed tick_size_change g 1,660 not meas. 80ms 99ms 416ms 716ms 0 transport_latency_assumed tick_size_change h 1,660 12 18ms 30ms 511ms 7.8s 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/04/2026-09-07T04.parquet sha256sum 2026-09-07T04.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.