Publication lifecycle
The path from a bounded private signal to public Market Demand and partner sync.
1. Eligibility
A modeled gap enters from the curated case materialization path, while an observed gap requires a completed real analysis and a confirmed uncovered exposure. An explicit request still requires a deliberate request action, and each path keeps its own evidence class.
2. Bounded capture
Customer capture accepts taxonomy values rather than raw text. The event can include a risk type, evidence class, harm direction, time horizon, coarse business segment, coarse geography and amount band when allowed. Raw owner prose, business names, exact addresses, monetary amounts, browser identifiers and model traces do not enter the event.
3. Private grouping
Eligible records accumulate in private cells whose keys use bounded dimensions. Below five unreleased members, customer evidence stays private.
4. Scheduled release
Complete groups publish with a weekly Monday bucket instead of individual event times. Published customer counts advance in multiples of five. Any remainder waits for a later complete group.
5. Public generation
Published Demand records receive partner-safe identifiers, lifecycle state and change metadata. The Partner API exposes a coherent public generation across snapshot, summary and taxonomy. Incremental consumers apply only the released changes after a completed snapshot.
Product refresh timing
The browser can refresh grouped Demand after local capture, on focus and on its regular visible-page interval. Capture alone cannot change the public count; a separate privacy step must first publish the newly recorded private event.