Synthesize multiple papers, benchmarks, interviews, reviews, or other sources into a defensible and qualified conclusion. Use for conflicting evidence, literature synthesis, claim auditing, argument mapping, qualitative coding, belief updates, or any request that must expose counter-evidence, uncertainty, and source…
Draw the line where it costs least. Use for build-vs-buy calls, "where does this module/team/service boundary belong?", APIs and abstractions forcing users into implementation vocabulary, tools that should augment rather than automate, hardcoded decisions that belong at runtime, or information nobody can find.
Correlation walked in; make it prove causation. Use when someone claims "X causes Y" from observational data, asks "did the change actually cause the improvement?", "is this confounded?", "what would have happened if we hadn't shipped it?", plans an A/B test, or investigates why an incident/outbreak spread the way it…