Hour audit: 2026-09-05T21
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-05T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T21:00:00.046544891+00:00 · last event 2026-09-05T21:59:59.999999362+00:00
VOLUME 118,485,690 rows · 1,242,484,495 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 117,655,938 · e: 117,631,042 · h: 117,594,863 · g: 116,943,378 · c: 108,909,300 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 738,329 (0.62%) · e: 3,970 (0.00%) · h: 9,997 (0.01%) · g: 116,940,422 (98.70%) · c: 792,972 (0.67%) (rows of the merged file that came from it; these partition it)
7 product-machine pairs publish no supplied count; the figures above still sum to the file's 118,485,690 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1917a2fdb037f752ae8d8af78b5167d31bc405f075632df2d5e48fe74d02dac1
the corpus checksum ledger names this file with the same digest
joined 118,489,095 to merged 118,485,690, minus 3,405 (minus 0.0029%)
boundary drops 3,405 · 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-06T01:28:36Z 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,396,147 118,570,087 0-39 c50190bd1c3aa8013069483d73878cd78ac28b28d608388de6e4d232250727f5 book 933,062 66,997,657 40-43 be62e7b919868e32528e59466a1a4aa8ea3e45966e19335fafed3c4931f28503 last_trade_price 62,859 3,590,375 44-44 87ff9231fb0cd854405e327caeeb4660b6366559b55c2614699d91f4f16440fa market_resolved 2,897 432,300 45-45 82af52dfa39ae43dfd516e39e534cf4d5ff693ce5331c3bfedff39ef6ae1d37e new_market 3,023 318,273 46-46 e1f38e3cabb2792c62bcbdf7866a00d651523e2b3ed83fdce38fc870241b249e price_change 107,082,598 1,051,042,639 47-455 65a4d1443ae5ebb68e8e11e571c3d22f803306d424b2fb6df70a276f18d7d5f8 tick_size_change 5,104 185,530 456-456 32fc877da0232998a1284b7a9e68fab93ada1b96c42d88c001e28a045d6e2891 EVENT MIX count share price_change 107,082,598 90.38% best_bid_ask 10,396,147 8.77% book 933,062 0.79% last_trade_price 62,859 0.05% tick_size_change 5,104 <0.01% new_market 3,023 <0.01% market_resolved 2,897 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,396,396 10,396,147 249 1,500 FULL book 933,524 933,062 462 184,248 FULL last_trade_price 62,859 62,859 0 260 FULL market_resolved 2,897 2,897 0 20 FULL new_market 3,023 3,023 0 0 FULL price_change 107,085,292 107,082,598 2,694 1,045 FULL tick_size_change 5,104 5,104 0 114 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,545,968 669 4ms 9ms 124ms 4.7s 0 transport_latency_assumed best_bid_ask e 10,393,090 297 40ms 52ms 225ms 2.9s 0 transport_latency_assumed best_bid_ask f 10,393,550 23,016 49ms 62ms 247ms 4.9s 0 transport_latency_assumed best_bid_ask g 10,371,144 10,370,904 83ms 172ms 1.3s 26.0s 0 transport_latency_assumed best_bid_ask h 10,394,623 1,261 18ms 34ms 289ms 51.1s 0 transport_latency_assumed book c 908,466 776,716 2.9min 9.4h 34.3d 99.0d 0 book_staleness book e 133,534 1,244 42ms 185ms 3.3s 49.4d 0 book_staleness book f 134,280 7,001 52ms 196ms 4.5s 80.4d 0 book_staleness book g 146,512 146,480 91ms 20.3s 7.8h 80.5d 0 book_staleness book h 134,005 1,621 22ms 85ms 3.5s 80.4d 0 book_staleness last_trade_price c 58,343 5 10ms 41ms 304ms 5.0s 0 transport_latency_assumed last_trade_price e 62,656 7 46ms 140ms 1.3s 5.0s 0 transport_latency_assumed last_trade_price f 62,835 2,515 55ms 145ms 1.3s 5.0s 0 transport_latency_assumed last_trade_price g 60,329 60,329 94ms 402ms 10.4s 26.0s 0 transport_latency_assumed last_trade_price h 62,826 3 23ms 73ms 630ms 9.1s 0 transport_latency_assumed market_resolved c 2,704 173 4ms 25ms 4.4min 4.9min 0 transport_latency_assumed market_resolved e 2,724 not meas. 42ms 175ms 548ms 57.4s 0 transport_latency_assumed market_resolved f 2,724 not meas. 51ms 163ms 530ms 59.7s 0 transport_latency_assumed market_resolved g 2,724 2,724 87ms 337ms 1.7s 1.0min 0 transport_latency_assumed market_resolved h 2,724 not meas. 19ms 65ms 750ms 1.0min 0 transport_latency_assumed new_market c 2,091 159 79ms 3.8min 4.3min 2.1h 0 transport_latency_assumed new_market e 2,067 68 152ms 20.3s 2.4min 1.8h 0 transport_latency_assumed new_market f 2,067 425 168ms 20.4s 2.4min 3.6min 0 transport_latency_assumed new_market g 2,067 2,067 272ms 18.1s 2.6min 55.5min 0 transport_latency_assumed new_market h 2,067 304 124ms 20.5s 2.6min 4.0h 0 transport_latency_assumed price_change c 98,387,080 15,250 4ms 10ms 126ms 5.2s 0 transport_latency_assumed price_change e 107,031,867 2,354 40ms 58ms 284ms 3.0s 0 transport_latency_assumed price_change f 107,055,378 705,372 49ms 69ms 305ms 5.0s 0 transport_latency_assumed price_change g 106,355,498 106,352,814 83ms 203ms 3.0s 26.0s 0 transport_latency_assumed price_change h 106,993,514 6,808 18ms 37ms 298ms 51.8s 0 transport_latency_assumed tick_size_change c 4,648 not meas. 4ms 9ms 79ms 423ms 0 transport_latency_assumed tick_size_change e 5,104 not meas. 40ms 46ms 170ms 379ms 0 transport_latency_assumed tick_size_change f 5,104 not meas. 49ms 64ms 208ms 580ms 0 transport_latency_assumed tick_size_change g 5,104 5,104 86ms 215ms 979ms 5.0s 0 transport_latency_assumed tick_size_change h 5,104 not meas. 18ms 29ms 163ms 4.4s 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/21/2026-09-05T21.parquet sha256sum 2026-09-05T21.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.