Articles

Establish the evidence boundary before comparing defaults A configuration documentation maintainer needs to compare an authorised application snapshot, its sample configuration, and its published setup guidance; record apparent default mismatches with origin, precedence, uncertainty, and reviewer action; and make no edit, service execution, access change, or production decision. This playbook…

1. Set the evidence boundary before discovery A migration assessment should begin with an agreed question, not a list of search matches. The question here is deliberately narrow: at one named repository commit, where is one approved library or application programming interface used directly or indirectly, what authoritative deprecation evidence…