Extremely hard disagree. The status page is exactly where you communicate about both the root cause, and the action plan to prevent it. Every status page incid

Extremely hard disagree. The status page is exactly where you communicate about both the root cause, and the action plan to prevent it. Every status page incident on every normal company everywhere in the world has links to lead you to the postmortem and their steps to avoid it. Here are a few examples: https://status.gitlab.com/ https://status.gitlab.com/ -> https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7 https://status.gitlab.com/pages/history/5b36dc6502d06804c083... https://status.hetzner.com/ https://status.hetzner.com/ -> https://status.hetzner.com/incident/2e715748-fddd-427b-a07b-b34a5a9edee3 https://status.hetzner.com/incident/2e715748-fddd-427b-a07b-... https://www.githubstatus.com/ https://www.githubstatus.com/ -> https://www.githubstatus.com/incidents/mj067hg9slb4 https://www.githubstatus.com/incidents/mj067hg9slb4 https://bitbucket.status.atlassian.com/ https://bitbucket.status.atlassian.com/ -> https://bitbucket.status.atlassian.com/incidents/4mcg46242wz4 https://bitbucket.status.atlassian.com/incidents/4mcg46242wz... It's literally a standard for your status page to communicate both about root cause and action plan how to prevent it in the future. Sure, when an incident is just happening, the status page entry doesn't have the postmortem and the steps to avoid, but later on those get added. Being so overconfidently wrong reminds me of an LLM.