Hour audit: 2026-09-14T12
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-14T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T12:00:00.000014297+00:00 · last event 2026-09-14T12:59:59.998494125+00:00
VOLUME 106,655,142 rows · 1,064,997,927 bytes (1015.66 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 106,606,979 · h: 106,539,724 · e: 106,534,991 · f: 106,528,585 · g: 106,462,578 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 102,127,019 (95.75%) · h: 4,105,947 (3.85%) · e: 259,410 (0.24%) · f: 122,358 (0.11%) · g: 40,408 (0.04%) (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 106,655,142 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 46f86140cc16ccfbc3891edcbef452fef6b3756b8ceecf2797a895618f101bba
the corpus checksum ledger names this file with the same digest
joined 106,657,250 to merged 106,655,142, minus 2,108 (minus 0.0020%)
boundary drops 2,108 · 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-14T14:35:07Z 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,917,634 118,352,651 0-41 dd1d402a01b83a88a4d0a2c610b61440d502ca4efc42289ef389cb9974565e2c book 154,953 16,681,422 42-42 8bfb28f02dd6f3329a7591ebef01d59dbc1120ce61a4829cf243f6c7580b85d5 last_trade_price 57,791 3,288,025 43-43 fb68519072971d5046986b61b3d38b898df5667499fca3267ef41e556a768ebf market_resolved 870 135,447 44-44 aecc4c5530594742f9082742f584f9f045927435bec1b47ace0d20111db9bbfd new_market 782 86,988 45-45 370e9e9b5f9a25ed0b9138fa0fd0fdfda6017564575e2ba82bb5992fe45cb640 price_change 95,520,468 925,141,066 46-410 8bd87a3d973207ab44b2e14ef96c7cc1691c8252adda59993ae97195a7913a87 tick_size_change 2,644 96,965 411-411 b56e74b146e8560c682790c113ba03bc561198b2ae5db35707f321caf00ae513 EVENT MIX count share price_change 95,520,468 89.56% best_bid_ask 10,917,634 10.24% book 154,953 0.15% last_trade_price 57,791 0.05% tick_size_change 2,644 <0.01% market_resolved 870 <0.01% new_market 782 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,917,882 10,917,634 248 144 FULL book 154,955 154,953 2 14,974 FULL last_trade_price 57,793 57,791 2 1 FULL market_resolved 870 870 0 0 FULL new_market 782 782 0 0 FULL price_change 95,522,324 95,520,468 1,856 302 FULL tick_size_change 2,644 2,644 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,917,056 10,490,687 5ms 11ms 84ms 9.3s 0 transport_latency_assumed best_bid_ask e 10,914,430 23,802 42ms 48ms 164ms 12.9s 0 transport_latency_assumed best_bid_ask f 10,914,552 9,906 48ms 56ms 175ms 18.4s 0 transport_latency_assumed best_bid_ask g 10,910,907 964 80ms 98ms 327ms 20.8s 0 transport_latency_assumed best_bid_ask h 10,916,554 392,275 18ms 26ms 104ms 6.3s 0 transport_latency_assumed book c 123,271 116,863 7ms 29ms 4.8h 89.1d 0 book_staleness book e 121,040 2,313 44ms 315ms 4.7min 89.1d 0 book_staleness book f 121,307 1,834 50ms 269ms 8.6min 88.9d 0 book_staleness book g 145,946 27,100 94ms 22.9min 7.1d 107.6d 0 book_staleness book h 121,194 6,843 22ms 66ms 3.2s 89.0d 0 book_staleness last_trade_price c 57,665 54,796 11ms 45ms 208ms 4.7s 0 transport_latency_assumed last_trade_price e 57,302 163 51ms 227ms 4.7s 12.9s 0 transport_latency_assumed last_trade_price f 57,297 109 57ms 205ms 3.8s 18.4s 0 transport_latency_assumed last_trade_price g 57,118 16 97ms 419ms 7.3s 20.7s 0 transport_latency_assumed last_trade_price h 57,687 2,707 24ms 77ms 347ms 5.7s 0 transport_latency_assumed market_resolved c 841 817 5ms 11ms 66ms 287ms 0 transport_latency_assumed market_resolved e 841 31 43ms 166ms 1.0min 2.3min 0 transport_latency_assumed market_resolved f 841 1 49ms 139ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 841 1 84ms 234ms 514ms 4.2s 0 transport_latency_assumed market_resolved h 841 20 19ms 75ms 1.0min 1.0min 0 transport_latency_assumed new_market c 562 368 74ms 17.4s 22.4s 1.3min 0 transport_latency_assumed new_market e 562 49 181ms 534ms 22.8s 1.4min 0 transport_latency_assumed new_market f 562 72 178ms 13.3s 22.6s 1.3min 0 transport_latency_assumed new_market g 562 65 273ms 13.6s 24.0s 1.1min 0 transport_latency_assumed new_market h 562 228 107ms 16.9s 24.6s 1.6min 0 transport_latency_assumed price_change c 95,504,940 91,460,968 5ms 12ms 101ms 9.3s 0 transport_latency_assumed price_change e 95,438,172 233,052 42ms 55ms 377ms 12.9s 0 transport_latency_assumed price_change f 95,431,382 110,436 48ms 64ms 367ms 18.4s 0 transport_latency_assumed price_change g 95,344,560 12,262 81ms 111ms 938ms 20.9s 0 transport_latency_assumed price_change h 95,440,242 3,703,750 18ms 29ms 143ms 6.3s 0 transport_latency_assumed tick_size_change c 2,644 2,520 5ms 10ms 55ms 141ms 0 transport_latency_assumed tick_size_change e 2,644 not meas. 42ms 46ms 118ms 732ms 0 transport_latency_assumed tick_size_change f 2,644 not meas. 48ms 56ms 112ms 162ms 0 transport_latency_assumed tick_size_change g 2,644 not meas. 80ms 98ms 156ms 301ms 0 transport_latency_assumed tick_size_change h 2,644 124 18ms 24ms 64ms 1.4s 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/12/2026-09-14T12.parquet sha256sum 2026-09-14T12.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.