Hour audit: 2026-09-07T14
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-07T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T14:00:00.000017317+00:00 · last event 2026-09-07T14:59:59.999583341+00:00
VOLUME 99,551,963 rows · 1,059,184,610 bytes (1010.12 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 98,949,859 · h: 98,830,816 · e: 98,779,673 · f: 98,700,549 · c: 94,755,503 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 260,971 (0.26%) · h: 8,421,922 (8.46%) · e: 667,830 (0.67%) · f: 362,340 (0.36%) · c: 89,838,900 (90.24%) (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 99,551,963 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7b72fbb0aa4a5a5db59ff6baf768a24a2a4ac8a210915b74ca422df99593a08c
the corpus checksum ledger names this file with the same digest
joined 99,555,545 to merged 99,551,963, minus 3,582 (minus 0.0036%)
boundary drops 3,582 · 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-07T15:56: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 10,428,214 113,386,805 0-39 221bb29035e0bc5f60954d301788cec02cf70396d8b7cff67f7d0d66ab99aabb book 961,397 75,163,139 40-43 20f7c6b23c0b6f5a64b5b498a33e0d1ff32fca613299c8f35656fb0eb67fe45e last_trade_price 68,796 3,766,389 44-44 4c7be7dd8e613ef4f04eeb21ee010d83a670d2443aea99d03224863aca56a443 market_resolved 986 161,604 45-45 c5cdd1da4a1ae5ec819322dcd4fa0caaf5597a09865dc2117387a86d407a8d93 new_market 3,050 295,942 46-46 6c2e4f9b5ee75bbc0cd88bca05b3e222167762197a5fc65c031019bad9688506 price_change 88,086,128 865,151,771 47-383 02cccb011dbf8a5fdfd4e532330e50e80c45415384ec1f341456288828563aef tick_size_change 3,392 123,593 384-384 fd2f7ce1c2e4a78ab92d26d5c98cc50d97159abcd8761836db890dbf348509ab EVENT MIX count share price_change 88,086,128 88.48% best_bid_ask 10,428,214 10.48% book 961,397 0.97% last_trade_price 68,796 0.07% tick_size_change 3,392 <0.01% new_market 3,050 <0.01% market_resolved 986 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,428,432 10,428,214 218 1,035 FULL book 962,401 961,397 1,004 164,954 FULL last_trade_price 68,796 68,796 0 60 FULL market_resolved 986 986 0 36 FULL new_market 3,050 3,050 0 68 FULL price_change 88,088,488 88,086,128 2,360 747 FULL tick_size_change 3,392 3,392 0 25 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,993,380 9,509,794 5ms 11ms 168ms 5.0s 0 transport_latency_assumed best_bid_ask e 10,423,982 60,176 38ms 46ms 265ms 24.3s 0 transport_latency_assumed best_bid_ask f 10,423,535 27,063 44ms 56ms 287ms 23.7s 0 transport_latency_assumed best_bid_ask g 10,417,985 2,297 82ms 112ms 694ms 32.2s 0 transport_latency_assumed best_bid_ask h 10,425,354 828,884 17ms 25ms 270ms 50.9s 0 transport_latency_assumed book c 578,195 450,755 3.4min 6.8h 30.0d 100.7d 0 book_staleness book e 300,717 91,204 4.8s 4.3h 17.8d 100.7d 0 book_staleness book f 305,653 91,491 6.4s 4.4h 22.8d 100.7d 0 book_staleness book g 547,250 236,636 3.7min 6.3h 29.9d 100.7d 0 book_staleness book h 296,960 91,311 2.9s 4.4h 19.5d 100.7d 0 book_staleness last_trade_price c 66,280 61,794 10ms 47ms 283ms 5.0s 0 transport_latency_assumed last_trade_price e 68,553 421 44ms 212ms 3.6s 24.4s 0 transport_latency_assumed last_trade_price f 68,576 262 51ms 207ms 3.6s 23.9s 0 transport_latency_assumed last_trade_price g 68,083 26 102ms 963ms 12.2s 32.3s 0 transport_latency_assumed last_trade_price h 68,731 6,293 23ms 75ms 523ms 16.9s 0 transport_latency_assumed market_resolved c 950 920 5ms 11ms 93ms 358ms 0 transport_latency_assumed market_resolved e 986 6 38ms 125ms 620ms 941ms 0 transport_latency_assumed market_resolved f 986 1 45ms 138ms 584ms 876ms 0 transport_latency_assumed market_resolved g 986 1 87ms 279ms 922ms 1.5s 0 transport_latency_assumed market_resolved h 986 58 18ms 63ms 215ms 632ms 0 transport_latency_assumed new_market c 1,825 1,155 121ms 1.0min 3.8min 3.8min 0 transport_latency_assumed new_market e 1,893 557 193ms 40.5s 1.4min 5.2min 0 transport_latency_assumed new_market f 1,893 333 207ms 41.4s 1.2min 2.1min 0 transport_latency_assumed new_market g 1,893 175 304ms 39.4s 1.5min 2.1min 0 transport_latency_assumed new_market h 1,893 830 145ms 41.2s 1.6min 2.1min 0 transport_latency_assumed price_change c 84,111,581 79,811,275 5ms 13ms 189ms 5.7s 0 transport_latency_assumed price_change e 87,980,150 515,462 38ms 57ms 392ms 24.4s 0 transport_latency_assumed price_change f 87,896,514 243,182 45ms 66ms 411ms 23.8s 0 transport_latency_assumed price_change g 87,910,270 21,836 84ms 150ms 1.7s 32.4s 0 transport_latency_assumed price_change h 88,033,500 7,494,373 17ms 29ms 285ms 51.0s 0 transport_latency_assumed tick_size_change c 3,292 3,207 5ms 9ms 33ms 162ms 0 transport_latency_assumed tick_size_change e 3,392 4 38ms 42ms 112ms 536ms 0 transport_latency_assumed tick_size_change f 3,392 8 44ms 48ms 109ms 243ms 0 transport_latency_assumed tick_size_change g 3,392 not meas. 83ms 98ms 239ms 416ms 0 transport_latency_assumed tick_size_change h 3,392 173 17ms 22ms 64ms 758ms 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/14/2026-09-07T14.parquet sha256sum 2026-09-07T14.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.