Hour audit: 2026-09-18T01
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-18T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T01:00:00.000102833+00:00 · last event 2026-09-18T01:59:59.999974632+00:00
VOLUME 122,092,349 rows · 1,305,258,631 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 120,945,429 · e: 120,913,221 · g: 116,461,711 · c: 116,154,954 · f: 111,143,184 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 10,534,672 (8.63%) · e: 987,945 (0.81%) · g: 231,944 (0.19%) · c: 109,412,142 (89.61%) · f: 925,646 (0.76%) (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 122,092,349 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 98a20951cdd3741839f9c093dac6bc2d1263e45bc0db35ca2f030b5565790e0a
the corpus checksum ledger names this file with the same digest
joined 122,095,916 to merged 122,092,349, minus 3,567 (minus 0.0029%)
boundary drops 3,567 · 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-18T03:02:08Z 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,422,413 128,965,907 0-43 22e35a5f8f6da43babdc2ac8c0316a3fa885b288d426342b8da020482adc2374 book 1,124,250 76,171,514 44-48 89103038e702b271ca250b43ad233806c468194e22027067fbcfdaa695175c12 last_trade_price 57,703 3,199,708 49-49 69df47645feb509413d61cb6c7eb0e022f7fd999a910eb99c41057206389fe4c market_resolved 825 123,901 50-50 ef48ef3e458caf20dfdae70ace13df224ecef863049783a8d15d48988b6fd7b1 new_market 448 50,634 51-51 81a2e96800751583200d2017e3e089725d3a1d8b453226c137611c0610501e37 price_change 109,483,438 1,095,237,357 52-469 f563d4f2e8b9ef86463188879db5fea8582fd2df40a6659e7501713a182864f8 tick_size_change 3,272 120,436 470-470 782f43ffa6204a3a7a0dee35596d840b50c073ea6d59deec6907b531dabaffaf EVENT MIX count share price_change 109,483,438 89.67% best_bid_ask 11,422,413 9.36% book 1,124,250 0.92% last_trade_price 57,703 0.05% tick_size_change 3,272 <0.01% market_resolved 825 <0.01% new_market 448 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,422,797 11,422,413 384 1,304 FULL book 1,124,326 1,124,250 76 187,655 FULL last_trade_price 57,704 57,703 1 251 FULL market_resolved 825 825 0 66 FULL new_market 448 448 0 37 FULL price_change 109,486,544 109,483,438 3,106 777 FULL tick_size_change 3,272 3,272 0 78 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,911,561 10,357,465 5ms 13ms 84ms 2.7s 0 transport_latency_assumed best_bid_ask e 11,418,643 81,720 41ms 51ms 128ms 4.7s 0 transport_latency_assumed best_bid_ask f 10,423,131 17,678 48ms 59ms 140ms 3.2s 0 transport_latency_assumed best_bid_ask g 10,935,011 1,614 83ms 102ms 210ms 4.3s 0 transport_latency_assumed best_bid_ask h 11,418,734 963,936 18ms 37ms 100ms 8.1s 0 transport_latency_assumed book c 499,159 220,457 2.2min 5.7h 33.5d 111.1d 0 book_staleness book e 126,293 8,205 44ms 161ms 47.7min 92.5d 0 book_staleness book f 873,584 670,291 3.4min 7.5h 37.3d 111.1d 0 book_staleness book g 497,053 206,809 2.2min 5.5h 33.5d 111.1d 0 book_staleness book h 126,457 18,488 21ms 107ms 31.6min 92.6d 0 book_staleness last_trade_price c 55,047 50,805 10ms 53ms 287ms 4.9s 0 transport_latency_assumed last_trade_price e 57,142 803 48ms 107ms 435ms 5.0s 0 transport_latency_assumed last_trade_price f 52,807 305 55ms 114ms 473ms 5.6s 0 transport_latency_assumed last_trade_price g 54,720 53 93ms 186ms 627ms 5.0s 0 transport_latency_assumed last_trade_price h 57,213 5,737 24ms 76ms 293ms 5.1s 0 transport_latency_assumed market_resolved c 761 734 5ms 13ms 5.2min 5.7min 0 transport_latency_assumed market_resolved e 762 1 44ms 122ms 355ms 500ms 0 transport_latency_assumed market_resolved f 705 2 51ms 132ms 344ms 2.5min 0 transport_latency_assumed market_resolved g 807 52 96ms 349ms 6.2min 7.5min 0 transport_latency_assumed market_resolved h 766 36 25ms 57ms 138ms 542ms 0 transport_latency_assumed new_market c 285 186 35ms 12.7s 17.8s 20.3s 0 transport_latency_assumed new_market e 285 56 75ms 14.8s 26.9s 1.4min 0 transport_latency_assumed new_market f 285 44 65ms 221ms 16.2s 4.0min 0 transport_latency_assumed new_market g 330 68 112ms 1.6h 1.6h 2.0h 0 transport_latency_assumed new_market h 285 94 46ms 13.0s 56.4s 1.3min 0 transport_latency_assumed price_change c 104,685,005 98,779,443 5ms 16ms 101ms 2.8s 0 transport_latency_assumed price_change e 109,306,824 897,160 41ms 56ms 169ms 5.0s 0 transport_latency_assumed price_change f 99,789,516 237,326 48ms 63ms 179ms 4.8s 0 transport_latency_assumed price_change g 104,970,638 23,348 83ms 104ms 272ms 8.4s 0 transport_latency_assumed price_change h 109,338,702 9,546,161 18ms 41ms 124ms 8.6s 0 transport_latency_assumed tick_size_change c 3,136 3,052 5ms 7ms 36ms 86ms 0 transport_latency_assumed tick_size_change e 3,272 not meas. 41ms 46ms 198ms 281ms 0 transport_latency_assumed tick_size_change f 3,156 not meas. 48ms 52ms 77ms 129ms 0 transport_latency_assumed tick_size_change g 3,152 not meas. 82ms 96ms 113ms 149ms 0 transport_latency_assumed tick_size_change h 3,272 220 18ms 23ms 147ms 233ms 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-18/01/2026-09-18T01.parquet sha256sum 2026-09-18T01.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.