Hour audit: 2026-09-09T10
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-09T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T10:00:00.000023222+00:00 · last event 2026-09-09T10:59:59.999987824+00:00
VOLUME 109,632,019 rows · 1,164,969,969 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 107,553,537 · f: 107,541,061 · e: 107,532,826 · h: 107,470,778 · c: 86,839,087 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 35,604 (0.03%) · f: 155,901 (0.14%) · e: 853,948 (0.78%) · h: 26,950,688 (24.58%) · c: 81,635,878 (74.46%) (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 109,632,019 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 bbd4d36a193ec3f3ec263c707be70ea710c47a3ad31d0b42b4db06d4b217bb40
the corpus checksum ledger names this file with the same digest
joined 109,635,007 to merged 109,632,019, minus 2,988 (minus 0.0027%)
boundary drops 2,988 · 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-09T12:34:58Z 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 9,794,808 108,746,570 0-37 1f30030a162b410a86c8f6016eef10a7646a141dcc6cbdb7615e450d7f6b7b70 book 2,097,492 92,448,978 38-46 77ac71fa4a687d0302504a14763aff4f9a47001e837b0085baea7a673d1cb966 last_trade_price 60,027 3,393,248 47-47 ceafd9a02dfd89b7173fc29b9688174c06a8cbb45438571d826057cf66d5af93 market_resolved 1,386 154,028 48-48 602c038250c54884c86eb05d6e006e0f0c08346526add97e9ea6b906c586abe4 new_market 532 54,664 49-49 49b8747f353ec04bf696733b3583dc41d9736ed88c3cf3f04e255ab9353748bd price_change 97,674,466 958,799,552 50-422 8b8dcd7fbc6917c2af60510cc28e5741286b96c4cf648a96695e264f87e4ef7a tick_size_change 3,308 121,644 423-423 8f3f38437441f96cceeb365550b6ee1a38835e7c36f12eac6a80fbaec42a2e1e EVENT MIX count share price_change 97,674,466 89.09% best_bid_ask 9,794,808 8.93% book 2,097,492 1.91% last_trade_price 60,027 0.05% tick_size_change 3,308 <0.01% market_resolved 1,386 <0.01% new_market 532 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,795,025 9,794,808 217 3,399 FULL book 2,097,652 2,097,492 160 192,131 FULL last_trade_price 60,028 60,027 1 376 FULL market_resolved 1,386 1,386 0 68 FULL new_market 532 532 0 0 FULL price_change 97,677,076 97,674,466 2,610 2,900 FULL tick_size_change 3,308 3,308 0 139 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,764,803 7,313,474 5ms 11ms 72ms 4.5s 0 transport_latency_assumed best_bid_ask e 9,792,825 68,796 36ms 41ms 124ms 3.1s 0 transport_latency_assumed best_bid_ask f 9,793,188 10,612 47ms 53ms 143ms 4.0s 0 transport_latency_assumed best_bid_ask g 9,792,323 736 85ms 98ms 251ms 9.2s 0 transport_latency_assumed best_bid_ask h 9,793,888 2,401,190 13ms 18ms 80ms 7.3s 0 transport_latency_assumed book c 2,050,508 2,017,226 22.8min 1.2d 31.8d 102.5d 0 book_staleness book e 139,785 14,476 39ms 31.3s 1.7d 84.0d 0 book_staleness book f 130,793 6,533 50ms 272ms 13.1h 84.0d 0 book_staleness book g 151,931 22,378 94ms 31.2min 2.3d 102.5d 0 book_staleness book h 131,389 36,879 17ms 96ms 12.1h 84.0d 0 book_staleness last_trade_price c 46,664 43,158 10ms 41ms 223ms 5.0s 0 transport_latency_assumed last_trade_price e 59,848 629 42ms 117ms 823ms 5.0s 0 transport_latency_assumed last_trade_price f 59,936 184 53ms 137ms 1.1s 5.0s 0 transport_latency_assumed last_trade_price g 59,899 33 96ms 207ms 2.1s 7.4s 0 transport_latency_assumed last_trade_price h 59,862 16,023 18ms 58ms 282ms 7.3s 0 transport_latency_assumed market_resolved c 1,141 1,050 10ms 10.3min 15.3min 15.4min 0 transport_latency_assumed market_resolved e 924 23 37ms 189ms 59.0s 1.0min 0 transport_latency_assumed market_resolved f 924 not meas. 48ms 212ms 59.0s 1.0min 0 transport_latency_assumed market_resolved g 924 36 86ms 263ms 674ms 1.5s 0 transport_latency_assumed market_resolved h 924 277 13ms 79ms 58.9s 59.0s 0 transport_latency_assumed new_market c 418 271 68ms 6.1min 11.3min 11.3min 0 transport_latency_assumed new_market e 348 18 76ms 336ms 18.6s 1.2min 0 transport_latency_assumed new_market f 348 35 94ms 391ms 24.9s 1.1min 0 transport_latency_assumed new_market g 348 41 138ms 14.2s 27.6s 56.3s 0 transport_latency_assumed new_market h 348 167 42ms 255ms 40.4s 1.1min 0 transport_latency_assumed price_change c 76,972,789 72,258,006 5ms 12ms 83ms 4.6s 0 transport_latency_assumed price_change e 97,535,788 769,982 36ms 44ms 182ms 3.6s 0 transport_latency_assumed price_change f 97,552,564 138,537 47ms 57ms 203ms 4.0s 0 transport_latency_assumed price_change g 97,544,816 12,380 85ms 103ms 353ms 9.3s 0 transport_latency_assumed price_change h 97,481,059 24,495,561 13ms 21ms 102ms 7.3s 0 transport_latency_assumed tick_size_change c 2,764 2,693 5ms 8ms 26ms 166ms 0 transport_latency_assumed tick_size_change e 3,308 24 36ms 45ms 113ms 233ms 0 transport_latency_assumed tick_size_change f 3,308 not meas. 47ms 58ms 128ms 366ms 0 transport_latency_assumed tick_size_change g 3,296 not meas. 83ms 101ms 266ms 1.7s 0 transport_latency_assumed tick_size_change h 3,308 591 13ms 24ms 83ms 3.0s 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-09/10/2026-09-09T10.parquet sha256sum 2026-09-09T10.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.