I’d wait. payments-api has an active incident, and this change touches the same service. Nothing here contradicts the score — but the score can’t see the incident timeline. Ship after the incident closes.
See it, then try it
Watch the Advisor decide — 2 minutes, no install
Open the interactive demo and choose the Engineering Advisor scenario: a live pre-flight where the score says SHIP and the Advisor says wait — and is right. The exact moment above, played out.
Try this yourself
Install on your own cluster and follow Your First Recommendation — you’ll run a real pre-flight in minutes. Advisor notes appear where the Early Access flag is enabled for your tenant.
Silence is deliberate
If the Advisor has nothing material to add beyond the score and the verdict, it stays silent. Restraint is the feature — you should never see filler advice, and when a note does appear it’s because something changed the decision.Availability — Early Access
Don’t plan production dependencies on Early Access capabilities. What every tenant has today, GA:- The pre-flight check — an on-demand SHIP / HOLD / BLOCK verdict with the score and reasons. See Connect your first cluster.
- Incident investigation — root cause with cited evidence, a proposed fix, and how to verify it. See Your First Recommendation.