<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Corpus-Analysis on Revelara</title><link>https://revelara.ai/tags/corpus-analysis/</link><description>Recent content in Corpus-Analysis on Revelara</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 10 May 2026 08:00:00 -0700</lastBuildDate><atom:link href="https://revelara.ai/tags/corpus-analysis/index.xml" rel="self" type="application/rss+xml"/><item><title>The Medium-Severity Paradox: Where Engineering Time Actually Goes</title><link>https://revelara.ai/blog/medium-severity-paradox-corpus-analysis/</link><pubDate>Sun, 10 May 2026 08:00:00 -0700</pubDate><guid>https://revelara.ai/blog/medium-severity-paradox-corpus-analysis/</guid><description>&lt;p&gt;The average critical-severity incident in the Revelara corpus takes about 19 hours to resolve. The average medium-severity incident takes about 17 hours. On those two numbers alone, the natural conclusion is that critical incidents are roughly where engineering time goes, and that medium-severity work is the manageable middle. The conclusion is wrong by roughly an order of magnitude, and the data shows why.&lt;/p&gt;
&lt;h2 id="the-numbers-and-how-the-analysis-was-run"&gt;The numbers, and how the analysis was run&lt;/h2&gt;
&lt;p&gt;This analysis pulls from the Revelara public postmortem corpus, which currently spans nearly 3,000 published incidents and grows daily. Two severity-targeted comparisons were run. The &amp;ldquo;critical&amp;rdquo; set returned 272 incidents matching body language like SEV1, P0, total outage, and major. The &amp;ldquo;medium&amp;rdquo; set returned 284 incidents matching SEV3, P2, degraded, and partial.&lt;/p&gt;</description></item></channel></rss>