concept
Vendor elimination
How and where a vendor is removed from the recommendation set as requirements are added.
- Question
- At which requirement is a vendor eliminated, and what makes an evaluator drop it?
Research components
Answers business questions
- Why did we disappear after follow-up questions?
- What must become true to survive evaluation?
- How do we measure whether our position improved?
- How do AI systems evaluate and recommend vendors?
Vendor elimination studies the moment a company leaves the recommendation set: which requirement removes it, and whether the removal holds across repeated runs. A real elimination is one where a vendor is present, then absent, and stays absent.
The core question is where and why a vendor is dropped. What remains open is whether the same elimination appears on more than one evaluator, and how much of it traces to the requirement rather than the evaluator.
Evidence in this component
What we have run, and what we have seen.
Experiments
- E-043Accounting software: When the whole field is wiped out and replaced
- E-044Accounting software: When the same kill repeats on a second evaluator
- E-034Clinical trial management software: When the recommendation set collapses
- E-002Healthcare CDP and the HIPAA flip: the program's one causally verified gate
Observations
- Candidate · 2026-07-20The same elimination appeared on two different evaluators
Related components
Relevant business questions
- Why did we disappear after follow-up questions?
- How do AI systems evaluate and recommend vendors?
This object references
- part-of → recommendation-survivability
- observes → requirements
Referenced by
- surface-independent-kill-effect (part-of)
- E-002 (part-of)
- E-034 (part-of)
- E-043 (part-of)
- E-044 (part-of)
Authors
Upstream Zero
Machine rendering