Hour audit: 2026-09-23T17
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-09-23T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T17:00:00.000023869+00:00 · last event 2026-09-23T17:59:59.999722936+00:00
VOLUME 137,879,019 rows · 1,542,552,366 bytes (1.44 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 135,002,127 · g: 129,313,923 · i: 124,881,934 · k: 119,565,597 · c: 103,239,526 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 9,376,322 (6.80%) · g: 159,311 (0.12%) · i: 2,575,689 (1.87%) · k: 33,807,598 (24.52%) · c: 91,960,099 (66.70%) (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 137,879,019 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 42013a21fa1ff21f8cde9ce312dc035555d938c8ccf91547db18ebd57f2c30f4
the corpus checksum ledger names this file with the same digest
joined 137,881,316 to merged 137,879,019, minus 2,297 (minus 0.0017%)
boundary drops 2,297 · 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-24T03:48:34Z as cghik
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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,991,058 146,120,327 0-45 c9b1f60fe3811a4ec46c4ea725571e8677f89fa84dd929801d434a1fc9a897ac book 2,961,900 116,524,732 46-57 da6c71b0df57aab40bddf26f46ef4007e4c6530f23ad50630594b777652247f3 last_trade_price 65,522 3,724,353 58-58 45bced21ec59dcb64d0d46296d6da7cde3c06cca10acf287041835266749b0c2 market_resolved 1,025 112,196 59-59 7543aa07c6c290fa442cf74af6f18f8b0e4f8a8acd98eb9c6e8005b011961877 new_market 1,724 167,024 60-60 6d55456523ad622c8784fd36284516b37d7649732915dbf867b74af017fb195a price_change 122,854,274 1,274,210,548 61-529 b0af48a9556ac2af890f1aee4f6b97df41f0ad22d40e1a13985a252aab1d3607 tick_size_change 3,516 126,483 530-530 b6baf0ecbecac4a63e1d5995aee0e75f5215c40fb90912c5b14f98a70cf1ef71 EVENT MIX count share price_change 122,854,274 89.10% best_bid_ask 11,991,058 8.70% book 2,961,900 2.15% last_trade_price 65,522 0.05% tick_size_change 3,516 <0.01% new_market 1,724 <0.01% market_resolved 1,025 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,991,260 11,991,058 202 4,107 FULL book 2,962,188 2,961,900 288 189,888 FULL last_trade_price 65,522 65,522 0 800 FULL market_resolved 1,025 1,025 0 78 FULL new_market 1,739 1,724 15 199 FULL price_change 122,856,066 122,854,274 1,792 1,179 FULL tick_size_change 3,516 3,516 0 349 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,022,141 8,109,825 5ms 19ms 131ms 3.2s 0 transport_latency_assumed best_bid_ask g 11,515,150 7,829 79ms 118ms 571ms 34.2s 0 transport_latency_assumed best_bid_ask h 11,989,425 789,887 19ms 40ms 170ms 19.4s 0 transport_latency_assumed best_bid_ask i 11,039,588 191,039 21ms 38ms 148ms 14.1s 0 transport_latency_assumed best_bid_ask k 10,566,058 2,892,478 13ms 25ms 107ms 5.6s 0 transport_latency_assumed book c 2,450,012 2,119,291 8.1min 4.2d 42.9d 116.8d 0 book_staleness book g 546,390 40,162 4.7min 2.8d 35.6d 116.8d 0 book_staleness book h 137,244 14,107 25ms 194ms 22.4min 98.3d 0 book_staleness book i 934,146 212,572 7.3min 3.1d 41.9d 116.8d 0 book_staleness book k 1,310,478 575,768 9.1min 4.1d 42.1d 116.8d 0 book_staleness last_trade_price c 46,988 41,391 6ms 30ms 203ms 1.3s 0 transport_latency_assumed last_trade_price g 58,998 128 100ms 3.5s 15.3s 34.2s 0 transport_latency_assumed last_trade_price h 65,344 5,486 22ms 113ms 522ms 6.9s 0 transport_latency_assumed last_trade_price i 59,036 1,119 26ms 191ms 1.1s 3.4s 0 transport_latency_assumed last_trade_price k 56,998 17,398 14ms 47ms 249ms 1.2s 0 transport_latency_assumed market_resolved c 687 520 8ms 5.8min 10.4min 10.8min 0 transport_latency_assumed market_resolved g 618 2 90ms 24.7s 5.7min 5.7min 0 transport_latency_assumed market_resolved h 630 113 22ms 10.2s 41.7s 41.8s 0 transport_latency_assumed market_resolved i 643 32 26ms 4.7min 9.6min 9.8min 0 transport_latency_assumed market_resolved k 797 358 28ms 9.0min 14.4min 15.1min 0 transport_latency_assumed new_market c 1,099 493 257ms 4.8min 6.2min 6.2min 0 transport_latency_assumed new_market g 874 72 293ms 4.3min 1.6h 1.6h 0 transport_latency_assumed new_market h 1,016 329 129ms 37.3s 58.2s 2.0min 0 transport_latency_assumed new_market i 1,039 277 94ms 8.2s 5.5min 5.5min 0 transport_latency_assumed new_market k 1,353 553 108ms 4.7min 9.8min 10.8min 0 transport_latency_assumed price_change c 91,716,019 81,686,243 6ms 23ms 164ms 3.8s 0 transport_latency_assumed price_change g 117,188,525 111,118 80ms 182ms 5.8s 34.2s 0 transport_latency_assumed price_change h 122,804,952 8,566,092 19ms 48ms 248ms 21.6s 0 transport_latency_assumed price_change i 112,844,202 2,170,586 22ms 49ms 273ms 19.7s 0 transport_latency_assumed price_change k 107,627,009 30,320,235 13ms 29ms 145ms 6.2s 0 transport_latency_assumed tick_size_change c 2,580 2,336 5ms 18ms 67ms 390ms 0 transport_latency_assumed tick_size_change g 3,368 not meas. 79ms 113ms 289ms 1.1s 0 transport_latency_assumed tick_size_change h 3,516 308 19ms 41ms 118ms 721ms 0 transport_latency_assumed tick_size_change i 3,280 64 22ms 38ms 113ms 228ms 0 transport_latency_assumed tick_size_change k 2,904 808 13ms 26ms 83ms 412ms 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-23/17/2026-09-23T17.parquet sha256sum 2026-09-23T17.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.