Hour audit: 2026-08-31T13
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-08-31T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-31T13:00:00.035722929+00:00 · last event 2026-08-31T13:59:59.999981146+00:00
VOLUME 98,913,933 rows · 1,025,507,665 bytes (978.00 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 98,439,392 · h: 98,368,682 · e: 97,371,599 · b: 6,834,152 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 51,514 (0.05%) · h: 1,073,449 (1.09%) · e: 97,370,033 (98.44%) · b: 418,937 (0.42%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 98,913,933 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 0bb2e8446570e31720dd700d418c04eb57bce1fc97b6645c155041c091f245f5
the corpus checksum ledger names this file with the same digest
joined 98,915,630 to merged 98,913,933, minus 1,697 (minus 0.0017%)
boundary drops 1,697 · 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-02T02:13:23Z as bceh
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 8,554,551 96,187,164 0-32 a3edeef1de428edd6037dd19afba3ab17188f61dc97097f41736a4fa9eb45362 book 588,462 57,233,787 33-35 f4d91b2160c9f81a1615ba9cf1d52385c0c5f745b7dfd5e27678ab1db731f6ed last_trade_price 101,357 5,466,546 36-36 b6a890f58d03d359f7a8fb8fe4739077d758587448afa589a9e7b0c95f24b7bc market_resolved 32,120 4,873,577 37-37 6809ff3f869c38bb148c0916cd79b4b77816de6a432a2b86d188117371a0c502 new_market 51,159 6,892,230 38-38 510787802d35c7cf91736d55804edd0cf7604fbe5521353ac10b43a0a16d8bc9 price_change 89,583,762 853,633,864 39-380 8019bf9eed00a60695e52c955369dd1d18ccea3886e68c3d692d4d21fe44b6a8 tick_size_change 2,522 92,753 381-381 e49b0b49d01a694824b6a4991d2d9b5a8899a2425dee0f2c1ac1b266f3d068b6 EVENT MIX count share price_change 89,583,762 90.57% best_bid_ask 8,554,551 8.65% book 588,462 0.59% last_trade_price 101,357 0.10% new_market 51,159 0.05% market_resolved 32,120 0.03% tick_size_change 2,522 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,554,631 8,554,551 80 43,874 FULL book 588,476 588,462 14 169,791 FULL last_trade_price 101,359 101,357 2 3,708 FULL market_resolved 32,120 32,120 0 32,074 FULL new_market 51,286 51,159 127 47,706 FULL price_change 89,585,236 89,583,762 1,474 38,466 FULL tick_size_change 2,522 2,522 0 590 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 647,486 not meas. 54ms 127ms 1.3s 17.5s 0 transport_latency_assumed best_bid_ask c 8,552,454 3,436 4ms 11ms 193ms 9.4s 0 transport_latency_assumed best_bid_ask e 8,509,840 8,509,760 46ms 155ms 3.5s 41.8s 0 transport_latency_assumed best_bid_ask h 8,549,601 41,355 12ms 29ms 429ms 58.7s 0 transport_latency_assumed book b 357,305 338,884 3.1min 1.6d 29.1d 93.6d 0 book_staleness book c 221,191 9,147 7ms 50ms 21.2min 75.1d 0 book_staleness book e 212,552 212,542 151ms 12.4s 2.6h 39.6d 0 book_staleness book h 221,249 27,889 19ms 178ms 23.5min 93.7d 0 book_staleness last_trade_price b 4,927 1 137ms 7.4s 16.3s 17.6s 0 transport_latency_assumed last_trade_price c 101,325 22 9ms 41ms 235ms 9.6s 0 transport_latency_assumed last_trade_price e 92,661 92,659 98ms 7.2s 20.4s 41.8s 0 transport_latency_assumed last_trade_price h 101,274 8,675 19ms 98ms 770ms 11.2s 0 transport_latency_assumed market_resolved b 31,684 31,680 19.5h 1.5d 1.6d 1.6d 0 transport_latency_assumed market_resolved c 440 not meas. 4ms 17ms 270ms 380ms 0 transport_latency_assumed market_resolved e 440 440 47ms 550ms 2.9s 6.4s 0 transport_latency_assumed market_resolved h 440 not meas. 14ms 95ms 380ms 704ms 0 transport_latency_assumed new_market b 47,368 46,292 23.8h 2.0d 2.5d 2.6d 0 transport_latency_assumed new_market c 3,302 541 51ms 19.0s 34.7s 1.4min 0 transport_latency_assumed new_market e 3,302 3,302 268ms 20.7s 32.3s 1.0min 0 transport_latency_assumed new_market h 3,302 1,024 157ms 20.9s 34.6s 1.1min 0 transport_latency_assumed price_change b 5,745,222 2,080 55ms 208ms 6.2s 17.8s 0 transport_latency_assumed price_change c 89,558,158 38,368 4ms 11ms 201ms 9.7s 0 transport_latency_assumed price_change e 88,550,294 88,548,820 46ms 250ms 9.2s 41.8s 0 transport_latency_assumed price_change h 89,490,294 994,494 13ms 33ms 443ms 59.1s 0 transport_latency_assumed tick_size_change b 160 not meas. 55ms 112ms 143ms 147ms 0 transport_latency_assumed tick_size_change c 2,522 not meas. 4ms 7ms 82ms 231ms 0 transport_latency_assumed tick_size_change e 2,510 2,510 46ms 121ms 1.1s 14.7s 0 transport_latency_assumed tick_size_change h 2,522 12 12ms 18ms 157ms 2.7s 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-08-31/13/2026-08-31T13.parquet sha256sum 2026-08-31T13.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.