# Prospecting extensions

> Explore bounded continuation Jobs and immutable qualification rubrics without treating either contract as GA.

Canonical guide: <https://api.blackpearl.com/docs/prospecting-extensions>

Raw Markdown: <https://api.blackpearl.com/docs/raw/prospecting-extensions.md>

OpenAPI: <https://api.blackpearl.com/v1/openapi.json>

These Prospecting extensions are Preview. They are useful for integration testing, but their contracts may change incompatibly and continuation execution requires a configured private backend. An unconfigured backend fails the child Job without persisting a synthetic result. Build the GA workflow around [Prospecting](https://api.blackpearl.com/docs/prospecting), Jobs, and Outcomes first.

## Create a bounded continuation

Preview operation `create_prospecting_continuation_v1_jobs__parent_job_id__continuations_post` creates one immutable child of a succeeded real Prospecting Job. It does not mutate or resume the parent.

```bash
curl --fail-with-body --silent --show-error \
  --request POST "$BLACKPEARL_API_BASE_URL/v1/jobs/$PARENT_JOB_ID/continuations" \
  --header "Authorization: Bearer $BLACKPEARL_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "continuation_key": "more-anz-revops-20260717",
    "additional_prospect_limit": 20,
    "max_rounds": 2,
    "min_new_prospects_per_round": 1
  }'
```

The parent and bearer key must share project and `live`/`test` environment. The parent must be a succeeded Prospecting Job with a valid normalized, non-synthetic result. The child binds the parent ID, result hash, normalized result snapshot, connection revision, and constraints so later changes cannot alter its provenance. Reusing the continuation key with the same request replays the child; changed constraints conflict.

## Store qualification policy contracts

Preview operation `create_qualification_policy_v1_qualification_policies_post` stores an immutable five-dimension rubric. A policy freezes its target taxonomy, exact integer weights, evidence and freshness rules, score bands, and expected policy version. It does not score prospects or authorize downstream action.

Preview operation `list_qualification_policies_v1_qualification_policies_get` lists policies in the current project and environment with cursor pagination. Preview operation `get_qualification_policy_v1_qualification_policies__qualification_policy_id__get` reads one policy. Use the returned policy hash when a future executor requires optimistic binding; never infer that creating a policy means a scorer is available.

Preview resources should remain isolated behind a feature flag and observability boundary. Do not persist assumptions about their schema into irreversible workflows.