Hour audit: 2026-10-08T18
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-08T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T18:00:00.000088702+00:00 · last event 2026-10-08T18:59:59.999975650+00:00
VOLUME 125,528,418 rows · 1,451,325,521 bytes (1.35 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 125,335,869 · m: 125,288,548 · h: 124,993,159 · i: 124,685,567 · n: 124,562,506 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 57,750,865 (46.01%) · m: 64,685,267 (51.53%) · h: 1,166,214 (0.93%) · i: 1,757,695 (1.40%) · n: 168,377 (0.13%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 61556bd8ad71eb572c61bfa55855f7560899f2f865d6e55e0ef27527a8fe3283
the corpus checksum ledger names this file with the same digest
joined 125,549,841 to merged 125,528,418, minus 21,423 (minus 0.0171%)
boundary drops 21,423 · 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-08T20:06:17Z 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 12,671,886 161,676,827 0-48 336013827c86080e66846b07598dc50372868e950e7ab91d4b847abba77c4861 book 166,697 18,066,563 49-49 0236a83c094d8531e09905c3707a21ce58ba9a7f0b76d35dc5dc578058aa6fef last_trade_price 56,989 3,295,246 50-50 3e67e2caedbc326ad1991dcd218f96881c8a5864b0a9ddffb0075f804afb1820 market_resolved 684 110,322 51-51 eeb92afb510b34fb4db3b8e4c928184f41844fb7aa2fe40ec3ed98dfc8653bb6 new_market 5,652 518,268 52-52 2d4e0777bdc735685664e484bc5532e634c47757b51664bba56ff8a020141844 price_change 112,623,972 1,266,135,574 53-482 08bcd06efcdab4675fb449f9ec27f2333895ee18e19e9867813c8da8e6ae36b0 tick_size_change 2,538 93,749 483-483 cef0cbd73f58f1ca825f329c157c68d514e826b145ffabca868e1e4c1095aa0c EVENT MIX count share price_change 112,623,972 89.72% best_bid_ask 12,671,886 10.09% book 166,697 0.13% last_trade_price 56,989 0.05% new_market 5,652 <0.01% tick_size_change 2,538 <0.01% market_resolved 684 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,672,973 12,671,886 1,087 676 FULL book 166,721 166,697 24 14,905 FULL last_trade_price 56,993 56,989 4 2 FULL market_resolved 684 684 0 0 FULL new_market 5,652 5,652 0 8 FULL price_change 112,644,280 112,623,972 20,308 252 FULL tick_size_change 2,538 2,538 0 6 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,656,611 110,546 21ms 112ms 1.2s 1.4min 0 transport_latency_assumed best_bid_ask i 12,651,521 178,537 22ms 43ms 270ms 18.0s 0 transport_latency_assumed best_bid_ask m 12,664,383 6,506,950 6ms 23ms 212ms 7.2s 0 transport_latency_assumed best_bid_ask n 12,657,303 12,072 45ms 92ms 628ms 27.7s 0 transport_latency_assumed best_bid_ask o 12,665,527 5,863,781 6ms 25ms 268ms 12.9s 0 transport_latency_assumed book h 125,840 8,572 36ms 1.6s 10.2h 113.3d 0 book_staleness book i 130,144 14,795 36ms 6.1s 14.8h 113.4d 0 book_staleness book m 127,037 67,170 9ms 261ms 10.0h 131.8d 0 book_staleness book n 130,770 16,178 101ms 17.1s 14.8h 113.3d 0 book_staleness book o 124,570 59,982 9ms 181ms 3.3h 113.2d 0 book_staleness last_trade_price h 56,275 577 26ms 308ms 5.3s 56.3s 0 transport_latency_assumed last_trade_price i 55,715 568 30ms 448ms 7.7s 17.9s 0 transport_latency_assumed last_trade_price m 56,675 28,533 7ms 38ms 284ms 6.4s 0 transport_latency_assumed last_trade_price n 54,932 101 76ms 2.2s 11.1s 27.7s 0 transport_latency_assumed last_trade_price o 56,756 27,210 7ms 41ms 373ms 11.5s 0 transport_latency_assumed market_resolved h 648 37 29ms 877ms 58.4s 59.6s 0 transport_latency_assumed market_resolved i 648 79 28ms 33.4s 47.4s 47.5s 0 transport_latency_assumed market_resolved m 648 294 7ms 34.7s 48.9s 49.0s 0 transport_latency_assumed market_resolved n 648 1 53ms 38.6s 55.4s 55.5s 0 transport_latency_assumed market_resolved o 648 273 7ms 33.4s 47.6s 47.7s 0 transport_latency_assumed new_market h 3,305 684 201ms 30.3s 46.1s 1.6min 0 transport_latency_assumed new_market i 3,305 707 127ms 28.3s 45.2s 1.8min 0 transport_latency_assumed new_market m 3,297 1,809 76ms 29.0s 43.4s 1.6min 0 transport_latency_assumed new_market n 3,297 1,118 108ms 33.5s 45.3s 1.5min 0 transport_latency_assumed new_market o 3,300 1,334 123ms 32.8s 51.8s 1.4min 0 transport_latency_assumed price_change h 112,147,966 1,045,784 22ms 153ms 2.4s 2.0min 0 transport_latency_assumed price_change i 111,841,696 1,562,978 22ms 75ms 2.4s 18.1s 0 transport_latency_assumed price_change m 112,433,970 58,079,168 6ms 26ms 232ms 7.6s 0 transport_latency_assumed price_change n 111,713,018 138,906 46ms 207ms 5.9s 29.7s 0 transport_latency_assumed price_change o 112,482,530 51,797,136 6ms 30ms 286ms 13.2s 0 transport_latency_assumed tick_size_change h 2,514 14 22ms 134ms 2.3s 12.2s 0 transport_latency_assumed tick_size_change i 2,538 31 22ms 44ms 1.3s 14.1s 0 transport_latency_assumed tick_size_change m 2,538 1,343 6ms 20ms 138ms 425ms 0 transport_latency_assumed tick_size_change n 2,538 1 46ms 89ms 493ms 16.5s 0 transport_latency_assumed tick_size_change o 2,538 1,149 7ms 21ms 327ms 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-08/18/2026-10-08T18.parquet sha256sum 2026-10-08T18.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.