Evidence packs that survive a service rename
Service renames scramble evidence trails if filenames and narratives still reference retired names. Adopt a stable identifier in your internal catalog and mention friendly names as aliases. When a rename ships, append a short addendum to the evidence index rather than rewriting history.
Train reviewers to follow identifiers first, diagrams second. Include a changelog table with dates and links to deployment tickets. This approach reduces duplicate requests when teams reorganize.
If you use infrastructure-as-code repositories, tag releases used for evidence snapshots. The tag becomes the durable pointer even when resource labels shift. Pair tags with human-readable summaries in your narrative.