Hour audit: 2026-10-03T17
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-10-03T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T17:00:00.000285690+00:00 · last event 2026-10-03T17:59:59.999720585+00:00
VOLUME 144,088,679 rows · 1,687,048,509 bytes (1.57 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 141,090,395 · h: 141,018,247 · i: 134,945,531 · g: 121,696,326 · k: 113,436,066 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 129,050,089 (89.56%) · h: 2,896,079 (2.01%) · i: 2,321,034 (1.61%) · g: 941,048 (0.65%) · k: 8,880,429 (6.16%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 144,088,679 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 657566a19eda7137544330f215262a76b3c1d8af739e840b69b9922f87f4ad43
the corpus checksum ledger names this file with the same digest
joined 144,093,860 to merged 144,088,679, minus 5,181 (minus 0.0036%)
boundary drops 5,181 · 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-10-03T19:54:05Z as ghikm
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,516,994 153,508,050 0-47 20d250fc123d989b14775f2371c94cd0a96a05da4eb4362c5fe58951bab74672 book 3,094,424 125,545,039 48-59 3ce37a1a8f387ab9bd91aba5f4de46229256473326c740774fea6077f097500d last_trade_price 65,685 3,825,332 60-60 377f7775aa8186ada8445450d8479ad0ce5397beb2b33ccd81bebb2f55709f2c market_resolved 4,265 513,812 61-61 17f67e378660f21359ec53312cc6792ce4bfb8ecd50683307f631bed10335dfe new_market 4,351 366,353 62-62 a88db57683160007a2cf8b2bc375477b559e5569bb93a5a7727103e43f61c972 price_change 128,395,800 1,401,388,926 63-552 c319b91d41b1dfe4af333e4fc6548d0f923aa63a8253a523f9f4414b15196c86 tick_size_change 7,160 264,328 553-553 9d95a058402215d5fd07a0451647ad9a8454af547eca2b2ed21ff10667d1346a EVENT MIX count share price_change 128,395,800 89.11% best_bid_ask 12,516,994 8.69% book 3,094,424 2.15% last_trade_price 65,685 0.05% tick_size_change 7,160 <0.01% new_market 4,351 <0.01% market_resolved 4,265 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,517,210 12,516,994 216 6,310 FULL book 3,096,580 3,094,424 2,156 236,908 FULL last_trade_price 65,687 65,685 2 686 FULL market_resolved 4,279 4,265 14 589 FULL new_market 4,482 4,351 131 155 FULL price_change 128,398,462 128,395,800 2,662 4,795 FULL tick_size_change 7,160 7,160 0 477 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,685,232 2,241 81ms 133ms 745ms 24.8s 0 transport_latency_assumed best_bid_ask h 12,512,210 250,974 19ms 36ms 630ms 58.9s 0 transport_latency_assumed best_bid_ask i 11,903,094 175,024 21ms 36ms 286ms 45.0s 0 transport_latency_assumed best_bid_ask k 9,865,686 619,159 14ms 31ms 262ms 47.1s 0 transport_latency_assumed best_bid_ask m 12,514,578 11,469,596 5ms 17ms 169ms 12.1s 0 transport_latency_assumed book g 1,601,715 915,490 20.9min 1.7d 42.1d 126.8d 0 book_staleness book h 158,396 10,268 28ms 3.3min 13.4d 126.8d 0 book_staleness book i 991,778 277,027 14.4min 1.7d 42.2d 126.8d 0 book_staleness book k 2,460,506 1,759,091 33.5min 1.8d 42.2d 126.8d 0 book_staleness book m 171,993 132,548 10ms 39.7min 18.1d 108.3d 0 book_staleness last_trade_price g 55,493 6 89ms 579ms 10.0s 24.8s 0 transport_latency_assumed last_trade_price h 65,509 1,617 21ms 74ms 827ms 56.4s 0 transport_latency_assumed last_trade_price i 62,415 1,214 24ms 64ms 470ms 43.4s 0 transport_latency_assumed last_trade_price k 51,706 3,953 16ms 45ms 363ms 24.7s 0 transport_latency_assumed last_trade_price m 65,491 58,895 6ms 23ms 195ms 3.8s 0 transport_latency_assumed market_resolved g 3,150 399 96ms 9.3min 15.5min 16.3min 0 transport_latency_assumed market_resolved h 2,775 86 21ms 139ms 51.4s 54.8s 0 transport_latency_assumed market_resolved i 2,984 219 24ms 3.8min 8.7min 10.3min 0 transport_latency_assumed market_resolved k 3,407 966 25ms 11.2min 17.5min 21.5min 0 transport_latency_assumed market_resolved m 2,776 2,595 6ms 8.4s 48.1s 57.1s 0 transport_latency_assumed new_market g 2,488 372 417ms 5.2min 6.2min 11.2min 0 transport_latency_assumed new_market h 2,245 644 163ms 37.2s 1.8min 2.6min 0 transport_latency_assumed new_market i 2,395 741 167ms 1.2min 3.8min 4.0min 0 transport_latency_assumed new_market k 3,084 1,109 187ms 6.6min 7.6min 8.4min 0 transport_latency_assumed new_market m 2,245 1,485 76ms 32.0s 1.9min 2.7min 0 transport_latency_assumed price_change g 109,341,788 22,540 82ms 175ms 1.9s 24.8s 0 transport_latency_assumed price_change h 128,269,952 2,632,396 19ms 41ms 726ms 1.0min 0 transport_latency_assumed price_change i 121,975,985 1,866,714 22ms 41ms 372ms 45.3s 0 transport_latency_assumed price_change k 101,046,001 6,495,748 14ms 33ms 291ms 48.3s 0 transport_latency_assumed price_change m 128,326,152 117,378,402 5ms 18ms 182ms 12.7s 0 transport_latency_assumed tick_size_change g 6,460 not meas. 80ms 111ms 418ms 720ms 0 transport_latency_assumed tick_size_change h 7,160 94 19ms 31ms 322ms 5.0s 0 transport_latency_assumed tick_size_change i 6,880 95 22ms 31ms 354ms 6.1s 0 transport_latency_assumed tick_size_change k 5,676 403 14ms 26ms 79ms 309ms 0 transport_latency_assumed tick_size_change m 7,160 6,568 5ms 15ms 58ms 257ms 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-10-03/17/2026-10-03T17.parquet sha256sum 2026-10-03T17.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.