Hour audit: 2026-08-29T16
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-29T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T16:00:00.037808567+00:00 · last event 2026-08-29T16:59:59.999959784+00:00
VOLUME 116,449,060 rows · 1,239,068,501 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 116,068,436 · h: 116,052,406 · e: 114,740,207 · a: 111,627,129 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · h: not measured · e: not measured · a: not measured (rows of the merged file that came from it; these partition it)
28 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 bbe4f5d1b050ac4c886d178232fa02d6ab5a78db288df65b8c2e95ec22f3d40d
the corpus checksum ledger names this file with the same digest
joined 116,450,324 to merged 116,449,060, minus 1,264 (minus 0.0011%)
boundary drops 1,264 · 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 10,563,928 122,308,085 0-40 d2ddede64c5efde1bace122bb944f287992767648d65e836595ed70188e7ec67 book 535,465 56,203,299 41-43 9ea397166ba608f14915fafa6ab473b5be8712f4d6072810006f590b4314caea last_trade_price 77,105 4,464,343 44-44 e31db3dabe4ca2107e6f90b8bc06b4efb656ed6a9dd306b0d443fb27199d6f9e market_resolved 2,750 419,287 45-45 30049766fa6f21c00239b45a01289f80d43dea8b2694fd98a709b30ea1d434dd new_market 1,856 187,292 46-46 9c1453815031a483de338a7fc6c22883060de13304417a797ff087dd8c52afd1 price_change 105,260,872 1,053,900,123 47-448 b51e11c9502fcb694330c031f5d7bfe02280652369dfb0fd68a44d4d02ab44af tick_size_change 7,084 259,100 449-449 d7fae48f2c7029b7508be9278d571f4c70823955b712a6f12d822d88c3b8180f EVENT MIX count share price_change 105,260,872 90.39% best_bid_ask 10,563,928 9.07% book 535,465 0.46% last_trade_price 77,105 0.07% tick_size_change 7,084 <0.01% market_resolved 2,750 <0.01% new_market 1,856 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,564,048 10,563,928 120 86,926 PARTIAL book 535,489 535,465 24 180,725 PARTIAL last_trade_price 77,105 77,105 0 5,204 PARTIAL market_resolved 2,750 2,750 0 2,645 PARTIAL new_market 1,856 1,856 0 1,221 PARTIAL price_change 105,261,992 105,260,872 1,120 147,249 PARTIAL tick_size_change 7,084 7,084 0 1,771 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 10,116,393 not meas. 36ms 50ms 335ms 17.4s 0 not stated best_bid_ask c 10,563,350 not meas. 4ms 9ms 150ms 9.6s 0 not stated best_bid_ask e 10,526,940 not meas. 45ms 132ms 3.0s 26.6s 0 not stated best_bid_ask h 10,562,246 not meas. 13ms 26ms 202ms 46.8s 0 not stated book a 512,025 not meas. 42.9s 4.2h 25.1d 91.7d 0 not stated book c 161,121 not meas. 7ms 35ms 38.7s 91.7d 0 not stated book e 160,073 not meas. 125ms 8.3s 1.4h 29.3d 0 not stated book h 160,117 not meas. 23ms 132ms 3.8s 73.2d 0 not stated last_trade_price a 72,555 not meas. 51ms 1.5s 10.9s 17.5s 0 not stated last_trade_price c 77,087 not meas. 9ms 41ms 254ms 5.0s 0 not stated last_trade_price e 71,814 not meas. 80ms 4.5s 13.9s 26.6s 0 not stated last_trade_price h 76,953 not meas. 19ms 103ms 771ms 22.6s 0 not stated market_resolved a 2,548 not meas. 39ms 185ms 717ms 5.3min 0 not stated market_resolved c 2,645 not meas. 4ms 9ms 73ms 1.0min 0 not stated market_resolved e 2,645 not meas. 48ms 380ms 51.2s 1.0min 0 not stated market_resolved h 2,645 not meas. 15ms 51ms 152ms 1.0min 0 not stated new_market a 1,225 not meas. 287ms 3.6min 4.1min 12.2min 0 not stated new_market c 1,221 not meas. 86ms 16.4s 21.1s 16.6min 0 not stated new_market e 1,221 not meas. 220ms 15.8s 23.2s 1.3min 0 not stated new_market h 1,221 not meas. 148ms 15.9s 22.2s 4.6min 0 not stated price_change a 100,915,571 not meas. 37ms 77ms 1.2s 17.5s 0 not stated price_change c 105,255,928 not meas. 4ms 9ms 171ms 11.2s 0 not stated price_change e 103,970,430 not meas. 45ms 278ms 6.9s 26.6s 0 not stated price_change h 105,242,140 not meas. 14ms 30ms 243ms 47.3s 0 not stated tick_size_change a 6,812 not meas. 36ms 43ms 167ms 520ms 0 not stated tick_size_change c 7,084 not meas. 4ms 8ms 62ms 276ms 0 not stated tick_size_change e 7,084 not meas. 45ms 123ms 2.2s 20.4s 0 not stated tick_size_change h 7,084 not meas. 14ms 29ms 101ms 367ms 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-29/16/2026-08-29T16.parquet sha256sum 2026-08-29T16.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.