Turns a messy timeline into a postmortem that blames the system
Everyone agrees postmortems should be blameless, and most are not. Not from bad intent: at midnight, "the config push at 17:40" is the easiest true sentence to write, and once a person is on the page the document stops being about the system.
This agent cannot name a person. It reconstructs the timeline from your logs, alerts and chat, separates what happened from what was believed at the time, and asks the questions that find systemic causes — why the alert did not fire, why the rollback took nine minutes, why the config could be pushed unreviewed at all.
Its action items are specific and testable, and it marks the ones that are really wishes. "Be more careful" is not an action item; "require review on production config changes" is. And it separates what is known from what is assumed, so next month nobody mistakes a theory in the document for an established fact.
A postmortem written a week later is a reconstruction.
Nothing in it can be read as an accusation.
Testable items instead of resolutions.
A hard rule, not a tone preference. It refers to roles and systems, which is what keeps it blameless.
What was true, and what responders thought at the time. Both matter, and confusing them is how myths start.
Not what triggered it — what made a trigger sufficient to cause an outage.
Each one has an owner role and a check for whether it worked. "Be more careful" is marked as a wish.
How long until anyone knew, and what made recovery slower than it needed to be.
An unresolved question is a finding, not a hole to fill with a theory.
This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.
Demo dataIllustrative sample output, abridged.
{
"severity": "SEV2",
"timeline": "…",
"incidentReference": "INC-402"
}{
"summary": "A configuration change reduced the connection pool below what peak traffic required. Requests queued, then timed out. Service was restored by reverting the change.",
"escalate": false,
"unknowns": [
"Why the pool size was reduced. The record does not say, and the change carried no description."
],
"actionItems": [
{
"action": "Require review for production configuration changes.",
"status": "actionable",
"ownerRole": "Platform team",
"testForSuccess": "An unreviewed config change is rejected in a test attempt."
},
{
"action": "Be more careful with configuration.",
"status": "not-actionable",
"ownerRole": "—",
"testForSuccess": "None possible."
}
],
"recoveryGap": "9 minutes of the 14-minute recovery was the redeploy. A config rollback would have been under a minute.",
"detectionGap": "23 minutes from first failed request to anyone knowing. The signal came from customers, not monitoring.",
"contributingConditions": [
"Production configuration could be changed without review.",
"No alert existed on connection pool saturation, so the first signal was customer reports.",
"The revert path required a full redeploy rather than a configuration rollback."
]
}No integrations required.
Turn the incident channel into a document in minutes.
Find the cause the last three postmortems missed.
A factual basis for what you tell customers, without internal detail.
$129/month
Billed monthly through your PROMIVO subscription. Cancel at any time.
Runs consume your plan allowance for agent executions and tokens. See plan limits.
Because if a person can cause an outage alone, the system allowed it, and that is the finding. Naming them ends the investigation early and teaches everyone else to be quieter during the next incident.
It can draft the factual basis, without internal system detail. Whether and how to communicate an incident is a decision with commercial and legal weight, and stays with a person.
It marks the gaps as unknown and lists what to check. A postmortem with a confidently invented middle is worse than one with an honest hole.
No reviews yet. Reviews open once customers have run this agent.
Tell us what to change and our team will scope a customised version for your business.
Customize this agent