Hour audit: 2026-09-14T11
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-14T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T11:00:00.000014481+00:00 · last event 2026-09-14T11:59:59.999887424+00:00
VOLUME 103,585,247 rows · 1,052,060,861 bytes (1003.32 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 103,218,966 · g: 103,192,413 · e: 103,182,631 · h: 103,162,664 · c: 99,490,132 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 109,214 (0.11%) · g: 25,888 (0.02%) · e: 305,711 (0.30%) · h: 7,075,864 (6.83%) · c: 96,068,570 (92.74%) (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 103,585,247 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a52f2c844b774396fcb85b2e6397cb71059545dbce7ea98e3c3cfd0dd7eeb7a7
the corpus checksum ledger names this file with the same digest
joined 103,589,565 to merged 103,585,247, minus 4,318 (minus 0.0042%)
boundary drops 4,318 · 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-14T12:58:33Z 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,479,463 112,747,383 0-39 e93b96ca058d4b64062d4040b0878c23375db731032d93639d90d5e562847a83 book 443,066 49,151,085 40-41 d250fa93b192d2e8e81c668e816bcfdb89cd846b59b026f73b0391eb1bbee196 last_trade_price 47,287 2,756,534 42-42 9e795fbc609b72fd5e2c09b2714bed08dd3393ca76b13f0f063f483fd3dbe1b4 market_resolved 686 100,665 43-43 bb032a57f9897f911d023cd97ec2f11399830f866e362c2cafdc86c2c9811087 new_market 739 81,155 44-44 890e8bf789589cb0ee62a31fc7bae3ac78b937a5d4e6f85c099e710f3de5441f price_change 92,611,822 885,963,173 45-398 359ee4c5859f4cb03315f87739d4e4e4f89056a121d1de2b350f077bcbc0fc04 tick_size_change 2,184 80,846 399-399 35661346ae0d3856257b0becff23ad9fd8aebffecac4486f173ab381f7ad1909 EVENT MIX count share price_change 92,611,822 89.41% best_bid_ask 10,479,463 10.12% book 443,066 0.43% last_trade_price 47,287 0.05% tick_size_change 2,184 <0.01% new_market 739 <0.01% market_resolved 686 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,479,745 10,479,463 282 546 FULL book 445,080 443,066 2,014 163,005 FULL last_trade_price 47,287 47,287 0 58 FULL market_resolved 686 686 0 0 FULL new_market 739 739 0 0 FULL price_change 92,613,844 92,611,822 2,022 364 FULL tick_size_change 2,184 2,184 0 13 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,055,763 9,723,546 5ms 9ms 71ms 2.8s 0 transport_latency_assumed best_bid_ask e 10,477,618 29,217 41ms 45ms 135ms 4.1s 0 transport_latency_assumed best_bid_ask f 10,478,328 8,824 48ms 52ms 149ms 4.8s 0 transport_latency_assumed best_bid_ask g 10,475,415 831 80ms 95ms 264ms 10.7s 0 transport_latency_assumed best_bid_ask h 10,478,336 717,045 18ms 23ms 93ms 42.8s 0 transport_latency_assumed book c 429,416 418,459 4.6min 1.7d 33.7d 107.5d 0 book_staleness book e 99,274 1,489 43ms 167ms 1.7min 88.9d 0 book_staleness book f 100,284 1,708 50ms 213ms 1.5h 107.5d 0 book_staleness book g 120,877 13,666 91ms 39.9min 7.0d 89.0d 0 book_staleness book h 100,080 7,744 22ms 71ms 41.3min 88.9d 0 book_staleness last_trade_price c 45,891 43,977 10ms 44ms 224ms 4.9s 0 transport_latency_assumed last_trade_price e 47,054 172 48ms 155ms 971ms 5.0s 0 transport_latency_assumed last_trade_price f 47,249 123 55ms 173ms 1.4s 5.0s 0 transport_latency_assumed last_trade_price g 47,072 36 94ms 224ms 1.8s 6.5s 0 transport_latency_assumed last_trade_price h 47,129 2,979 24ms 76ms 408ms 7.2s 0 transport_latency_assumed market_resolved c 623 587 5ms 97ms 5.2min 5.2min 0 transport_latency_assumed market_resolved e 606 38 42ms 276ms 53.1s 53.9s 0 transport_latency_assumed market_resolved f 606 12 49ms 278ms 53.1s 54.0s 0 transport_latency_assumed market_resolved g 606 29 84ms 245ms 609ms 1.0min 0 transport_latency_assumed market_resolved h 606 20 19ms 113ms 53.6s 54.4s 0 transport_latency_assumed new_market c 517 383 67ms 16.2s 25.8s 1.3min 0 transport_latency_assumed new_market e 517 73 185ms 16.0s 23.6s 54.5s 0 transport_latency_assumed new_market f 517 65 167ms 15.1s 24.8s 1.2min 0 transport_latency_assumed new_market g 517 46 292ms 15.1s 26.9s 56.6s 0 transport_latency_assumed new_market h 517 172 134ms 15.5s 27.7s 1.2min 0 transport_latency_assumed price_change c 88,955,786 85,879,538 5ms 10ms 81ms 3.4s 0 transport_latency_assumed price_change e 92,555,378 274,722 41ms 48ms 210ms 4.4s 0 transport_latency_assumed price_change f 92,589,798 98,482 48ms 56ms 236ms 5.5s 0 transport_latency_assumed price_change g 92,545,742 11,280 80ms 100ms 366ms 12.6s 0 transport_latency_assumed price_change h 92,533,816 6,347,800 18ms 25ms 129ms 43.4s 0 transport_latency_assumed tick_size_change c 2,136 2,080 5ms 8ms 35ms 182ms 0 transport_latency_assumed tick_size_change e 2,184 not meas. 41ms 44ms 110ms 124ms 0 transport_latency_assumed tick_size_change f 2,184 not meas. 48ms 51ms 85ms 116ms 0 transport_latency_assumed tick_size_change g 2,184 not meas. 79ms 93ms 138ms 258ms 0 transport_latency_assumed tick_size_change h 2,180 104 18ms 22ms 42ms 109ms 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-14/11/2026-09-14T11.parquet sha256sum 2026-09-14T11.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.