Hour audit: 2026-09-13T01
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-13T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T01:00:00.001021283+00:00 · last event 2026-09-13T01:59:59.999951301+00:00
VOLUME 117,527,484 rows · 1,271,962,690 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 115,370,999 · h: 115,359,682 · f: 115,353,121 · g: 115,346,178 · c: 89,507,437 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,096,501 (0.93%) · h: 29,005,631 (24.68%) · f: 289,290 (0.25%) · g: 50,775 (0.04%) · c: 87,085,287 (74.10%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 117,527,484 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 46f9710c13762902ff5e846cd3d82d73776a42a97e88b21059b2d32b2bfe0c62
the corpus checksum ledger names this file with the same digest
joined 117,529,637 to merged 117,527,484, minus 2,153 (minus 0.0018%)
boundary drops 2,153 · 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-13T03:37:43Z 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 12,436,360 135,333,348 0-47 eb74f20178051a0b0039ddf8bf0ff1a75f2ec841ec8fe21c5804ca4569d462f2 book 2,287,519 88,596,617 48-56 e35dd407b53908e42c6cf95f63c7fe160819551769217746cccc20aaeb8b4893 last_trade_price 46,343 2,691,701 57-57 067e4dd0b50c9e417ed54d7f66f74786d00b11af3fce7e5785d3f69d91669658 market_resolved 4,246 458,325 58-58 1036756cddf631982a53123d956f66d913b9d468910ac93918f5d047acf87d91 new_market 698 56,603 59-59 0863ce4711b8aedd2f1128e551ecb55dfd1deba926dcc1098ccc5c74a6007951 price_change 102,744,010 1,043,183,118 60-451 655bb21899e13f45f62946b87befeabac56cfce24e12d24ecf5404d5bdfc38a8 tick_size_change 8,308 306,772 452-452 369ddf1f6f4cf10633e3c71c957d18e84499cd554dbf29d56005feace3598cb8 EVENT MIX count share price_change 102,744,010 87.42% best_bid_ask 12,436,360 10.58% book 2,287,519 1.95% last_trade_price 46,343 0.04% tick_size_change 8,308 <0.01% market_resolved 4,246 <0.01% new_market 698 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,436,602 12,436,360 242 4,927 FULL book 2,287,601 2,287,519 82 185,279 FULL last_trade_price 46,344 46,343 1 504 FULL market_resolved 4,246 4,246 0 222 FULL new_market 698 698 0 31 FULL price_change 102,745,838 102,744,010 1,828 2,860 FULL tick_size_change 8,308 8,308 0 553 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,487,598 9,246,705 4ms 8ms 44ms 1.9s 0 transport_latency_assumed best_bid_ask e 12,435,117 105,227 41ms 45ms 91ms 3.3s 0 transport_latency_assumed best_bid_ask f 12,435,060 25,453 46ms 50ms 109ms 4.7s 0 transport_latency_assumed best_bid_ask g 12,433,137 1,527 77ms 91ms 191ms 16.7s 0 transport_latency_assumed best_bid_ask h 12,435,552 3,057,448 17ms 21ms 70ms 8.1s 0 transport_latency_assumed book c 2,208,148 2,117,643 34.7min 1.3d 35.2d 106.2d 0 book_staleness book e 153,665 48,089 47ms 3.9h 19.5d 106.1d 0 book_staleness book f 143,882 28,731 50ms 3.7h 13.3d 88.1d 0 book_staleness book g 160,708 33,227 95ms 4.8h 21.5d 87.7d 0 book_staleness book h 145,641 59,829 23ms 3.8h 18.3d 106.1d 0 book_staleness last_trade_price c 31,725 30,427 10ms 38ms 152ms 4.8s 0 transport_latency_assumed last_trade_price e 46,280 732 47ms 95ms 394ms 4.9s 0 transport_latency_assumed last_trade_price f 46,255 244 52ms 103ms 451ms 4.9s 0 transport_latency_assumed last_trade_price g 46,166 92 86ms 180ms 531ms 5.4s 0 transport_latency_assumed last_trade_price h 46,264 14,848 22ms 56ms 248ms 8.2s 0 transport_latency_assumed market_resolved c 3,714 3,646 6ms 13.2min 21.2min 21.5min 0 transport_latency_assumed market_resolved e 2,744 30 43ms 122ms 47.4s 59.0s 0 transport_latency_assumed market_resolved f 2,744 33 47ms 126ms 283ms 1.1s 0 transport_latency_assumed market_resolved g 2,743 not meas. 85ms 236ms 644ms 1.0min 0 transport_latency_assumed market_resolved h 2,744 537 19ms 58ms 47.2s 58.6s 0 transport_latency_assumed new_market c 502 392 14.1s 44.8min 5.3h 6.0h 0 transport_latency_assumed new_market e 335 78 87ms 19.2s 29.0s 34.8min 0 transport_latency_assumed new_market f 334 50 77ms 12.9s 6.5min 2.9h 0 transport_latency_assumed new_market g 334 34 120ms 13.4s 36.4s 1.0h 0 transport_latency_assumed new_market h 334 144 58ms 11.8s 9.4min 3.3h 0 transport_latency_assumed price_change c 77,769,654 75,680,537 4ms 9ms 51ms 2.0s 0 transport_latency_assumed price_change e 102,724,550 942,192 41ms 46ms 116ms 3.5s 0 transport_latency_assumed price_change f 102,716,538 234,730 46ms 51ms 130ms 4.7s 0 transport_latency_assumed price_change g 102,694,782 15,895 77ms 92ms 231ms 17.3s 0 transport_latency_assumed price_change h 102,720,839 25,870,656 17ms 23ms 81ms 8.2s 0 transport_latency_assumed tick_size_change c 6,096 5,937 4ms 9ms 37ms 225ms 0 transport_latency_assumed tick_size_change e 8,308 153 41ms 45ms 113ms 282ms 0 transport_latency_assumed tick_size_change f 8,308 49 46ms 53ms 156ms 275ms 0 transport_latency_assumed tick_size_change g 8,308 not meas. 77ms 92ms 340ms 587ms 0 transport_latency_assumed tick_size_change h 8,308 2,169 17ms 25ms 73ms 255ms 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-13/01/2026-09-13T01.parquet sha256sum 2026-09-13T01.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.