... Engineering culture says document your limitations. Marketing culture says lead with your strengths. I keep seeing evidence for both: changelogs that openly admit bugs seem to earn trust, "known limitations" pages get cited approvingly in communities (and yet the competitor with the confident, caveat-free claim often still wins the comparison table). So I'd love real stories from builders here. Have you shipped something where you stated the limits up front: error margins, unsupported cases, an honest "this tool ... ... What actually happened: did users reward the honesty, or did you just hand your objections to a competitor

... because it's dumb, but because the radius is determined by capabilities it isn't even looking at. That's the strongest version of the "worst judge of its own reach" point I've seen. And your authority-armed-versus-action-approved distinction is the one I'd underline hardest, because it's exactly the stale-gate failure from earlier in this thread wearing a security hat. A global unlock tells you authority is currently armed. It says nothing about ... ... Genuine question, since Writeara lives exactly on this line: do you treat every destination as one publish-gate, or does the gate's weight scale with the destination's reach, a push to a personal blog with 12 readers versus

... actual insight, and it's bigger than it looks: making the notification say why it's waiting is what turns a ping into a triage. "Done" makes you tab back to find out what "done" means. "Needs approval vs finished vs