Hour audit: 2026-08-30T04
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-30T04 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T04:00:00.037940107+00:00 · last event 2026-08-30T04:59:59.999949709+00:00
VOLUME 99,886,743 rows · 1,022,944,066 bytes (975.56 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 99,473,817 · h: 99,426,916 · e: 99,165,105 · a: 95,811,384 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 57,110 (0.06%) · h: 310,365 (0.31%) · e: 99,163,912 (99.28%) · a: 355,356 (0.36%) (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 99,886,743 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
the listing string reads "abche"; the letters above are the machines whose rows are in the file
INTEGRITY sha256 7345e8b451a7baafae9aacd5ac2f6b01936a03d7a8d40e6d99f1409207571d04
the corpus checksum ledger names this file with the same digest
joined 99,887,968 to merged 99,886,743, minus 1,225 (minus 0.0012%)
boundary drops 1,225 · 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-01T11:36:32Z as aceh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,068,782 101,208,830 0-34 e5b2e8e795877444238bf25eccafba7a434d4e0581e9858f3329f8ea691a46ec book 538,704 52,182,429 35-37 9932ed492bcaada15181f9a3a6a37f8321f9b135c8f273d089b477e3dbe6b366 last_trade_price 45,002 2,624,522 38-38 08e906dd94150433b9942af7479a86978aca73e168dfe6b1c105202d4b8f2bb4 market_resolved 1,511 243,702 39-39 7f4c46acc2e8549f6bbd896e8ed8d688db2f25b38e40b1c220c00ca4d8ea4746 new_market 5,012 517,709 40-40 02493845c208787d1c878518b0edb6820cc43bd4ef1c39db72cf22c38112798c price_change 90,224,008 864,888,824 41-385 41b85634b9504a80e0bfbf5d3f3b661cc3a7cbeb4914674c60f08a9e5be414db tick_size_change 3,724 136,960 386-386 d5c49c18d7d3005ec9f7d8a938acd9bacc7787371fc87966734f83a8ec726ae1 EVENT MIX count share price_change 90,224,008 90.33% best_bid_ask 9,068,782 9.08% book 538,704 0.54% last_trade_price 45,002 0.05% new_market 5,012 <0.01% tick_size_change 3,724 <0.01% market_resolved 1,511 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,068,893 9,068,782 111 72,626 PARTIAL book 538,738 538,704 34 171,444 PARTIAL last_trade_price 45,002 45,002 0 3,178 PARTIAL market_resolved 1,511 1,511 0 1,501 PARTIAL new_market 5,012 5,012 0 3,420 PARTIAL price_change 90,225,088 90,224,008 1,080 129,761 PARTIAL tick_size_change 3,724 3,724 0 931 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,678,052 524 36ms 58ms 534ms 25.5s 0 transport_latency_assumed best_bid_ask c 9,066,526 1,176 4ms 7ms 280ms 6.3s 0 transport_latency_assumed best_bid_ask e 9,055,508 9,055,397 44ms 130ms 1.5s 42.7s 0 transport_latency_assumed best_bid_ask h 9,065,620 11,685 12ms 19ms 561ms 58.9s 0 transport_latency_assumed book a 471,806 350,463 1.3min 8.5h 27.7d 92.3d 0 book_staleness book c 143,106 42,887 10ms 20.2min 21.6d 92.3d 0 book_staleness book e 128,468 128,464 170ms 5.7min 21.6d 92.3d 0 book_staleness book h 112,478 16,890 21ms 33.1s 7.6d 73.8d 0 book_staleness last_trade_price a 42,857 2 46ms 619ms 5.9s 25.0s 0 transport_latency_assumed last_trade_price c 44,986 4 9ms 44ms 314ms 4.9s 0 transport_latency_assumed last_trade_price e 44,454 44,454 62ms 2.1s 13.5s 42.7s 0 transport_latency_assumed last_trade_price h 44,991 542 18ms 97ms 778ms 56.3s 0 transport_latency_assumed market_resolved a 1,481 3 36ms 287ms 865ms 1.8s 0 transport_latency_assumed market_resolved c 1,501 5 4ms 10ms 314ms 641ms 0 transport_latency_assumed market_resolved e 1,501 1,501 44ms 299ms 1.5s 1.1min 0 transport_latency_assumed market_resolved h 1,501 2 13ms 67ms 814ms 1.0min 0 transport_latency_assumed new_market a 3,420 394 361ms 48.7s 1.1min 4.5min 0 transport_latency_assumed new_market c 3,420 260 165ms 50.2s 1.2min 3.1min 0 transport_latency_assumed new_market e 3,420 3,420 273ms 50.0s 1.1min 7.3min 0 transport_latency_assumed new_market h 3,420 938 230ms 50.0s 1.1min 2.8min 0 transport_latency_assumed price_change a 86,610,068 3,970 36ms 82ms 778ms 25.5s 0 transport_latency_assumed price_change c 90,210,554 12,778 4ms 8ms 283ms 6.5s 0 transport_latency_assumed price_change e 89,928,030 89,926,952 44ms 180ms 3.7s 42.7s 0 transport_latency_assumed price_change h 90,195,182 280,308 12ms 21ms 575ms 1.0min 0 transport_latency_assumed tick_size_change a 3,700 not meas. 37ms 403ms 791ms 11.5s 0 transport_latency_assumed tick_size_change c 3,724 not meas. 4ms 171ms 586ms 863ms 0 transport_latency_assumed tick_size_change e 3,724 3,724 45ms 598ms 1.5s 11.3s 0 transport_latency_assumed tick_size_change h 3,724 not meas. 12ms 276ms 2.4s 21.2s 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-30/04/2026-08-30T04.parquet sha256sum 2026-08-30T04.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.