I think of evidence-first automation as a habit rather than a product feature. The work should leave behind enough context for another person, or a future version of me, to understand the result.
What evidence means here
Evidence can be as simple as a readiness state, a generated configuration file, a run log, a version stamp, or a clear failure. The point is to reduce ambiguity before and after a change.
- Readiness before action.
- Clear approvals before risky operations.
- Run history that distinguishes success, failure, and skipped work.
- Exportable output that supports review and handover.
Why it matters
Infrastructure automation often fails socially before it fails technically. If people cannot see what it intends to do, they will not trust it. Evidence gives automation a shape that can be discussed.