Hour audit: 2026-10-06T13
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-06T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T13:00:00.000068099+00:00 · last event 2026-10-06T13:59:59.999985479+00:00
VOLUME 119,703,914 rows · 1,355,178,571 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 119,643,768 · o: 119,639,263 · h: 119,615,731 · i: 119,408,058 · n: 119,203,487 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 58,640,795 (48.99%) · o: 59,130,289 (49.40%) · h: 1,133,456 (0.95%) · i: 754,789 (0.63%) · n: 44,585 (0.04%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 119,703,914 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 813ffcd74f18eeb53528a657f91114705f9c6df9f970b1fe4e05149f72ccdefa
the corpus checksum ledger names this file with the same digest
joined 119,704,964 to merged 119,703,914, minus 1,050 (minus 0.0009%)
boundary drops 1,050 · 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-06T15:06:22Z 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 11,064,026 143,017,660 0-42 49b3ff7e605c8643c2d28651c8ba2d3287e296701802048aef1e6387ee0f1171 book 149,622 16,844,012 43-43 5a046d537ef279af37d39b4072757115e8f6f42f5c93e65d9474f6016df8d874 last_trade_price 62,794 3,626,477 44-44 db6d754c34367451232b62254adbc3b0ca77665021157d0ab8174f4b65472513 market_resolved 943 147,771 45-45 b958974319d6dad3274042e4ee25e8f58dea05a58497ab0cfacfd5211e87703e new_market 1,667 156,771 46-46 b45ff9e041e2212ae054cd71b6d7828b2eb36d264b0109b2c88bf26c44226c4d price_change 108,419,938 1,189,839,773 47-460 605e67af7045e7ddda233224b1b7f6a225861a2b87b8b6915a10e59d96452fd1 tick_size_change 4,924 181,033 461-461 bfdfd67dc8161e9e7c318bc864e651fd5bd89387fa1956f9da8504efb2c6a0be EVENT MIX count share price_change 108,419,938 90.57% best_bid_ask 11,064,026 9.24% book 149,622 0.12% last_trade_price 62,794 0.05% tick_size_change 4,924 <0.01% new_market 1,667 <0.01% market_resolved 943 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,064,150 11,064,026 124 57 FULL book 149,624 149,622 2 8,295 FULL last_trade_price 62,794 62,794 0 0 FULL market_resolved 943 943 0 0 FULL new_market 1,667 1,667 0 0 FULL price_change 108,420,862 108,419,938 924 182 FULL tick_size_change 4,924 4,924 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,061,941 99,488 19ms 34ms 268ms 46.0s 0 transport_latency_assumed best_bid_ask i 11,057,000 66,960 22ms 36ms 173ms 9.4s 0 transport_latency_assumed best_bid_ask m 11,063,210 5,385,937 6ms 18ms 105ms 7.7s 0 transport_latency_assumed best_bid_ask n 11,055,774 2,894 45ms 65ms 350ms 35.3s 0 transport_latency_assumed best_bid_ask o 11,062,849 5,508,747 5ms 18ms 109ms 5.6s 0 transport_latency_assumed book h 131,209 5,390 25ms 292ms 4.9h 111.1d 0 book_staleness book i 130,812 6,489 27ms 684ms 5.4h 111.1d 0 book_staleness book m 129,630 65,209 8ms 41ms 9.8min 111.0d 0 book_staleness book n 133,838 8,502 52ms 3.8s 19.4h 129.6d 0 book_staleness book o 129,302 64,032 8ms 42ms 6.1min 111.1d 0 book_staleness last_trade_price h 62,611 632 21ms 159ms 1.0s 25.2s 0 transport_latency_assumed last_trade_price i 61,896 434 27ms 283ms 5.0s 9.4s 0 transport_latency_assumed last_trade_price m 62,628 31,197 7ms 28ms 206ms 3.9s 0 transport_latency_assumed last_trade_price n 61,593 35 52ms 1.0s 8.3s 33.5s 0 transport_latency_assumed last_trade_price o 62,588 30,496 7ms 29ms 199ms 2.6s 0 transport_latency_assumed market_resolved h 924 6 21ms 17.8s 45.4s 45.5s 0 transport_latency_assumed market_resolved i 924 132 23ms 26.4s 50.9s 51.0s 0 transport_latency_assumed market_resolved m 924 380 7ms 29.9s 54.1s 54.1s 0 transport_latency_assumed market_resolved n 924 not meas. 47ms 24.3s 52.2s 52.2s 0 transport_latency_assumed market_resolved o 924 425 7ms 22.2s 49.8s 49.9s 0 transport_latency_assumed new_market h 996 147 162ms 1.1min 2.3min 2.7min 0 transport_latency_assumed new_market i 996 234 105ms 1.1min 2.4min 2.8min 0 transport_latency_assumed new_market m 996 664 48ms 1.0min 2.3min 2.7min 0 transport_latency_assumed new_market n 996 188 213ms 1.2min 2.5min 2.8min 0 transport_latency_assumed new_market o 996 434 66ms 47.9s 2.4min 2.7min 0 transport_latency_assumed price_change h 108,353,130 1,027,774 19ms 42ms 466ms 47.1s 0 transport_latency_assumed price_change i 108,151,506 680,534 22ms 47ms 692ms 9.4s 0 transport_latency_assumed price_change m 108,381,456 53,154,962 6ms 20ms 117ms 8.6s 0 transport_latency_assumed price_change n 107,945,438 32,966 45ms 97ms 3.2s 36.5s 0 transport_latency_assumed price_change o 108,377,680 53,523,702 6ms 20ms 124ms 5.7s 0 transport_latency_assumed tick_size_change h 4,920 19 19ms 39ms 217ms 5.9s 0 transport_latency_assumed tick_size_change i 4,924 6 22ms 42ms 95ms 167ms 0 transport_latency_assumed tick_size_change m 4,924 2,446 5ms 15ms 44ms 492ms 0 transport_latency_assumed tick_size_change n 4,924 not meas. 45ms 54ms 167ms 1.3s 0 transport_latency_assumed tick_size_change o 4,924 2,453 6ms 15ms 50ms 252ms 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/13/2026-10-06T13.parquet sha256sum 2026-10-06T13.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.