Hour audit: 2026-09-10T14
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-10T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T14:00:00.000067849+00:00 · last event 2026-09-10T14:59:59.999570944+00:00
VOLUME 120,008,916 rows · 1,302,829,766 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 117,737,215 · f: 117,724,833 · g: 117,671,460 · e: 116,979,498 · c: 93,447,670 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 30,100,028 (25.08%) · f: 556,705 (0.46%) · g: 53,585 (0.04%) · e: 1,339,558 (1.12%) · c: 87,959,040 (73.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 120,008,916 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e0ea6626e82c090508d75c7420f905ac165b4051a8ba6f0de6980a21de0e092c
the corpus checksum ledger names this file with the same digest
joined 120,015,562 to merged 120,008,916, minus 6,646 (minus 0.0055%)
boundary drops 6,646 · 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-10T16: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,463,645 130,702,548 0-43 00a46a9054e5ccb1d2ba7ce3b4ac2e3643beccbbe7d963d54dc8c7c27fbaf232 book 2,328,990 97,008,269 44-52 3239d0b99c86f76812bb5fb636a43e1ff5735de2fdc71fd78d021b8c57797eb5 last_trade_price 66,872 3,794,486 53-53 649596503ae1d636249a74feaf8f6196136a3797c50bdc7a267d969f355e381f market_resolved 1,181 121,730 54-54 7d45d07b52e5ac2885b0762f875848a9c0994438d25be5740bf9059baa3324a7 new_market 2,498 236,465 55-55 9a0b9a375e6d87cafdd1e3ba525a1af90e253031afc36887046b89d0a44d38a4 price_change 106,142,434 1,069,484,236 56-460 b90c19e242ca6b897ca4f03d0062b1372f77d7f7277efcebb803a52f64d4669f tick_size_change 3,296 118,931 461-461 9b8e0d914e0da708b7b38f094efb14f3a302f6a815f4d857e00a90966d4e4453 EVENT MIX count share price_change 106,142,434 88.45% best_bid_ask 11,463,645 9.55% book 2,328,990 1.94% last_trade_price 66,872 0.06% tick_size_change 3,296 <0.01% new_market 2,498 <0.01% market_resolved 1,181 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,463,911 11,463,645 266 2,825 FULL book 2,332,688 2,328,990 3,698 193,693 FULL last_trade_price 66,874 66,872 2 449 FULL market_resolved 1,181 1,181 0 33 FULL new_market 2,500 2,498 2 8 FULL price_change 106,145,112 106,142,434 2,678 1,556 FULL tick_size_change 3,296 3,296 0 82 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,867,490 8,336,932 6ms 15ms 184ms 20.1s 0 transport_latency_assumed best_bid_ask e 11,423,597 132,964 42ms 57ms 1.3s 27.3s 0 transport_latency_assumed best_bid_ask f 11,461,073 51,297 48ms 63ms 281ms 12.1s 0 transport_latency_assumed best_bid_ask g 11,459,772 4,103 80ms 114ms 528ms 21.4s 0 transport_latency_assumed best_bid_ask h 11,462,439 2,938,349 18ms 30ms 270ms 52.2s 0 transport_latency_assumed book c 2,285,663 2,270,909 28.9min 1.2d 32.8d 103.7d 0 book_staleness book e 146,446 12,391 49ms 5.5s 6.3h 1.1d 0 book_staleness book f 141,413 2,700 51ms 210ms 3.2s 41.2d 0 book_staleness book g 154,026 5,935 91ms 4.5s 23.4h 85.2d 0 book_staleness book h 142,078 37,055 23ms 71ms 4.0s 85.1d 0 book_staleness last_trade_price c 51,073 47,716 12ms 48ms 327ms 5.4s 0 transport_latency_assumed last_trade_price e 63,616 567 63ms 1.7s 8.5s 27.3s 0 transport_latency_assumed last_trade_price f 66,724 666 60ms 196ms 1.7s 11.9s 0 transport_latency_assumed last_trade_price g 66,669 123 96ms 340ms 6.7s 21.4s 0 transport_latency_assumed last_trade_price h 66,805 17,800 25ms 75ms 564ms 9.4s 0 transport_latency_assumed market_resolved c 1,000 947 33ms 12.2min 14.7min 17.2min 0 transport_latency_assumed market_resolved e 714 42 43ms 125ms 55.0s 57.9s 0 transport_latency_assumed market_resolved f 714 5 49ms 235ms 55.0s 57.9s 0 transport_latency_assumed market_resolved g 714 17 85ms 352ms 1.1s 1.8s 0 transport_latency_assumed market_resolved h 714 170 19ms 114ms 55.0s 58.4s 0 transport_latency_assumed new_market c 1,790 1,047 181ms 5.8min 13.4min 1.0h 0 transport_latency_assumed new_market e 1,472 278 195ms 21.0s 1.1min 40.7d 0 transport_latency_assumed new_market f 1,472 389 174ms 20.4s 1.3min 40.7d 0 transport_latency_assumed new_market g 1,470 151 311ms 22.5s 1.2min 1.5min 0 transport_latency_assumed new_market h 1,470 633 138ms 20.0s 1.1min 1.7min 0 transport_latency_assumed price_change c 82,237,686 77,298,678 6ms 16ms 190ms 20.3s 0 transport_latency_assumed price_change e 105,340,357 1,193,295 43ms 75ms 3.7s 27.3s 0 transport_latency_assumed price_change f 106,050,141 501,632 48ms 71ms 386ms 12.1s 0 transport_latency_assumed price_change g 105,985,513 43,256 81ms 135ms 869ms 21.5s 0 transport_latency_assumed price_change h 106,060,413 27,105,573 19ms 32ms 269ms 55.1s 0 transport_latency_assumed tick_size_change c 2,968 2,811 6ms 13ms 69ms 253ms 0 transport_latency_assumed tick_size_change e 3,296 21 42ms 65ms 325ms 1.3s 0 transport_latency_assumed tick_size_change f 3,296 16 47ms 59ms 204ms 369ms 0 transport_latency_assumed tick_size_change g 3,296 not meas. 79ms 93ms 276ms 563ms 0 transport_latency_assumed tick_size_change h 3,296 448 18ms 27ms 116ms 325ms 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-10/14/2026-09-10T14.parquet sha256sum 2026-09-10T14.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.