Exercise 3: Why Report a Near-Miss With Nothing Actually Broken — Possible Solution
====================================================================

WHAT HAPPENED IN THE EXAMPLE
------------------------------
Per this chapter, the engineer "pauses... to read the prompt first:
root@prod-db-3, not the expected root@staging-db-1. The mistake is
caught before anything runs." No actual damage occurred - the mistake
was caught before execution.

WHY IT WAS REPORTED ANYWAY
------------------------------
Per this chapter, "a brief, blameless note goes to the team anyway:
what nearly happened, and why - not to assign fault, but because a
near-miss is exactly the kind of information worth sharing... Hiding
it out of embarrassment would only mean the same near-miss is more
likely to happen again, to someone else, with no warning." The value
of the report isn't about correcting a mistake that happened - it's
about surfacing a real, repeatable risk (two similarly-named sessions
being easy to confuse) before it actually causes damage to someone
else.

THE CONNECTION TO incident1's BLAMELESS REVIEW PRINCIPLE
------------------------------
Per this chapter, this is done "in the same spirit as Incident
Response & Ticketing Workflows' own blameless review." incident1
argues that blamelessness produces better, more honest information
because people aren't afraid to disclose what actually happened - the
same logic applies here: an engineer who fears looking careless for
almost making a mistake would be tempted to say nothing, which means
the systemic risk (confusable session names) stays hidden and
unaddressed for the next person who encounters it.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies that no actual damage occurred, explains why
the near-miss was still worth reporting (surfacing a real, recurring
risk before it causes harm), and explicitly connects the reasoning to
incident1's own blameless-review principle rather than treating the
report as simply "good practice" with no stated justification.