Ask for the evidence path, not the answer.

“Why is BGP down?” can produce a fluent answer. It does not force the system to prove that answer.

Expand the diagnostic surface.

That sequence is useful because each layer can falsify an assumption made at another layer. A BGP session can be established while the expected prefix is absent. The prefix can exist in the RIB while the FIB resolves differently. The forward path can work while the return path crosses the wrong stateful boundary.

Prompt for boundaries.

Ask the system to separate observed facts, inferred causes, missing evidence, architecture impact, and recommended next tests. Then require citations to the network evidence or tool output that supports each claim.