A key’s day

Part 7 recap · Response

Response: the short version

A fix is a claim until a fresh check proves the old key is dead and every app still works.

Take the full lesson

Where the copies are

Issued by the payment service, kept in the vault, then 3 copies:

  1. Git history, checkout repository
  2. CI build log
  3. Jira ticket comment

The day, step by step

  1. The queue · 9:00 AM Four findings wait in the queue.
  2. Verify · 9:20 AM Sort the queue by what each check proved.
  3. Analyze · 9:40 AM Write down what is known, and what isn’t.
  4. Find the owner · 10:35 AM Who owns it? Five people, three handoffs.
  5. Coordinate · 11:30 AM Three apps depend on it. Line them up first.
  6. Rotate · 2:10 PM Swap in a new key.
  7. Re-verify · 2:25 PM Re-verify the old key.
  8. App health · 3:00 PM Are the apps healthy? A separate question.
  9. Record · 3:15 PM Confirmed: the old key is dead. The record stays.

How it ended

Swap in a new key. A report that the key was rotated is a claim. The next step checks it.

Confirmed: the old key is dead. The record stays. The record shows what was proven, what is still open, and how long each part took, without claiming more than the checks showed.

Keep going