Hour audit: 2026-09-26T02
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 2 contributed no rows: c, g. The hour is still whole on minutes; it simply rests on 3 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-26T02 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T02:00:00.000013721+00:00 · last event 2026-09-26T02:59:59.999606286+00:00
VOLUME 116,710,478 rows · 1,212,767,498 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured h: 116,507,269 · k: 116,452,196 · i: 114,341,060 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,478,268 (6.41%) · k: 105,301,545 (90.22%) · i: 3,930,665 (3.37%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 24fe89f444f7d9de0e3c7f2f67247c3fd8df1c1920c0afdeb8a99eb0edbcb199
the corpus checksum ledger names this file with the same digest
joined 116,716,661 to merged 116,710,478, minus 6,183 (minus 0.0053%)
boundary drops 6,183 · 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-09-26T04:38:58Z as hik
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,832,838 129,450,974 0-45 1b12c0d84cf8c0b49a4966b45e7a2b653cd1ae73a42b91bc5a90d7f3df3d0c48 book 522,609 49,546,461 46-47 f1fd2559bd9e5ff247b6fca95cf9d810548502e24f313853c09aa3897141ef0f last_trade_price 46,105 2,632,635 48-48 248bb1c787f51fcf668bee2435665745af3a7cd083583395c7704d3408205564 market_resolved 3,835 589,729 49-49 ba41078a5907ef5661556345bac567b38e8bf553379017912c4f20234a6b0843 new_market 1,155 127,576 50-50 16cbd36f8f279089cca3c986e5cd66d571a851fbd0d30743302560bd804ac6cd price_change 104,294,488 1,028,756,024 51-448 d4b2cc900586df70e84cc1063688aa126b16fc013fc1e1d80ad19ae50c3c6ffe tick_size_change 9,448 340,072 449-449 b8f9f73f1fe1e6319895964e07c52dc9529b40dcdd75dea3e4f7b955c16579a4 EVENT MIX count share price_change 104,294,488 89.36% best_bid_ask 11,832,838 10.14% book 522,609 0.45% last_trade_price 46,105 0.04% tick_size_change 9,448 <0.01% market_resolved 3,835 <0.01% new_market 1,155 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,833,510 11,832,838 672 51,149 PARTIAL book 522,627 522,609 18 181,379 PARTIAL last_trade_price 46,108 46,105 3 3,170 PARTIAL market_resolved 3,835 3,835 0 3,745 PARTIAL new_market 1,155 1,155 0 851 PARTIAL price_change 104,299,978 104,294,488 5,490 89,365 PARTIAL tick_size_change 9,448 9,448 0 2,362 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,830,819 702,513 18ms 27ms 155ms 45.5s 0 transport_latency_assumed best_bid_ask i 11,672,988 342,206 21ms 26ms 79ms 4.2s 0 transport_latency_assumed best_bid_ask k 11,830,712 10,788,119 12ms 19ms 97ms 8.9s 0 transport_latency_assumed book h 389,582 245,791 14.2min 4.2d 34.5d 119.2d 0 book_staleness book i 99,086 16,415 23ms 381ms 4.2d 100.6d 0 book_staleness book k 332,295 260,403 6.1min 4.2d 34.5d 119.2d 0 book_staleness last_trade_price h 45,850 3,667 19ms 50ms 300ms 9.5s 0 transport_latency_assumed last_trade_price i 44,449 2,718 22ms 37ms 188ms 3.1s 0 transport_latency_assumed last_trade_price k 45,801 39,720 13ms 32ms 211ms 1.6s 0 transport_latency_assumed market_resolved h 3,745 163 18ms 20.7s 47.5s 56.9s 0 transport_latency_assumed market_resolved i 3,702 620 22ms 26.9s 55.4s 2.4min 0 transport_latency_assumed market_resolved k 3,745 3,052 13ms 25.8s 53.3s 54.8s 0 transport_latency_assumed new_market h 851 323 107ms 17.9s 3.2min 4.3min 0 transport_latency_assumed new_market i 851 576 44ms 16.4s 2.5min 4.0min 0 transport_latency_assumed new_market k 851 256 84ms 15.0s 2.3min 4.3min 0 transport_latency_assumed price_change h 104,226,974 6,525,440 18ms 32ms 188ms 45.5s 0 transport_latency_assumed price_change i 102,510,720 3,568,006 21ms 27ms 100ms 4.8s 0 transport_latency_assumed price_change k 104,229,344 94,201,042 13ms 21ms 112ms 9.0s 0 transport_latency_assumed tick_size_change h 9,448 371 18ms 21ms 65ms 893ms 0 transport_latency_assumed tick_size_change i 9,264 124 21ms 24ms 59ms 390ms 0 transport_latency_assumed tick_size_change k 9,448 8,953 12ms 15ms 55ms 351ms 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-09-26/02/2026-09-26T02.parquet sha256sum 2026-09-26T02.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.