Hour audit: 2026-10-04T06
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-04T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T06:00:00.000017507+00:00 · last event 2026-10-04T06:59:59.998922878+00:00
VOLUME 94,054,624 rows · 964,530,948 bytes (919.85 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 93,995,809 · m: 93,991,309 · h: 93,968,920 · k: 93,967,513 · g: 93,865,877 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 352,056 (0.37%) · m: 90,528,941 (96.25%) · h: 611,086 (0.65%) · k: 2,531,306 (2.69%) · g: 31,235 (0.03%) (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 94,054,624 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2a19c24e0260b64c07b5b18d06c97956b59d6c7ec5440a345a2620f31cc906f1
the corpus checksum ledger names this file with the same digest
joined 94,056,552 to merged 94,054,624, minus 1,928 (minus 0.0020%)
boundary drops 1,928 · 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-04T08:43:10Z 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 9,043,934 105,328,299 0-34 699f5f662cf4718fd677c20e31d937eca2faab9eef123b403606da4e4fed2889 book 133,342 13,150,788 35-35 a455272e92c5e2a61dd59623f1e693334ff5125ac4b4d4d28d8cad595be86657 last_trade_price 44,084 2,549,356 36-36 3beedd840d5b7fe9eea6bc7723358543766a0b800e4fd4309e0823fa080e062b market_resolved 1,497 229,999 37-37 8eed34cbe4def24697ed155888ab18ea9676dca8a09029dd8e7c168d40c8aaf0 new_market 1,543 149,074 38-38 dbd3d17b5e3461db353f55ab36c9b362c4bad8e41fcd73d03faefed204d949c4 price_change 84,826,168 841,899,069 39-362 b154aeb0a301737b3d7f853fb29009fc1fcd73b5a027cb8fcafe8a0496d3c70f tick_size_change 4,056 148,801 363-363 2d74e4836b79151c9fcdfbe9fd47b5edd0d2ca388cd1bea46a9665f4814da30d EVENT MIX count share price_change 84,826,168 90.19% best_bid_ask 9,043,934 9.62% book 133,342 0.14% last_trade_price 44,084 0.05% tick_size_change 4,056 <0.01% new_market 1,543 <0.01% market_resolved 1,497 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,044,116 9,043,934 182 207 FULL book 133,344 133,342 2 18,439 FULL last_trade_price 44,084 44,084 0 0 FULL market_resolved 1,497 1,497 0 0 FULL new_market 1,543 1,543 0 0 FULL price_change 84,827,912 84,826,168 1,744 405 FULL tick_size_change 4,056 4,056 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,040,882 537 75ms 92ms 417ms 15.4s 0 transport_latency_assumed best_bid_ask h 9,041,949 50,471 17ms 22ms 249ms 1.7min 0 transport_latency_assumed best_bid_ask i 9,042,832 28,380 20ms 24ms 126ms 19.1s 0 transport_latency_assumed best_bid_ask k 9,042,126 222,115 13ms 19ms 179ms 1.1min 0 transport_latency_assumed best_bid_ask m 9,043,154 8,742,431 4ms 8ms 49ms 5.6s 0 transport_latency_assumed book g 114,636 24,698 80ms 45.7min 26.8d 127.3d 0 book_staleness book h 96,442 7,484 21ms 187ms 1.4d 127.3d 0 book_staleness book i 92,561 3,469 22ms 62ms 1.6h 108.8d 0 book_staleness book k 96,410 10,224 16ms 137ms 1.5d 108.8d 0 book_staleness book m 93,466 87,467 6ms 23ms 4.7h 108.8d 0 book_staleness last_trade_price g 43,816 7 77ms 191ms 1.3s 13.4s 0 transport_latency_assumed last_trade_price h 44,012 495 19ms 30ms 434ms 50.2s 0 transport_latency_assumed last_trade_price i 44,055 237 21ms 36ms 330ms 3.3s 0 transport_latency_assumed last_trade_price k 44,016 1,705 14ms 24ms 271ms 19.1s 0 transport_latency_assumed last_trade_price m 44,070 41,640 5ms 12ms 121ms 3.4s 0 transport_latency_assumed market_resolved g 1,425 not meas. 76ms 221ms 51.0s 51.2s 0 transport_latency_assumed market_resolved h 1,425 11 19ms 55ms 52.3s 1.0min 0 transport_latency_assumed market_resolved i 1,425 5 21ms 55ms 50.9s 57.4s 0 transport_latency_assumed market_resolved k 1,425 91 14ms 32ms 51.4s 51.5s 0 transport_latency_assumed market_resolved m 1,425 1,390 5ms 18.2s 48.8s 48.9s 0 transport_latency_assumed new_market g 990 153 510ms 56.0s 1.1min 1.6min 0 transport_latency_assumed new_market h 990 127 289ms 53.2s 1.1min 1.8min 0 transport_latency_assumed new_market i 990 259 304ms 52.7s 1.0min 1.8min 0 transport_latency_assumed new_market k 990 393 393ms 51.6s 59.2s 1.9min 0 transport_latency_assumed new_market m 990 611 78ms 54.3s 1.1min 1.5min 0 transport_latency_assumed price_change g 84,660,076 5,836 75ms 95ms 660ms 15.4s 0 transport_latency_assumed price_change h 84,780,050 552,478 17ms 24ms 311ms 1.7min 0 transport_latency_assumed price_change i 84,809,890 319,696 20ms 26ms 243ms 19.1s 0 transport_latency_assumed price_change k 84,778,490 2,296,678 13ms 20ms 235ms 1.2min 0 transport_latency_assumed price_change m 84,804,148 81,651,480 4ms 9ms 61ms 5.8s 0 transport_latency_assumed tick_size_change g 4,052 4 75ms 92ms 828ms 5.6s 0 transport_latency_assumed tick_size_change h 4,052 20 17ms 23ms 476ms 30.1s 0 transport_latency_assumed tick_size_change i 4,056 10 20ms 26ms 429ms 753ms 0 transport_latency_assumed tick_size_change k 4,056 100 13ms 22ms 665ms 12.5s 0 transport_latency_assumed tick_size_change m 4,056 3,922 4ms 9ms 87ms 498ms 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/06/2026-10-04T06.parquet sha256sum 2026-10-04T06.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.