Hour audit: 2026-09-16T00
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-16T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T00:00:00.000162479+00:00 · last event 2026-09-16T00:59:59.999918212+00:00
VOLUME 115,003,325 rows · 1,196,762,310 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 114,636,193 · g: 114,594,759 · e: 114,483,729 · f: 114,461,467 · h: 114,395,280 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 109,345,811 (95.08%) · g: 303,893 (0.26%) · e: 391,092 (0.34%) · f: 165,043 (0.14%) · h: 4,797,486 (4.17%) (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 115,003,325 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 22df210d8cf2c1edb9325927ae1126cda1d3efe9310c26556c9e6db222f491ff
the corpus checksum ledger names this file with the same digest
joined 115,006,262 to merged 115,003,325, minus 2,937 (minus 0.0026%)
boundary drops 2,937 · 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:03:19Z 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,674,869 142,855,002 0-48 4cb684734e6abc3ae5d34d0c7b1570dda67c78590ed5ade59f3e676bc2e2c6cb book 536,862 49,775,667 49-51 cc3c1a6cbf3f9a85d629e207bfeae4f885d4221c0aa4d267f7ef494ac446a1b2 last_trade_price 52,468 2,974,718 52-52 8c7124c5f3ed90afb3285537abec9e795ab532cf1cfcbb768afde0d08b51f2fd market_resolved 624 103,510 53-53 b8180c0480fc7c054aaa29baa3eaf88b14b30c1951212466c93cca39cccb3f6c new_market 514 60,446 54-54 8aa2ef92f62dfaa1f92ab0ebf94c331bfee83ee2622763fb3fe09c53bcba7816 price_change 101,734,148 999,542,253 55-443 ce41784ac5f0770cb5c99f58bed729b5bb4ec8e149a163f1bde630912427fe67 tick_size_change 3,840 138,512 444-444 e1d1375b9e2ad0a384f913fa567a9eaa6ecafd9cc279b558acaa6cf64df14d7e EVENT MIX count share price_change 101,734,148 88.46% best_bid_ask 12,674,869 11.02% book 536,862 0.47% last_trade_price 52,468 0.05% tick_size_change 3,840 <0.01% market_resolved 624 <0.01% new_market 514 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,675,139 12,674,869 270 151 FULL book 536,960 536,862 98 146,746 FULL last_trade_price 52,469 52,468 1 0 FULL market_resolved 624 624 0 0 FULL new_market 514 514 0 0 FULL price_change 101,736,716 101,734,148 2,568 138 FULL tick_size_change 3,840 3,840 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,672,217 12,163,441 5ms 10ms 74ms 2.6s 0 transport_latency_assumed best_bid_ask e 12,672,781 33,144 40ms 49ms 146ms 5.3s 0 transport_latency_assumed best_bid_ask f 12,672,312 12,486 45ms 58ms 160ms 5.7s 0 transport_latency_assumed best_bid_ask g 12,666,823 1,281 82ms 99ms 250ms 9.7s 0 transport_latency_assumed best_bid_ask h 12,669,423 464,517 18ms 27ms 99ms 7.6s 0 transport_latency_assumed book c 235,740 223,385 5.4s 35.3min 24.4d 109.1d 0 book_staleness book e 115,147 6,940 43ms 314ms 37.4min 90.5d 0 book_staleness book f 116,426 7,078 48ms 387ms 9.2h 90.6d 0 book_staleness book g 416,891 280,997 1.8min 7.4h 31.5d 109.1d 0 book_staleness book h 120,229 18,462 21ms 2.3s 42.9min 90.6d 0 book_staleness last_trade_price c 52,176 49,043 10ms 46ms 210ms 4.9s 0 transport_latency_assumed last_trade_price e 52,237 322 49ms 154ms 978ms 4.9s 0 transport_latency_assumed last_trade_price f 52,099 87 54ms 153ms 804ms 4.9s 0 transport_latency_assumed last_trade_price g 51,945 40 94ms 234ms 1.5s 6.3s 0 transport_latency_assumed last_trade_price h 51,848 2,976 23ms 70ms 258ms 4.9s 0 transport_latency_assumed market_resolved c 620 565 5ms 32ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 620 4 42ms 216ms 53.3s 55.7s 0 transport_latency_assumed market_resolved f 620 1 47ms 212ms 53.3s 55.7s 0 transport_latency_assumed market_resolved g 620 not meas. 88ms 359ms 56.9s 59.6s 0 transport_latency_assumed market_resolved h 620 54 19ms 79ms 51.6s 54.0s 0 transport_latency_assumed new_market c 388 278 40ms 283ms 19.3s 1.6min 0 transport_latency_assumed new_market e 388 30 128ms 557ms 26.6s 1.3min 0 transport_latency_assumed new_market f 388 25 126ms 326ms 20.2s 57.9s 0 transport_latency_assumed new_market g 388 47 105ms 12.2s 1.1min 1.7min 0 transport_latency_assumed new_market h 388 134 54ms 12.7s 20.3s 1.3min 0 transport_latency_assumed price_change c 101,671,212 96,905,358 5ms 13ms 102ms 2.7s 0 transport_latency_assumed price_change e 101,638,716 350,646 41ms 59ms 290ms 8.3s 0 transport_latency_assumed price_change f 101,615,782 145,366 45ms 68ms 281ms 7.8s 0 transport_latency_assumed price_change g 101,454,252 21,528 82ms 110ms 387ms 10.4s 0 transport_latency_assumed price_change h 101,548,932 4,311,250 18ms 32ms 139ms 7.6s 0 transport_latency_assumed tick_size_change c 3,840 3,741 5ms 8ms 50ms 83ms 0 transport_latency_assumed tick_size_change e 3,840 6 41ms 49ms 113ms 254ms 0 transport_latency_assumed tick_size_change f 3,840 not meas. 45ms 56ms 139ms 422ms 0 transport_latency_assumed tick_size_change g 3,840 not meas. 82ms 97ms 209ms 463ms 0 transport_latency_assumed tick_size_change h 3,840 93 18ms 30ms 83ms 2.5s 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/00/2026-09-16T00.parquet sha256sum 2026-09-16T00.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.