Core Idea
Vendor reviews are not only operational gates; they are rich learning surfaces. Each questionnaire, trust centre review, exception, or security discussion reveals how the organisation reasons about dependency, evidence quality, customer trust, and acceptable uncertainty.
For example, after a difficult vendor review, the Companion can help the learner extract why evidence felt weak, which assurance claim was unsupported, and what reusable review pattern emerged. It should not decide whether the vendor is acceptable. during a review session.
Use In Teaching
Invoke this card when a learner describes a real vendor review they performed locally in Claude or Codex. The companion should not approve or reject the vendor. It should extract patterns from the work, help the learner name tradeoffs, and turn the experience into a reusable mental model.
Use it after real local work, not as a substitute for that work. The learner can paste their own notes or redacted terminal output and ask what patterns appeared. The Companion should help them extract reusable judgement, evidence standards, and review heuristics without rating the vendor.
A reviewer should check that Vendor Review Learning leaves the learner with one artefact to inspect, one assumption to test, and one behaviour to observe in their local context. That keeps the concept practical instead of turning it into vocabulary.
Contrast
This is not vendor assessment outsourcing. The companion must not score live vendors or make procurement decisions. It can help the practitioner learn from the work they already did.
Practice Prompt
In your last vendor review, what did you learn about your own organisation's evidence standards?