What several separate origins carried in the published window

The corroboration layer of the maintained record: events in the published window that publishers carried from more than one separate origin. Free, no key, CORS-enabled (access-control-allow-origin: *). Each entry carries the claim as its sources state it, the corroboration tier, two exact counts — publisherCount (distinct publishers that carried it, after wire copies, republished copies and same-portal duplicates are collapsed) and originCount (separate origins left after publishers behind one address, and publishers relaying one named upstream, are collapsed too) — the publishers by name with wires marked, the number of republished copies collapsed, the entities, and the earliest report date when the producing run carries one. The tier is computed from knownOriginCount (originCount minus originsUnknownUpstream): strong = carried by publishers from 4 or more separate origins, moderate = from 2 or 3. NEITHER COUNT IS EVIDENTIARY INDEPENDENCE: an outlet that names no upstream still counts as its own origin (originsUnknownUpstream says how many could not be checked), and many outlets working from one official statement is wide carriage, not verification. The method object states the counting rules (publisher_rule, origin_rule, aggregator_rule) and the engine's own words verbatim under engineMethod. knownOriginCount is the separate origins whose upstream is known, the count the tier stands on. DEPRECATED ALIAS: independentOrigins mirrors knownOriginCount (identical value, null when the origins were not measured), kept so existing readers do not break and never larger than the count the tier stands on; it is not dependency-aware evidentiary independence — read publisherCount, originCount and knownOriginCount. NO PROBABILITY HERE IS OURS: prediction-market prices appear only where the match was claim-direction verified, and are a cited external sensor; we serve current state, not forecasts. THREE STATES, NEVER TWO: state is measured (the pass ran — an empty clusters list then means nothing cleared the bar) or cannot-measure with cannotMeasureReason naming which pass failed. A cannot-measure reading is served as a 200, not an error, so a client can distinguish a quiet week from a blind instrument. Rate limits: 30 requests/minute burst per network address and 500/day anonymous (this read spends no model tokens; the limits protect the edge). Cached 10 minutes at the edge.