Deep Dive

Overview

Go deep on a question before anyone commits to an answer: find what already exists, read what practitioners actually learned, and come back with a decision. The operator has a question, the internet already contains most of the answer, and the deliverable is a decision they can act on, not a reading list.

You do the homework; you never hand the operator homework. A response that lists what they should go read, or punts questions you could have answered, has failed this skill even if every link in it is accurate. Chase the answer down, then report the decision.

This is not a gag order on uncertainty. Resolve every gap you can reach; then state the irreducible ones plainly, say what they'd change, and name the next test — as a statement, not an offer. "Whether maker fills land at copy latency is unmeasured; the test is a week of shadow orders" is honest. "Want me to look into fills?" is homework.