Hour audit: 2026-09-14T03
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-14T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T03:00:00.000190223+00:00 · last event 2026-09-14T03:59:59.999990481+00:00
VOLUME 99,846,327 rows · 976,213,746 bytes (930.99 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 99,709,204 · f: 99,674,793 · g: 99,668,500 · e: 99,643,354 · h: 99,623,665 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 97,043,229 (97.19%) · f: 91,257 (0.09%) · g: 48,845 (0.05%) · e: 223,023 (0.22%) · h: 2,439,973 (2.44%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 99,846,327 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1be7a534fffb1a21ddc4e7b96938dff3a487120b59b66462388fcd72825f0be3
the corpus checksum ledger names this file with the same digest
joined 99,848,207 to merged 99,846,327, minus 1,880 (minus 0.0019%)
boundary drops 1,880 · 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-14T04:58:38Z 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 11,054,065 115,916,380 0-42 91bf13b317d7e2f689d7b8ddeba3aafefdfeba9d1ac254b69beeab3e7bb0af49 book 273,989 28,703,383 43-44 3d9e5d1604bfdad997ae95a94f532c9d974cdcdd2d33b376c6a47270b52f2cef last_trade_price 49,533 2,771,090 45-45 1cb010bf09ae55f381c2ab70fb06e87e938bef3d7559a68e26ca9516bddf6b4f market_resolved 1,340 220,045 46-46 80c973a36b541db55077cda2501a20122af83bbbee45e0169d3f2114a06a5dd9 new_market 472 57,162 47-47 f67119a28f9911340b013a37f16bbbb7ae33caadc06a9577081246e7028e235d price_change 88,464,620 827,319,662 48-385 c4c51883daa78cdb55b360cf35c36d1495ac3bd6fcec745986fba1f161fa9dab tick_size_change 2,308 85,209 386-386 b1bc4c8a2e8edc232b7571b57572f6dc38be2544a575cf6c4196455f38f659c6 EVENT MIX count share price_change 88,464,620 88.60% best_bid_ask 11,054,065 11.07% book 273,989 0.27% last_trade_price 49,533 0.05% tick_size_change 2,308 <0.01% market_resolved 1,340 <0.01% new_market 472 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,054,291 11,054,065 226 195 FULL book 273,997 273,989 8 76,542 FULL last_trade_price 49,533 49,533 0 0 FULL market_resolved 1,340 1,340 0 0 FULL new_market 472 472 0 0 FULL price_change 88,466,266 88,464,620 1,646 191 FULL tick_size_change 2,308 2,308 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,053,557 10,793,928 4ms 7ms 49ms 2.1s 0 transport_latency_assumed best_bid_ask e 11,051,646 15,584 41ms 44ms 94ms 3.9s 0 transport_latency_assumed best_bid_ask f 11,051,892 4,992 47ms 51ms 113ms 8.2s 0 transport_latency_assumed best_bid_ask g 11,049,227 244 81ms 96ms 193ms 13.9s 0 transport_latency_assumed best_bid_ask h 11,052,576 239,317 18ms 22ms 70ms 39.5s 0 transport_latency_assumed book c 153,627 143,394 7ms 6.6h 16.6d 107.2d 0 book_staleness book e 152,009 43,097 44ms 6.7h 19.4d 88.7d 0 book_staleness book f 140,409 31,149 51ms 3.8h 11.4d 107.2d 0 book_staleness book g 155,218 44,820 92ms 6.6h 17.4d 107.2d 0 book_staleness book h 112,183 11,529 21ms 89ms 1.4d 88.7d 0 book_staleness last_trade_price c 49,413 47,412 9ms 40ms 168ms 4.8s 0 transport_latency_assumed last_trade_price e 49,368 250 47ms 96ms 412ms 4.8s 0 transport_latency_assumed last_trade_price f 49,443 93 53ms 117ms 881ms 4.9s 0 transport_latency_assumed last_trade_price g 49,454 13 91ms 172ms 703ms 5.0s 0 transport_latency_assumed last_trade_price h 49,333 1,765 23ms 57ms 199ms 7.7s 0 transport_latency_assumed market_resolved c 1,340 1,315 4ms 8ms 54ms 453ms 0 transport_latency_assumed market_resolved e 1,340 2 42ms 123ms 350ms 457ms 0 transport_latency_assumed market_resolved f 1,340 1 48ms 131ms 346ms 1.1s 0 transport_latency_assumed market_resolved g 1,340 not meas. 89ms 251ms 581ms 1.1s 0 transport_latency_assumed market_resolved h 1,340 22 19ms 61ms 127ms 1.0s 0 transport_latency_assumed new_market c 373 292 24ms 191ms 15.5s 16.5s 0 transport_latency_assumed new_market e 373 22 59ms 10.6s 5.3min 3.4h 0 transport_latency_assumed new_market f 373 26 66ms 7.0s 19.3s 22.3min 0 transport_latency_assumed new_market g 373 28 84ms 401ms 15.1s 2.1min 0 transport_latency_assumed new_market h 373 104 35ms 293ms 16.8s 49.4min 0 transport_latency_assumed price_change c 88,448,586 86,054,680 5ms 8ms 58ms 4.4s 0 transport_latency_assumed price_change e 88,386,310 164,068 41ms 46ms 123ms 4.1s 0 transport_latency_assumed price_change f 88,429,028 54,996 47ms 54ms 143ms 8.7s 0 transport_latency_assumed price_change g 88,410,580 3,740 82ms 99ms 236ms 14.1s 0 transport_latency_assumed price_change h 88,405,552 2,187,136 18ms 24ms 84ms 40.8s 0 transport_latency_assumed tick_size_change c 2,308 2,208 5ms 8ms 76ms 181ms 0 transport_latency_assumed tick_size_change e 2,308 not meas. 41ms 44ms 82ms 133ms 0 transport_latency_assumed tick_size_change f 2,308 not meas. 47ms 51ms 92ms 255ms 0 transport_latency_assumed tick_size_change g 2,308 not meas. 81ms 95ms 123ms 569ms 0 transport_latency_assumed tick_size_change h 2,308 100 18ms 23ms 63ms 243ms 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/03/2026-09-14T03.parquet sha256sum 2026-09-14T03.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.