Hour audit: 2026-10-05T08
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-05T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T08:00:00.000041585+00:00 · last event 2026-10-05T08:59:59.999941445+00:00
VOLUME 110,764,538 rows · 1,232,528,247 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 110,695,063 · h: 110,620,076 · m: 110,600,260 · i: 110,553,542 · n: 110,473,352 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 53,701,243 (48.48%) · h: 790,222 (0.71%) · m: 55,621,982 (50.22%) · i: 589,319 (0.53%) · n: 61,772 (0.06%) (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 110,764,538 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a653ad85aa60c097e99aa8c338aabbe4d3a60b527b057b99972dc88f4273fa6e
the corpus checksum ledger names this file with the same digest
joined 110,766,090 to merged 110,764,538, minus 1,552 (minus 0.0014%)
boundary drops 1,552 · 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-05T10:04:52Z 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 9,419,356 118,388,291 0-35 bd2d9498c9d51bcd61e2503d13e24b3ad7af88cb3bca7fc57242b152458f27a1 book 137,863 15,325,309 36-36 47c07e92ccf2dedbd5c6604856aec4fa7f4d896725efb823cd78f1deef88d5a0 last_trade_price 53,880 3,111,747 37-37 9e1fe9d57f096bbcb9b19df3c3cae69e8b3f96cdb7f423e9845918d4f158b647 market_resolved 705 117,145 38-38 c55ba0231acd58048f2909fdfd0438bbff0acb6300b98a968d85f909fa5cc01c new_market 2,058 192,423 39-39 4f0fd24f43b8e52698a57af5bfb422efc8f1849c3ad5220830b9932247928ff7 price_change 101,147,340 1,094,007,897 40-425 427c06a699e7ff0afde6f8aa7cbcb91a41d28f75d6ecb4860e97ea3fe0acc886 tick_size_change 3,336 123,385 426-426 f5ca933c8e9f3eb5abb20486c64aae91c41c0305890a8b113fd23064a54ceb15 EVENT MIX count share price_change 101,147,340 91.32% best_bid_ask 9,419,356 8.50% book 137,863 0.12% last_trade_price 53,880 0.05% tick_size_change 3,336 <0.01% new_market 2,058 <0.01% market_resolved 705 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,419,558 9,419,356 202 140 FULL book 137,875 137,863 12 11,298 FULL last_trade_price 53,882 53,880 2 1 FULL market_resolved 705 705 0 0 FULL new_market 2,058 2,058 0 0 FULL price_change 101,148,676 101,147,340 1,336 1,424 FULL tick_size_change 3,336 3,336 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,417,328 59,017 19ms 37ms 499ms 1.4min 0 transport_latency_assumed best_bid_ask i 9,417,642 49,377 21ms 33ms 160ms 15.7s 0 transport_latency_assumed best_bid_ask m 9,418,695 4,795,303 5ms 15ms 95ms 5.5s 0 transport_latency_assumed best_bid_ask n 9,415,269 3,503 46ms 68ms 323ms 24.6s 0 transport_latency_assumed best_bid_ask o 9,418,616 4,512,156 5ms 15ms 99ms 8.7s 0 transport_latency_assumed book h 122,894 14,201 28ms 9.9s 3.3d 109.9d 0 book_staleness book i 112,430 3,809 25ms 462ms 2.0h 109.9d 0 book_staleness book m 111,506 55,986 7ms 41ms 2.5min 109.8d 0 book_staleness book n 117,135 9,299 55ms 4.0s 21.0h 109.9d 0 book_staleness book o 111,490 54,568 7ms 34ms 1.5min 60.9d 0 book_staleness last_trade_price h 53,766 510 22ms 106ms 751ms 43.1s 0 transport_latency_assumed last_trade_price i 53,606 248 25ms 270ms 1.5s 15.7s 0 transport_latency_assumed last_trade_price m 53,803 27,057 6ms 25ms 224ms 2.6s 0 transport_latency_assumed last_trade_price n 53,149 26 53ms 811ms 7.4s 24.7s 0 transport_latency_assumed last_trade_price o 53,796 26,039 6ms 22ms 196ms 2.7s 0 transport_latency_assumed market_resolved h 705 3 22ms 124ms 42.4s 47.9s 0 transport_latency_assumed market_resolved i 705 44 23ms 120ms 31.4s 36.5s 0 transport_latency_assumed market_resolved m 705 346 6ms 22ms 34.1s 40.2s 0 transport_latency_assumed market_resolved n 705 not meas. 50ms 218ms 44.3s 49.5s 0 transport_latency_assumed market_resolved o 705 312 6ms 22ms 41.4s 47.1s 0 transport_latency_assumed new_market h 1,222 226 416ms 55.6s 1.1min 1.7min 0 transport_latency_assumed new_market i 1,222 326 216ms 55.9s 1.2min 1.2min 0 transport_latency_assumed new_market m 1,222 588 172ms 54.7s 1.1min 1.6min 0 transport_latency_assumed new_market n 1,222 424 347ms 56.8s 1.1min 1.7min 0 transport_latency_assumed new_market o 1,222 494 171ms 56.9s 1.1min 1.8min 0 transport_latency_assumed price_change h 101,020,825 716,210 20ms 46ms 605ms 1.4min 0 transport_latency_assumed price_change i 100,964,601 535,464 22ms 44ms 543ms 15.7s 0 transport_latency_assumed price_change m 101,010,993 50,741,111 5ms 17ms 116ms 10.9s 0 transport_latency_assumed price_change n 100,882,536 48,516 47ms 90ms 2.3s 24.7s 0 transport_latency_assumed price_change o 101,105,898 49,106,039 5ms 17ms 112ms 9.3s 0 transport_latency_assumed tick_size_change h 3,336 55 21ms 49ms 308ms 39.0s 0 transport_latency_assumed tick_size_change i 3,336 51 22ms 52ms 160ms 308ms 0 transport_latency_assumed tick_size_change m 3,336 1,591 6ms 29ms 164ms 304ms 0 transport_latency_assumed tick_size_change n 3,336 4 46ms 80ms 248ms 686ms 0 transport_latency_assumed tick_size_change o 3,336 1,635 6ms 29ms 180ms 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-10-05/08/2026-10-05T08.parquet sha256sum 2026-10-05T08.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.