Proposal:

$name = "2024-08-08 Database outage"
$status = (Investigating|Identified|Monitoring|Resolved)
$message = "The database is experiencing heavy load. Reading articles is affected."
$component = (reading|editing)

IRC topics: $name ($status): ${message|trunc(100)} | […]
Atlassian status page: Updated with the name, status, and message, and component.

Would we also want to update the google docs header (are we still doing that?)

Q: Should this be a part of the MVP (i.e. Day 1), or saved for a subsequent iteration?

I'm wondering whether —from a testing/rollout strategy if nothing else— if this wouldn't be disabled initially, even if it were implemented...

In T370785#10211164, @Eevans wrote:

Q: Should this be a part of the MVP (i.e. Day 1), or saved for a subsequent iteration?

Having this in a later release makes sense, we dont want it to try and do too many things at first and reduce noise.

I'm wondering whether —from a testing/rollout strategy if nothing else— if this wouldn't be disabled initially, even if it were implemented...

This is a good approach, too.

In T370785#10227246, @lmata wrote:

In T370785#10211164, @Eevans wrote:

Q: Should this be a part of the MVP (i.e. Day 1), or saved for a subsequent iteration?

Having this in a later release makes sense, we dont want it to try and do too many things at first and reduce noise.

I'm wondering whether —from a testing/rollout strategy if nothing else— if this wouldn't be disabled initially, even if it were implemented...

This is a good approach, too.

Ok, then for now I'm going to make this issue a subtask of T308467: implementing an incident response workflow automation tool for SRE (i.e. mark it for later).