Hour audit: 2026-10-04T10
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-04T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T10:00:00.000002117+00:00 · last event 2026-10-04T10:59:59.999942251+00:00
VOLUME 99,402,596 rows · 1,089,574,978 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 99,351,506 · i: 99,342,789 · o: 99,333,562 · h: 99,306,493 · n: 99,257,476 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 51,521,999 (51.83%) · i: 247,867 (0.25%) · o: 47,119,312 (47.40%) · h: 463,813 (0.47%) · n: 49,605 (0.05%) (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 99,402,596 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6c5146711bb6bbfe969e2efa90192043d2b7400cbb14d3f6b64ad9ef97fa474f
the corpus checksum ledger names this file with the same digest
joined 99,403,806 to merged 99,402,596, minus 1,210 (minus 0.0012%)
boundary drops 1,210 · 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-04T11:58:35Z as himno
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 8,362,465 104,177,969 0-31 b4bfe7f17a84bcafba67fdd85e1701b9cc2b278b0097727b731890d6e7952aff book 109,071 11,690,707 32-32 2c5a67eb19ef47c362e20870fcc9e05c0388387d7fe217f02ccb92ddba8e6ba4 last_trade_price 47,898 2,825,975 33-33 3e5d6b1911ef2f63eee22ccd3a9ee540098193fed6df8057838e825bc4aa82db market_resolved 888 132,061 34-34 e3ab38633076e14eb9ce6d25e57d6ebcf0a2fdee2874e7d7f64a2c01553b097b new_market 1,494 149,853 35-35 86582c53611250510f0f45b5589a89d2f1a810340670e1f2b9a864418e12b135 price_change 90,876,948 969,324,039 36-382 e219f71dfbb43d1abcac0dc1e4e9ea52ac3066febb570196243a4ac4e74218f2 tick_size_change 3,832 139,354 383-383 55f88aadedd99648990adfcbd5dd452f60cf8fcd243fbce6700e96727e7a759a EVENT MIX count share price_change 90,876,948 91.42% best_bid_ask 8,362,465 8.41% book 109,071 0.11% last_trade_price 47,898 0.05% tick_size_change 3,832 <0.01% new_market 1,494 <0.01% market_resolved 888 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,362,577 8,362,465 112 79 FULL book 109,071 109,071 0 5,121 FULL last_trade_price 47,898 47,898 0 0 FULL market_resolved 888 888 0 0 FULL new_market 1,494 1,494 0 0 FULL price_change 90,878,046 90,876,948 1,098 697 FULL tick_size_change 3,832 3,832 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 8,361,400 29,702 18ms 24ms 174ms 55.3s 0 transport_latency_assumed best_bid_ask i 8,361,617 15,332 22ms 27ms 124ms 6.7s 0 transport_latency_assumed best_bid_ask m 8,362,018 4,388,422 5ms 10ms 70ms 7.4s 0 transport_latency_assumed best_bid_ask n 8,360,624 2,392 45ms 55ms 213ms 26.5s 0 transport_latency_assumed best_bid_ask o 8,362,167 3,926,617 5ms 10ms 67ms 9.8s 0 transport_latency_assumed book h 101,356 5,113 22ms 80ms 2.2h 109.0d 0 book_staleness book i 98,157 1,235 24ms 73ms 4.8s 109.0d 0 book_staleness book m 98,484 49,509 7ms 22ms 32.5s 108.8d 0 book_staleness book n 101,060 4,317 49ms 268ms 2.1h 108.9d 0 book_staleness book o 98,932 48,897 7ms 20ms 4.3min 127.5d 0 book_staleness last_trade_price h 47,720 330 20ms 36ms 402ms 30.3s 0 transport_latency_assumed last_trade_price i 47,768 124 23ms 55ms 529ms 4.0s 0 transport_latency_assumed last_trade_price m 47,821 23,592 6ms 16ms 180ms 1.6s 0 transport_latency_assumed last_trade_price n 47,643 73 49ms 132ms 1.7s 26.5s 0 transport_latency_assumed last_trade_price o 47,840 23,779 6ms 14ms 163ms 1.2s 0 transport_latency_assumed market_resolved h 822 61 20ms 28.5s 44.5s 46.3s 0 transport_latency_assumed market_resolved i 822 6 24ms 31.9s 54.6s 54.6s 0 transport_latency_assumed market_resolved m 822 364 6ms 28.8s 54.4s 56.8s 0 transport_latency_assumed market_resolved n 822 not meas. 48ms 31.0s 51.8s 56.6s 0 transport_latency_assumed market_resolved o 822 457 6ms 27.4s 53.1s 56.3s 0 transport_latency_assumed new_market h 967 229 230ms 29.3s 1.3min 1.7min 0 transport_latency_assumed new_market i 967 82 149ms 24.4s 1.4min 1.7min 0 transport_latency_assumed new_market m 967 627 64ms 24.0s 1.3min 1.7min 0 transport_latency_assumed new_market n 967 99 254ms 25.8s 1.3min 1.7min 0 transport_latency_assumed new_market o 967 457 87ms 26.2s 1.2min 1.5min 0 transport_latency_assumed price_change h 90,790,396 428,370 19ms 27ms 322ms 55.6s 0 transport_latency_assumed price_change i 90,829,626 231,088 22ms 31ms 309ms 7.4s 0 transport_latency_assumed price_change m 90,837,562 47,057,490 5ms 11ms 111ms 7.9s 0 transport_latency_assumed price_change n 90,742,528 42,724 46ms 63ms 498ms 26.5s 0 transport_latency_assumed price_change o 90,819,002 43,117,276 5ms 11ms 111ms 9.8s 0 transport_latency_assumed tick_size_change h 3,832 8 18ms 22ms 41ms 62ms 0 transport_latency_assumed tick_size_change i 3,832 not meas. 22ms 26ms 48ms 92ms 0 transport_latency_assumed tick_size_change m 3,832 1,995 5ms 8ms 24ms 141ms 0 transport_latency_assumed tick_size_change n 3,832 not meas. 45ms 52ms 70ms 126ms 0 transport_latency_assumed tick_size_change o 3,832 1,829 5ms 9ms 29ms 59ms 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-04/10/2026-10-04T10.parquet sha256sum 2026-10-04T10.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.