Skip to main content

PF_MULTI_001 — One winning quote per Opportunity with sibling quotes lost

This proof tests one bounded workflow: several representative quotes share one Opportunity, one selected quote is won, and every sibling quote becomes lost. It does not claim a measured reduction in pipeline double counting or any change in win rate or market share.

kind: proof_catalog
schema_version: 2
proofs:
- id: PF_MULTI_001
vertical_ids:
- M1_V1
- M1_V2
- M1_V3
- M1_V4
- M1_V5
- M1_V6
- M1_V7
name: 'One winning quote per Opportunity with sibling quotes lost'
status: approved
proof_type: 'workflow test'
safe_artifact: >-
One sanitized representative Opportunity with at least two non-sensitive
sales quotes linked to it; no customer-identifying or live customer data.
procedure:
- 'Create or select one Opportunity representing the shared end project.'
- >-
From the Opportunity table, use Generate Sales Quote at least twice so
two or more representative quotes share that Opportunity.
- >-
Inspect Associated sales quotes to confirm every test quote is linked to
the selected Opportunity.
- 'Take one selected quote through the winning sales-order conversion path.'
- >-
Reopen the Opportunity and inspect the selected quote and every sibling
quote.
expected_observation: >-
The selected quote has status won, every other quote sharing the
Opportunity has status lost, and all test quotes remain inspectable under
Associated sales quotes.
acceptance_criterion: >-
For an Opportunity with N linked quotes, where N is at least 2, exactly
one selected quote has status won and all N-1 sibling quotes have status
lost after the winning action; no sibling remains draft, open, or
acknowledged.
owner: sales
capability_boundaries:
- >-
A Quote stores data.opportunityId, the Opportunity table exposes
Generate Sales Quote, and the Opportunity view exposes Associated sales
quotes.
- >-
The configured won state describes sibling loss, and the winning action
resolves to process-sales-order-from-quote. The hook body did not expose
the exact sibling-status writes.
- >-
The customer must define the underlying project and use the correct
Opportunity. Automatic project matching and historical backfill are not
demonstrated.
- >-
The observed context is one private buyer account with more
than 200 quotes across multiple Opportunities over more than one year;
exact dates and the account's vertical were not supplied.
- >-
Applicability across M1_V1 through M1_V7 relies on product-expert
attestation, not separate production samples in every vertical.
- >-
This proof does not independently measure pipeline reporting, quantified
double-counting reduction, final project award, win rate, or market
share.
transfer:
level: prohibited
from_vertical_ids: []
conditions:
- >-
Use is limited to the listed vertical_ids. Any future or otherwise
unlisted vertical requires separately validated evidence
and an explicit applicable canonical transfer rule.
evidence_ids:
- EV_MULTI_002