Hour audit: 2026-08-30T13
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-30T13 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T13:00:00.034603939+00:00 · last event 2026-08-30T13:59:59.999996616+00:00
VOLUME 104,786,902 rows · 1,104,965,704 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 104,420,549 · h: 104,378,295 · e: 103,917,780 · a: 100,666,445 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 34,855 (0.03%) · h: 483,528 (0.46%) · e: 103,916,578 (99.17%) · a: 351,941 (0.34%) (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 104,786,902 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 91c262eae39b6c1773e61c54867b4852e4d29aea1912232bf8fe13e2c8524512
the corpus checksum ledger names this file with the same digest
joined 104,788,117 to merged 104,786,902, minus 1,215 (minus 0.0012%)
boundary drops 1,215 · 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-08-30T15:32:59Z 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 8,658,460 97,111,014 0-33 ca4906281050d3ca6b08e78f44203b30ef3f8fc2a4cf807f45229726e3595d34 book 517,078 55,006,064 34-35 e3c1c0f88f1991d143a7a2e97ae53d60b10d2161144fb2c7f049f4d438d28958 last_trade_price 76,878 4,368,299 36-36 f2d5eb32186c8a20cc00feb04e7c53dfe58c7c0ea8fbfd22991dc73ffef2ac7c market_resolved 620 91,559 37-37 8d7d97c1a4181f67ee078c8ff289fc6eba0f26c256266d2fc63de28382d904ae new_market 1,072 116,069 38-38 5ccc8fed59b3acd2cf5c0694f45a8cf4fc07d8f809edc4cd75477adce0d23884 price_change 95,527,602 946,890,813 39-403 34693563636020019bbbc5db2ce64079f9c1c8877956ae2b90bf635c9ae881a9 tick_size_change 5,192 187,070 404-404 8f6b5bbd7b43e6286d59665618b3a3f0bc84f5668409e5fe17113bc25e5ba29a EVENT MIX count share price_change 95,527,602 91.16% best_bid_ask 8,658,460 8.26% book 517,078 0.49% last_trade_price 76,878 0.07% tick_size_change 5,192 <0.01% new_market 1,072 <0.01% market_resolved 620 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,658,599 8,658,460 139 70,187 PARTIAL book 517,092 517,078 14 174,654 PARTIAL last_trade_price 76,878 76,878 0 4,849 PARTIAL market_resolved 620 620 0 559 PARTIAL new_market 1,072 1,072 0 753 PARTIAL price_change 95,528,664 95,527,602 1,062 129,784 PARTIAL tick_size_change 5,192 5,192 0 1,298 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,332,907 4 36ms 48ms 417ms 25.4s 0 transport_latency_assumed best_bid_ask c 8,658,012 547 4ms 8ms 78ms 11.3s 0 transport_latency_assumed best_bid_ask e 8,641,766 8,641,628 44ms 115ms 2.2s 39.1s 0 transport_latency_assumed best_bid_ask h 8,657,725 16,281 13ms 21ms 128ms 8.4s 0 transport_latency_assumed book a 501,552 348,662 48.5s 7.0h 26.6d 92.6d 0 book_staleness book c 159,582 1,630 7ms 26ms 2.3s 74.1d 0 book_staleness book e 158,624 158,614 109ms 8.2s 42.9min 3.0d 0 book_staleness book h 158,786 8,172 20ms 98ms 858ms 74.0d 0 book_staleness last_trade_price a 73,294 5 56ms 2.7s 12.0s 25.5s 0 transport_latency_assumed last_trade_price c 76,837 9 9ms 38ms 206ms 5.1s 0 transport_latency_assumed last_trade_price e 73,442 73,442 78ms 5.9s 16.5s 39.1s 0 transport_latency_assumed last_trade_price h 76,842 3,422 19ms 92ms 573ms 7.8s 0 transport_latency_assumed market_resolved a 551 47 37ms 229ms 441ms 561ms 0 transport_latency_assumed market_resolved c 559 14 5ms 13ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 559 559 45ms 556ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 559 not meas. 14ms 83ms 1.0min 1.0min 0 transport_latency_assumed new_market a 753 19 200ms 17.3s 26.2s 1.1min 0 transport_latency_assumed new_market c 753 75 71ms 18.2s 25.7s 1.1min 0 transport_latency_assumed new_market e 753 753 217ms 15.9s 25.9s 1.3min 0 transport_latency_assumed new_market h 753 225 86ms 15.1s 26.6s 2.0min 0 transport_latency_assumed price_change a 91,752,344 3,204 36ms 71ms 1.7s 25.5s 0 transport_latency_assumed price_change c 95,519,614 32,580 5ms 9ms 105ms 12.6s 0 transport_latency_assumed price_change e 95,037,448 95,036,394 44ms 218ms 6.9s 39.1s 0 transport_latency_assumed price_change h 95,478,438 455,424 13ms 23ms 164ms 9.1s 0 transport_latency_assumed tick_size_change a 5,044 not meas. 35ms 41ms 143ms 2.7s 0 transport_latency_assumed tick_size_change c 5,192 not meas. 5ms 8ms 32ms 248ms 0 transport_latency_assumed tick_size_change e 5,188 5,188 44ms 115ms 424ms 5.6s 0 transport_latency_assumed tick_size_change h 5,192 4 13ms 20ms 87ms 303ms 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/13/2026-08-30T13.parquet sha256sum 2026-08-30T13.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.