Hour audit: 2026-09-16T01
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-16T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T01:00:00.000035204+00:00 · last event 2026-09-16T01:59:59.999966655+00:00
VOLUME 116,171,251 rows · 1,212,205,736 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 115,490,336 · e: 115,452,376 · f: 115,443,509 · h: 115,433,384 · g: 115,260,651 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 110,870,785 (95.44%) · e: 528,266 (0.45%) · f: 301,881 (0.26%) · h: 4,315,266 (3.71%) · g: 155,053 (0.13%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 8ac6ddc2ea730b7f27acf61afaa8363f8798dacc12d0c78341ecf502f475038e
the corpus checksum ledger names this file with the same digest
joined 116,175,091 to merged 116,171,251, minus 3,840 (minus 0.0033%)
boundary drops 3,840 · 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-16T02:59:52Z 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,648,338 140,311,767 0-48 cb53be08a05709c34e8dfbd5d3e68671c5743d52062b47a38079d790bd88bb56 book 1,018,780 73,556,306 49-52 fd5acb7bbb395733fd70b8926b2cbfab4e2e4908c0378edeccf4c3e42ee236cc last_trade_price 45,387 2,553,019 53-53 ea4247e9b953a729d91bc377335c5fa0f10c849027fe486c0d873da074de8d4d market_resolved 2,601 418,224 54-54 cbb78813e2baa2935ffb64921335c742d26da202d12785c359f64a901949f5a5 new_market 781 85,015 55-55 47ebcb0cdc86d1868e5167b5a246687ff3eeef1f04da01cb36d0da94f287a2f2 price_change 102,446,616 993,648,078 56-446 3a721aec01c7bb0bcb9425ad2ca09808d4bd1b0d3934073add1e8fb15e169eef tick_size_change 8,748 312,211 447-447 ea5ce58ca6bbd8669b180f913465440251090f28a6976564072437042e01a627 EVENT MIX count share price_change 102,446,616 88.19% best_bid_ask 12,648,338 10.89% book 1,018,780 0.88% last_trade_price 45,387 0.04% tick_size_change 8,748 <0.01% market_resolved 2,601 <0.01% new_market 781 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,648,648 12,648,338 310 111 FULL book 1,019,544 1,018,780 764 156,429 FULL last_trade_price 45,387 45,387 0 1 FULL market_resolved 2,601 2,601 0 1 FULL new_market 781 781 0 0 FULL price_change 102,449,382 102,446,616 2,766 134 FULL tick_size_change 8,748 8,748 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,645,559 12,192,405 4ms 9ms 67ms 2.9s 0 transport_latency_assumed best_bid_ask e 12,643,596 31,262 39ms 47ms 130ms 4.3s 0 transport_latency_assumed best_bid_ask f 12,643,856 10,935 45ms 56ms 152ms 3.1s 0 transport_latency_assumed best_bid_ask g 12,642,737 587 82ms 111ms 280ms 13.4s 0 transport_latency_assumed best_bid_ask h 12,642,854 413,149 17ms 28ms 92ms 7.3s 0 transport_latency_assumed book c 379,280 274,880 1.9min 8.9h 34.3d 109.1d 0 book_staleness book e 393,689 190,440 2.0min 8.7h 34.3d 109.1d 0 book_staleness book f 379,421 175,515 1.8min 8.2h 34.3d 109.1d 0 book_staleness book g 250,374 147,375 35.7s 1.5h 24.5d 109.1d 0 book_staleness book h 415,082 230,570 2.2min 9.0h 34.4d 109.1d 0 book_staleness last_trade_price c 45,217 42,757 10ms 45ms 199ms 5.0s 0 transport_latency_assumed last_trade_price e 45,197 285 47ms 101ms 513ms 5.0s 0 transport_latency_assumed last_trade_price f 45,235 131 52ms 111ms 417ms 5.0s 0 transport_latency_assumed last_trade_price g 45,160 16 95ms 208ms 2.1s 6.8s 0 transport_latency_assumed last_trade_price h 45,006 2,198 23ms 68ms 242ms 6.9s 0 transport_latency_assumed market_resolved c 2,554 2,501 5ms 9ms 55.7s 1.0min 0 transport_latency_assumed market_resolved e 2,554 3 106ms 183ms 333ms 768ms 0 transport_latency_assumed market_resolved f 2,553 2 113ms 193ms 366ms 1.7min 0 transport_latency_assumed market_resolved g 2,554 4 208ms 334ms 56.0s 1.0min 0 transport_latency_assumed market_resolved h 2,554 91 35ms 61ms 126ms 6.0s 0 transport_latency_assumed new_market c 548 366 58ms 33.2s 59.5s 2.2min 0 transport_latency_assumed new_market e 548 65 134ms 13.8s 49.0s 1.1min 0 transport_latency_assumed new_market f 548 62 156ms 31.3s 56.9s 1.8min 0 transport_latency_assumed new_market g 548 31 197ms 14.4s 58.1s 1.1min 0 transport_latency_assumed new_market h 548 257 65ms 17.6s 50.2s 1.1min 0 transport_latency_assumed price_change c 102,408,430 98,349,372 5ms 11ms 78ms 3.2s 0 transport_latency_assumed price_change e 102,358,044 306,202 39ms 51ms 198ms 5.1s 0 transport_latency_assumed price_change f 102,363,148 115,234 46ms 62ms 222ms 4.9s 0 transport_latency_assumed price_change g 102,310,530 7,036 83ms 121ms 392ms 13.4s 0 transport_latency_assumed price_change h 102,318,596 3,668,772 17ms 32ms 117ms 7.3s 0 transport_latency_assumed tick_size_change c 8,748 8,504 4ms 8ms 57ms 375ms 0 transport_latency_assumed tick_size_change e 8,748 9 39ms 66ms 491ms 714ms 0 transport_latency_assumed tick_size_change f 8,748 2 46ms 115ms 340ms 526ms 0 transport_latency_assumed tick_size_change g 8,748 4 82ms 102ms 289ms 606ms 0 transport_latency_assumed tick_size_change h 8,744 229 17ms 28ms 88ms 337ms 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-16/01/2026-09-16T01.parquet sha256sum 2026-09-16T01.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.