Hour audit: 2026-09-05T12
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-09-05T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T12:00:00.055561325+00:00 · last event 2026-09-05T12:59:59.999948956+00:00
VOLUME 114,376,344 rows · 1,203,910,708 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 112,801,803 · h: 112,787,675 · f: 112,671,694 · g: 112,575,682 · c: 95,772,424 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 59,172 (0.05%) · h: 13,670 (0.01%) · f: 195,670 (0.17%) · g: 112,573,439 (98.42%) · c: 1,534,393 (1.34%) (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 114,376,344 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 82749ec423e231bd0a5d50106f85af173a4494f4d3e14dc4ec3f6d89d8c55598
the corpus checksum ledger names this file with the same digest
joined 114,378,591 to merged 114,376,344, minus 2,247 (minus 0.0020%)
boundary drops 2,247 · 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-05T22:14:13Z as cefgh
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 10,423,920 116,164,669 0-39 cc33622ed6049af16f899f85ffffd4b7a011cdbb8a33cc7be478d98e594bf4e3 book 1,682,599 84,266,046 40-46 48f6dadb683d94d748ebf5484307de6e9ee572c9aff1ad12fdb90be77730586b last_trade_price 64,444 3,665,066 47-47 9796180933967aa2712d696ae92e4b45a4d67533df939e8af0cc66e93ed4580b market_resolved 879 116,458 48-48 39398aa472f3bcd181a59e1852bb9651ae86dfa0d73b4d0e65037d9a7c109387 new_market 1,446 141,201 49-49 0e3afcd1f1e2884be14dd350d6d190190da51d5ac43e0e4ab9fe98c80611044d price_change 102,196,632 998,026,572 50-439 491a8229c244ac5c7eafb7d1d6a18986a7cbb5472c4cda5f62cb6aa86985c091 tick_size_change 6,424 229,428 440-440 d15561b629d92d25e4619e3726a7bf845123a1d32bb73450c75ac13e5cd3ff32 EVENT MIX count share price_change 102,196,632 89.35% best_bid_ask 10,423,920 9.11% book 1,682,599 1.47% last_trade_price 64,444 0.06% tick_size_change 6,424 <0.01% new_market 1,446 <0.01% market_resolved 879 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,424,168 10,423,920 248 2,421 FULL book 1,682,605 1,682,599 6 187,541 FULL last_trade_price 64,445 64,444 1 428 FULL market_resolved 879 879 0 40 FULL new_market 1,446 1,446 0 11 FULL price_change 102,198,624 102,196,632 1,992 846 FULL tick_size_change 6,424 6,424 0 214 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,736,435 535 9ms 22ms 101ms 4.6s 0 transport_latency_assumed best_bid_ask e 10,421,624 4,230 39ms 43ms 137ms 1.5s 0 transport_latency_assumed best_bid_ask f 10,413,547 9,316 48ms 59ms 273ms 14.7s 0 transport_latency_assumed best_bid_ask g 10,408,920 10,408,672 82ms 109ms 551ms 16.7s 0 transport_latency_assumed best_bid_ask h 10,422,757 1,167 18ms 23ms 127ms 15.2s 0 transport_latency_assumed book c 1,647,847 1,529,988 2.8min 13.8h 34.0d 98.6d 0 book_staleness book e 133,420 2,039 40ms 93ms 951ms 80.0d 0 book_staleness book f 135,953 5,309 50ms 181ms 4.6min 23.6h 0 book_staleness book g 144,078 144,076 83ms 3.0s 5.2h 37.9d 0 book_staleness book h 133,944 1,187 21ms 46ms 2.2s 80.0d 0 book_staleness last_trade_price c 54,346 3 16ms 45ms 271ms 4.9s 0 transport_latency_assumed last_trade_price e 64,377 635 44ms 87ms 559ms 4.9s 0 transport_latency_assumed last_trade_price f 63,324 1,441 54ms 113ms 5.3s 14.7s 0 transport_latency_assumed last_trade_price g 62,340 62,339 89ms 185ms 2.3s 16.7s 0 transport_latency_assumed last_trade_price h 64,402 26 23ms 55ms 319ms 7.3s 0 transport_latency_assumed market_resolved c 766 139 14ms 5.7min 13.3min 15.0min 0 transport_latency_assumed market_resolved e 707 not meas. 40ms 195ms 510ms 588ms 0 transport_latency_assumed market_resolved f 707 23 48ms 116ms 1.6s 2.1s 0 transport_latency_assumed market_resolved g 707 707 77ms 229ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 707 10 18ms 141ms 59.7s 59.8s 0 transport_latency_assumed new_market c 1,003 126 113ms 4.2min 2.5h 3.4h 0 transport_latency_assumed new_market e 903 160 163ms 15.4s 22.1s 1.0min 0 transport_latency_assumed new_market f 903 187 180ms 16.9s 23.2s 1.5min 0 transport_latency_assumed new_market g 903 903 296ms 13.8s 23.1s 1.5min 0 transport_latency_assumed new_market h 903 70 134ms 14.8s 24.4s 2.2min 0 transport_latency_assumed price_change c 85,326,459 3,602 10ms 23ms 134ms 7.2s 0 transport_latency_assumed price_change e 102,174,348 52,108 39ms 45ms 184ms 1.8s 0 transport_latency_assumed price_change f 102,050,836 179,394 48ms 68ms 333ms 14.7s 0 transport_latency_assumed price_change g 101,952,310 101,950,318 81ms 133ms 674ms 16.7s 0 transport_latency_assumed price_change h 102,158,538 11,210 18ms 25ms 164ms 16.9s 0 transport_latency_assumed tick_size_change c 5,568 not meas. 11ms 22ms 205ms 809ms 0 transport_latency_assumed tick_size_change e 6,424 not meas. 39ms 43ms 184ms 1.0s 0 transport_latency_assumed tick_size_change f 6,424 not meas. 47ms 96ms 197ms 584ms 0 transport_latency_assumed tick_size_change g 6,424 6,424 82ms 149ms 303ms 1.2s 0 transport_latency_assumed tick_size_change h 6,424 not meas. 18ms 22ms 179ms 3.6s 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-09-05/12/2026-09-05T12.parquet sha256sum 2026-09-05T12.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.