How does a pilot move from sample to a listing a marketplace can publish?

A marketplace's data product lead opens listing `LIST-0087` for a healthcare administration release: purchase approvals at a multi-site clinic group. The pilot covers one domain and four tables, `requests`, `authority_matrix`, `delegations` and `decisions`, plus a small task set with expected outcomes.

The sample arrives with a manifest and a schema file. The data quality analyst runs the join and boundary checks and finds that every request at exactly the clinic manager's limit of $5,000 is approved, with none rejected. That is a coverage gap, not an error, so they ask for boundary cases to be added in the next version.

In parallel, the licensing lead reads the draft licence and finds it does not say whether customers may fine-tune models on the data and then distribute those models. The listing status moves from `draft` to `blocked_pending_licence`. Once the permitted uses are agreed in writing, the manifest's `permitted_uses` field is updated and the status moves to `ready_for_review`.

The consequence is that nothing reaches a customer until both streams clear. Had the listing gone live on data quality alone, the marketplace would have sold material to customers whose intended use the licence had not addressed.

**What it teaches:** run quality checks and licence review as separate gates, record each gate's status against the listing, and review the sample for grounding and disclosure risk because the material is generated.