... 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

... agent didn't just act, it acted with someone's credentials, someone's access, someone's blast radius. and when it goes wrong, the audit trail usually can't tell you what the agent was actually authorised to do versus what it happened to have access to. those are different things and most systems conflate them. honestly that's a big part of why we're building MonoCloud the way we are. scoped identity for agents so the blast radius ... ... nothing, the reviewer's normal experience becomes an empty screen, and empty screens train people to expect empty. Whether the one that is not empty gets read properly on day forty is an open question. It still beats the alternative

... galdayan): our setup ended up being a Slack webhook per agent session, posted to a channel only that agent writes to. sounds basic but the key part was making the notification say WHY it's waiting (needs approval vs finished vs