Hour audit: 2026-08-28T22
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.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-28T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-28T22:00:00.019208874+00:00 · last event 2026-08-28T22:59:59.999985232+00:00
VOLUME 93,507,640 rows · 1,004,341,883 bytes (957.82 MiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 92,859,344 · b: 92,648,384 · e: 92,092,188 · h: 89,499,319 · a: 88,983,949 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · b: not measured · e: not measured · h: not measured · a: not measured (rows of the merged file that came from it; these partition it)
35 product-machine pairs publish no supplied count, and the figures above do not reconcile to the file's row count, so the split is incomplete by an unrecorded amount
INTEGRITY sha256 a71364c54d81995e62ba33060cf9788ee5215fd2252f157bd005a280563ff87f
the corpus checksum ledger names this file with the same digest
joined 93,508,688 to merged 93,507,640, minus 1,048 (minus 0.0011%)
boundary drops 1,048 · 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 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 not evaluated
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
SKIPPED which machines were expected is not published beside this hour
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 7,179,516 86,426,088 0-27 4b879c24bfee847d9f107382197b0ab7c4635782686c163b6ae3c4ee41498a96 book 759,135 67,376,654 28-30 3b88419e40a53642c0372e6bb26985691f16ba2c208aac65729656f56a9397cd last_trade_price 60,947 3,425,445 31-31 373dd364aa016b6f275f8326f09c26b3d2755e1f3df4c6235a9e7443b7ef2087 market_resolved 2,702 416,909 32-32 fd824dda5dce2142bd3b56da045a729363d1b47abd8eeab496dd4dbb46ecd613 new_market 2,354 228,744 33-33 2dbf175d730ed0d6e7f5281034d6194ccecd7fb50df92cabd966d0983731269b price_change 85,500,506 845,306,462 34-360 e0fa181fe5783df64fd1ea6e96ca0c8faca43b1fb11892ab0d94d9d2b0b19c76 tick_size_change 2,480 92,189 361-361 b028550e9c3fd0f9d2520ea7297dc7b35643edf67f3646ab3488cb363ac462cd EVENT MIX count share price_change 85,500,506 91.44% best_bid_ask 7,179,516 7.68% book 759,135 0.81% last_trade_price 60,947 0.07% market_resolved 2,702 <0.01% tick_size_change 2,480 <0.01% new_market 2,354 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,179,572 7,179,516 56 1,967 FULL book 759,153 759,135 18 182,177 FULL last_trade_price 60,947 60,947 0 177 FULL market_resolved 2,702 2,702 0 80 FULL new_market 2,354 2,354 0 225 FULL price_change 85,501,480 85,500,506 974 761 FULL tick_size_change 2,480 2,480 0 24 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 6,863,757 not meas. 39ms 65ms 633ms 33.1s 0 not stated best_bid_ask b 7,170,111 not meas. 51ms 96ms 888ms 27.4s 0 not stated best_bid_ask c 7,179,306 not meas. 4ms 10ms 214ms 3.0s 0 not stated best_bid_ask e 7,156,917 not meas. 45ms 166ms 3.6s 39.0s 0 not stated best_bid_ask h 6,857,890 not meas. 12ms 23ms 246ms 38.2s 0 not stated book a 492,577 not meas. 1.0min 9.6h 25.1d 91.0d 0 not stated book b 128,258 not meas. 109ms 4.7s 1.4h 89.4d 0 not stated book c 129,054 not meas. 6ms 43ms 4.5s 72.5d 0 not stated book e 130,271 not meas. 127ms 8.5s 5.3h 9.8d 0 not stated book h 499,774 not meas. 1.0min 9.3h 25.1d 91.0d 0 not stated last_trade_price a 56,478 not meas. 68ms 2.3s 11.2s 33.1s 0 not stated last_trade_price b 58,931 not meas. 89ms 2.9s 13.5s 27.1s 0 not stated last_trade_price c 60,914 not meas. 9ms 46ms 278ms 5.0s 0 not stated last_trade_price e 57,491 not meas. 89ms 5.0s 13.5s 38.6s 0 not stated last_trade_price h 57,750 not meas. 19ms 154ms 757ms 17.0s 0 not stated market_resolved a 2,467 not meas. 41ms 232ms 780ms 5.0min 0 not stated market_resolved b 2,468 not meas. 52ms 275ms 1.0s 14.9s 0 not stated market_resolved c 2,468 not meas. 4ms 11ms 59.7s 1.1min 0 not stated market_resolved e 2,463 not meas. 45ms 398ms 2.1s 1.2min 0 not stated market_resolved h 2,394 not meas. 13ms 102ms 4.4min 4.9min 0 not stated new_market a 1,448 not meas. 358ms 29.5s 51.1s 1.7h 0 not stated new_market b 1,448 not meas. 395ms 25.2s 51.2s 41.2min 0 not stated new_market c 1,448 not meas. 134ms 31.5s 49.1s 2.7h 0 not stated new_market e 1,448 not meas. 278ms 27.4s 58.2s 1.9h 0 not stated new_market h 1,223 not meas. 112ms 33.9s 4.0min 50.7min 0 not stated price_change a 81,564,762 not meas. 40ms 86ms 1.9s 33.3s 0 not stated price_change b 85,284,688 not meas. 51ms 127ms 2.8s 27.4s 0 not stated price_change c 85,483,674 not meas. 4ms 8ms 203ms 3.3s 0 not stated price_change e 84,741,122 not meas. 45ms 219ms 6.9s 39.1s 0 not stated price_change h 82,077,880 not meas. 12ms 23ms 285ms 38.4s 0 not stated tick_size_change a 2,460 not meas. 39ms 45ms 521ms 724ms 0 not stated tick_size_change b 2,480 not meas. 51ms 64ms 471ms 1.6s 0 not stated tick_size_change c 2,480 not meas. 4ms 7ms 200ms 483ms 0 not stated tick_size_change e 2,476 not meas. 45ms 123ms 3.4s 10.0s 0 not stated tick_size_change h 2,408 not meas. 12ms 20ms 73ms 847ms 0 not stated
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-28/22/2026-08-28T22.parquet sha256sum 2026-08-28T22.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.