Principles embedded in the product
These principles shape day-to-day engineering choices. A new connector is evaluated for permission scope, rate-limit behavior, failure visibility, field provenance, and whether it can operate without silently widening the task. A workflow is not ready merely because it returns data. Reviewers need enough context to reproduce the input, understand the transformation, and decide whether the output belongs in an operational system.
Show the stateCopying, running, configuring, and producing a first result are different states, and the interface should never blur them.
Keep evidence closeFirmographic, technographic, and contact fields are more useful when operators can see status and provenance.
Protect the reviewDraft generation must not quietly become automatic sending; approval belongs to the accountable operator.
Design for removalInstallations should be inspectable, credentials should remain scoped, and teams should understand how to update or uninstall.