Hour audit: 2026-09-15T12
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-15T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T12:00:00.000590892+00:00 · last event 2026-09-15T12:59:59.999605760+00:00
VOLUME 100,398,282 rows · 1,032,758,747 bytes (984.92 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 100,359,586 · e: 100,319,198 · h: 100,288,553 · f: 100,257,050 · g: 100,186,267 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 95,747,008 (95.37%) · e: 397,024 (0.40%) · h: 4,056,487 (4.04%) · f: 161,631 (0.16%) · g: 36,132 (0.04%) (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 100,398,282 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 79ed9bba9e9d46c78f543ece03dbdf2a3a7d25f67710154da3a2c2eaa57d76c4
the corpus checksum ledger names this file with the same digest
joined 100,399,984 to merged 100,398,282, minus 1,702 (minus 0.0017%)
boundary drops 1,702 · 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-15T13:57:45Z 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,659,550 119,138,464 0-40 49d34bc745ea41a97047f11525b39a47e293afd78293f3f77848b5f73edbee4b book 147,055 16,165,199 41-41 f28e0bc4a821333e30dce6b965208079241cc830f727f3288a6abad2e88ad827 last_trade_price 57,565 3,296,005 42-42 132a4ea1ee8dbbe70a07896a0317b1ab0b9da728d72a47d4e8838905c3db02ad market_resolved 699 110,826 43-43 1ccc9929e9bb838a9cba2ca80064102fa490e388523e97f48f53369a0dc690db new_market 793 85,602 44-44 5b86dd634e6ad19d57dbe8bcacc0ca2743b0e373baaf17b2190b801efc560b6c price_change 89,529,088 892,691,203 45-386 6fa11f205b8c163090e0bc7774699f59ce0f5f19bc581599fcef3a167e73320f tick_size_change 3,532 126,899 387-387 6581b7bb9991f48ab1e72cded57835f7762159fd7ab70c9fc1235e98afcd832a EVENT MIX count share price_change 89,529,088 89.17% best_bid_ask 10,659,550 10.62% book 147,055 0.15% last_trade_price 57,565 0.06% tick_size_change 3,532 <0.01% new_market 793 <0.01% market_resolved 699 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,659,774 10,659,550 224 122 FULL book 147,057 147,055 2 10,033 FULL last_trade_price 57,565 57,565 0 0 FULL market_resolved 699 699 0 0 FULL new_market 793 793 0 0 FULL price_change 89,530,564 89,529,088 1,476 155 FULL tick_size_change 3,532 3,532 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,659,196 10,211,827 6ms 12ms 78ms 3.1s 0 transport_latency_assumed best_bid_ask e 10,657,266 32,345 38ms 46ms 169ms 6.8s 0 transport_latency_assumed best_bid_ask f 10,656,215 11,033 45ms 54ms 180ms 8.9s 0 transport_latency_assumed best_bid_ask g 10,653,932 1,207 80ms 101ms 351ms 24.6s 0 transport_latency_assumed best_bid_ask h 10,657,705 403,138 18ms 25ms 112ms 7.3s 0 transport_latency_assumed book c 120,576 113,851 7ms 24ms 2.3s 90.0d 0 book_staleness book e 123,040 4,623 40ms 247ms 43.7min 90.1d 0 book_staleness book f 125,143 6,693 48ms 361ms 3.8h 90.0d 0 book_staleness book g 131,950 13,518 91ms 12.2s 3.8d 108.6d 0 book_staleness book h 122,188 8,370 22ms 79ms 36.0min 89.9d 0 book_staleness last_trade_price c 57,472 54,579 11ms 48ms 226ms 5.0s 0 transport_latency_assumed last_trade_price e 57,380 274 46ms 177ms 2.1s 6.8s 0 transport_latency_assumed last_trade_price f 56,994 140 54ms 177ms 2.3s 8.9s 0 transport_latency_assumed last_trade_price g 56,585 16 97ms 517ms 7.1s 24.6s 0 transport_latency_assumed last_trade_price h 57,306 2,556 25ms 80ms 309ms 5.5s 0 transport_latency_assumed market_resolved c 685 649 6ms 15ms 54.3s 58.9s 0 transport_latency_assumed market_resolved e 685 18 38ms 192ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 685 2 45ms 192ms 53.4s 1.0min 0 transport_latency_assumed market_resolved g 685 4 84ms 302ms 31.9s 59.0s 0 transport_latency_assumed market_resolved h 685 26 19ms 88ms 1.0min 1.0min 0 transport_latency_assumed new_market c 545 392 63ms 13.3s 21.9s 1.2min 0 transport_latency_assumed new_market e 545 98 180ms 14.2s 22.0s 1.2min 0 transport_latency_assumed new_market f 545 97 172ms 13.7s 22.4s 1.4min 0 transport_latency_assumed new_market g 545 61 258ms 20.5s 23.9s 56.4s 0 transport_latency_assumed new_market h 545 145 86ms 445ms 22.3s 24.4s 0 transport_latency_assumed price_change c 89,517,580 85,362,264 6ms 14ms 125ms 3.6s 0 transport_latency_assumed price_change e 89,476,750 359,666 38ms 55ms 441ms 8.6s 0 transport_latency_assumed price_change f 89,413,936 143,666 45ms 65ms 446ms 9.0s 0 transport_latency_assumed price_change g 89,339,038 21,326 81ms 121ms 1.1s 24.7s 0 transport_latency_assumed price_change h 89,446,592 3,642,166 18ms 31ms 211ms 7.9s 0 transport_latency_assumed tick_size_change c 3,532 3,446 5ms 9ms 30ms 97ms 0 transport_latency_assumed tick_size_change e 3,532 not meas. 38ms 43ms 110ms 174ms 0 transport_latency_assumed tick_size_change f 3,532 not meas. 45ms 50ms 138ms 208ms 0 transport_latency_assumed tick_size_change g 3,532 not meas. 80ms 99ms 230ms 451ms 0 transport_latency_assumed tick_size_change h 3,532 86 18ms 24ms 44ms 69ms 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-15/12/2026-09-15T12.parquet sha256sum 2026-09-15T12.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.