Trust Simplified

• Users trust that the software behaves as expected
• Product Owners trust that changes can be made without exorbitant cost, and without breaking existing functionality
• Engineers trust that the changes they're making don't break existing functionality
• Engineers trust that the agents are writing good-enough code
• Engineers trust that the tests written by the agents are meaningful

The most important one is the first. Users need to be able to trust that the software behaves as expected. Everything else is downstream from that, and can be optimized within that primary constraint.

In order to know whether or not the software behaves as expected, we have to clarify expectations. The product owner should be able to approximate user expectations up front, and then support tickets come in to clarify the edges.

User expectations follow existing idioms for working software (Google works like this, so why wouldn't this thing be similar?), and documentation for that specific software.