Enterprise Operations Workflow Demo

An SRE team needs a structured postmortem after a production database failover caused a 47-minute service degradation affecting API response times across three regions. The output must follow blameless review conventions, separate root cause from contributing factors, assign corrective actions with owners, and avoid language that attributes fault to individuals. This is an illustrative walkthrough, not a customer case study or a recorded run.

Configuration

Layer	Selection
Vertical	Enterprise Operations
Template	Incident Postmortem Report (`incident_postmortem`)
Style profile	Developer Experience Writer (`developer_experience_writer`)
Required inputs	Incident Title; Incident Date; Severity; Affected Services; Customer / User Impact; Incident Summary
Length	1,200–3,500 words

What this run is checked against

Check	For this run
Sources	Research must return at least 3 usable sources, or no draft is written.
Disclaimers	1 mandatory, inserted if missing and confirmed at the Quality Gate.
Forbidden claims	4, such as “guaranteed ROI”, “zero risk”, “no approval needed”. Any one blocks the draft.
Domain verification	`enterprise.availability`, `common.quantities`, advisory: findings are recorded, not blocking.
Required sections	Incident summary; Severity and impact; Detection and response; Timeline; Root cause analysis; Contributing factors; Remediation completed; Corrective actions; Owners and due dates; Lessons learned. Recorded at the Quality Gate; a missing section does not block on its own.

Every result above is written to the document’s passport, with an unverifiable result recorded as such rather than as a pass.

Other combinations for this work

Use case	Template	Style profile
Repeatable process documentation	Standard Operating Procedure	Developer Experience Writer
Customer onboarding program	Customer Onboarding Guide	Knowledge Base Support Writer
Org-wide tooling migration	Change Management Plan	Executive Summary
Channel partner activation	Partner Enablement Kit	Campaign Strategist

Example brief

Field	Example value
Incident type	Production database failover
Duration	47 minutes
Impact	API response time degradation across three regions
Affected systems	Primary database cluster, API gateway, downstream services
Audience	Engineering, SRE, and leadership teams
Output	Blameless postmortem with timeline and action items

Illustrative excerpt

Written for this page to show the expected shape and register. It is not output from a recorded run, and its figures and claims are not sourced.

# Incident Postmortem: Database Failover — [Date]

**Duration:** 47 minutes
**Impact:** API response time degradation across three regions
**Status:** Resolved

## Summary

A primary database cluster failover triggered cascading latency across the API gateway and downstream services. Automated failover completed successfully but took longer than expected due to connection pool exhaustion during the switchover window.

## Contributing Factors

- Connection pool limits were not sized to handle failover surge traffic
- Health check intervals did not detect degraded read replica state before promotion
- Runbook for this failure class had not been updated following last quarter's infrastructure changes

Enterprise Operations content is structured for internal use. Outputs are operational drafts intended for team review, wiki publication, or direct deployment. No external distribution is assumed.

Vertical rules

Everything this vertical enforces, and what its verifiers do not establish.

Asset Dossier

Where a run’s checks, sources, and approvals are recorded.

​Configuration

​What this run is checked against

​Other combinations for this work

​Example brief

​Illustrative excerpt

​Related pages

Vertical rules

Asset Dossier

Configuration

What this run is checked against

Other combinations for this work

Example brief

Illustrative excerpt

Related pages