Hour audit: 2026-10-06T08
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-06T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T08:00:00.000006309+00:00 · last event 2026-10-06T08:59:59.999648801+00:00
VOLUME 112,283,038 rows · 1,323,966,896 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 111,038,550 · m: 111,016,496 · o: 110,990,535 · i: 110,962,920 · n: 106,909,490 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,142,572 (1.02%) · m: 59,155,798 (52.68%) · o: 50,517,045 (44.99%) · i: 884,461 (0.79%) · n: 583,162 (0.52%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 6346f9143e35147866a971be16f7bb734ae70958f1b5c2802afd6db45ca1f068
the corpus checksum ledger names this file with the same digest
joined 112,289,992 to merged 112,283,038, minus 6,954 (minus 0.0062%)
boundary drops 6,954 · 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-06T10:01:27Z 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 10,685,520 135,479,090 0-40 6f2a68fc5c4b8437042d73fc602447a2902d32b0daa675874a9c396e2ad8abc9 book 1,918,614 108,507,552 41-48 28c2c3336ddfcf97f0aed078e36b7448d0a07f7df6344043991ee2b322583749 last_trade_price 51,626 3,029,335 49-49 dea3ec5587390f3d38a6fc63cf37ec9ab0513464f0736a362293cbddabc7507b market_resolved 778 116,804 50-50 f7e0def576e117c91e8d49072bbad39f897cfb0d4949cf730aa2dc1013cd5f0d new_market 2,114 206,341 51-51 33663156de2e6cd8ff03ad22c08782087b092c3fe9520aa0a5a9167a0b22325a price_change 99,620,898 1,075,215,971 52-432 4597dfe50c80ab6f4bd2dafb02cbf935eb163235e9b0ef3676f5db905d680e7f tick_size_change 3,488 129,637 433-433 3c973580e1952950c3f91574e74d1cf19e5e0e0c5e4bd0c41cb6b77c7de8e849 EVENT MIX count share price_change 99,620,898 88.72% best_bid_ask 10,685,520 9.52% book 1,918,614 1.71% last_trade_price 51,626 0.05% tick_size_change 3,488 <0.01% new_market 2,114 <0.01% market_resolved 778 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,685,630 10,685,520 110 905 FULL book 1,924,408 1,918,614 5,794 98,857 FULL last_trade_price 51,626 51,626 0 105 FULL market_resolved 778 778 0 13 FULL new_market 2,114 2,114 0 0 FULL price_change 99,621,948 99,620,898 1,050 939 FULL tick_size_change 3,488 3,488 0 32 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,681,310 67,057 18ms 28ms 244ms 55.6s 0 transport_latency_assumed best_bid_ask i 10,681,815 56,699 21ms 30ms 140ms 7.9s 0 transport_latency_assumed best_bid_ask m 10,681,887 5,760,415 4ms 13ms 92ms 6.7s 0 transport_latency_assumed best_bid_ask n 10,242,905 2,876 43ms 58ms 285ms 12.8s 0 transport_latency_assumed best_bid_ask o 10,681,398 4,798,473 5ms 13ms 103ms 10.1s 0 transport_latency_assumed book h 774,000 358,662 18.4min 1.8d 44.8d 129.4d 0 book_staleness book i 665,888 267,825 16.0min 1.4d 44.8d 129.4d 0 book_staleness book m 714,488 378,298 16.6min 1.5d 44.8d 129.4d 0 book_staleness book n 1,075,487 549,464 28.3min 1.9d 44.8d 129.4d 0 book_staleness book o 714,590 364,365 16.1min 1.6d 44.8d 129.4d 0 book_staleness last_trade_price h 51,537 484 20ms 92ms 540ms 30.5s 0 transport_latency_assumed last_trade_price i 51,497 250 25ms 167ms 854ms 4.9s 0 transport_latency_assumed last_trade_price m 51,485 26,318 6ms 24ms 194ms 1.5s 0 transport_latency_assumed last_trade_price n 48,772 15 49ms 769ms 7.5s 11.8s 0 transport_latency_assumed last_trade_price o 51,441 24,559 6ms 22ms 180ms 1.9s 0 transport_latency_assumed market_resolved h 717 2 21ms 110ms 55.0s 55.0s 0 transport_latency_assumed market_resolved i 717 63 23ms 225ms 46.2s 56.6s 0 transport_latency_assumed market_resolved m 717 351 6ms 29ms 51.9s 52.0s 0 transport_latency_assumed market_resolved n 704 35 45ms 124ms 389ms 4.4s 0 transport_latency_assumed market_resolved o 717 327 6ms 19ms 56.5s 57.0s 0 transport_latency_assumed new_market h 1,331 283 236ms 23.2s 30.1s 1.8min 0 transport_latency_assumed new_market i 1,331 274 136ms 22.1s 28.2s 1.6min 0 transport_latency_assumed new_market m 1,331 766 70ms 22.1s 28.8s 1.5min 0 transport_latency_assumed new_market n 1,331 310 293ms 22.7s 28.7s 1.6min 0 transport_latency_assumed new_market o 1,331 481 145ms 20.9s 27.7s 1.4min 0 transport_latency_assumed price_change h 99,526,167 716,060 19ms 35ms 349ms 56.0s 0 transport_latency_assumed price_change i 99,558,184 559,302 21ms 39ms 413ms 7.9s 0 transport_latency_assumed price_change m 99,563,116 52,987,708 5ms 15ms 109ms 8.6s 0 transport_latency_assumed price_change n 95,536,915 30,458 44ms 86ms 1.9s 12.9s 0 transport_latency_assumed price_change o 99,537,570 45,327,370 5ms 15ms 118ms 11.5s 0 transport_latency_assumed tick_size_change h 3,488 24 18ms 40ms 588ms 6.2s 0 transport_latency_assumed tick_size_change i 3,488 48 22ms 50ms 316ms 451ms 0 transport_latency_assumed tick_size_change m 3,472 1,942 5ms 19ms 248ms 322ms 0 transport_latency_assumed tick_size_change n 3,376 4 45ms 123ms 610ms 2.1s 0 transport_latency_assumed tick_size_change o 3,488 1,470 5ms 25ms 344ms 464ms 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-06/08/2026-10-06T08.parquet sha256sum 2026-10-06T08.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.