Show HN：IncidentPost – 運用極簡工具生成 AI 驅動的事件事後分析報告

I built IncidentPost (https://incidentpost.vect.pro
) to help engineers and SREs ship clear, public incident postmortems without heavy internal tooling or manual writing stress. Many teams struggle to format timelines, summarize root causes, and produce shareable reports after outages — especially under time pressure.

What it does:

Paste a raw timeline (Slack logs, timestamps, alerts)

Generates a structured report with executive summary, root cause analysis, timeline, mitigations, and action items

Produces a public URL, Markdown/HN post draft, and Twitter thread you can publish instantly

No accounts or complex onboarding to read public reports — minimal barriers for transparency

Why this matters:

Public postmortems improve trust and engineering processes

Automates hours of writing into minutes

Keeps focus on incident resolution, not documentation

It’s early, feedback-driven, and intentionally minimal. I’d really appreciate thoughts from engineers, SREs, or founders who deal with reliability and postmortems:
What’s missing? What feels necessary? Would you use something like this?