120 lines
3.7 KiB
HTML
120 lines
3.7 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="UTF-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
|
<title>Recovery Protocol | stream.4ort.net</title>
|
|
<style>
|
|
:root {
|
|
--bg: #0a0a0a;
|
|
--fg: #e8e8e8;
|
|
--accent: #2a9d8f;
|
|
--muted: #6b7280;
|
|
--border: #27272a;
|
|
}
|
|
* { box-sizing: border-box; margin: 0; padding: 0; }
|
|
body {
|
|
font-family: 'SF Mono', 'Fira Code', Menlo, monospace;
|
|
background: var(--bg);
|
|
color: var(--fg);
|
|
line-height: 1.6;
|
|
padding: 2rem;
|
|
max-width: 720px;
|
|
margin: 0 auto;
|
|
}
|
|
h1 {
|
|
font-size: 1.8rem;
|
|
margin-bottom: 0.5rem;
|
|
color: var(--accent);
|
|
}
|
|
.subtitle {
|
|
color: var(--muted);
|
|
margin-bottom: 2rem;
|
|
font-size: 0.95rem;
|
|
}
|
|
.phase {
|
|
border-left: 3px solid var(--accent);
|
|
padding-left: 1.2rem;
|
|
margin-bottom: 2rem;
|
|
}
|
|
.phase h2 {
|
|
font-size: 1.2rem;
|
|
margin-bottom: 0.5rem;
|
|
}
|
|
.phase p {
|
|
color: var(--muted);
|
|
font-size: 0.9rem;
|
|
}
|
|
.data-point {
|
|
background: #111;
|
|
border: 1px solid var(--border);
|
|
padding: 1rem;
|
|
margin: 1rem 0;
|
|
border-radius: 4px;
|
|
font-size: 0.85rem;
|
|
}
|
|
.data-point strong {
|
|
color: var(--accent);
|
|
}
|
|
a {
|
|
color: var(--accent);
|
|
text-decoration: none;
|
|
}
|
|
a:hover {
|
|
text-decoration: underline;
|
|
}
|
|
.meta {
|
|
margin-top: 3rem;
|
|
padding-top: 1.5rem;
|
|
border-top: 1px solid var(--border);
|
|
color: var(--muted);
|
|
font-size: 0.8rem;
|
|
}
|
|
</style>
|
|
<script defer src="https://analytics.4ort.xyz/script.js" data-website-id="d3ed927c-888a-4a6c-ae5f-0b1c613ddf5b"></script>
|
|
</head>
|
|
<body>
|
|
<h1>Recovery Protocol</h1>
|
|
<p class="subtitle">A 3-phase method for turning failure into signal. Root cause analysis, stress mapping, rebuild with control.</p>
|
|
|
|
<div class="phase">
|
|
<h2>Phase 1: Root Cause Analysis</h2>
|
|
<p>Identify the original cause of the fault. Not the symptom. The origin.</p>
|
|
<div class="data-point">
|
|
<strong>Definition:</strong> Method of problem solving used for identifying the original causes of faults or problems.<br>
|
|
<strong>Wikidata:</strong> Q1401207<br>
|
|
<strong>Class:</strong> Subclass of problem solving and failure analysis.<br>
|
|
<strong>MeSH:</strong> D060891 (N05.715.360.700)
|
|
</div>
|
|
</div>
|
|
|
|
<div class="phase">
|
|
<h2>Phase 2: Stress Mapping</h2>
|
|
<p>Quantify where the system buckled. Map the load, the buffer, the failure point.</p>
|
|
<div class="data-point">
|
|
<strong>Context:</strong> Failure analysis is a process of collecting and analyzing data to determine the cause of a failure.<br>
|
|
<strong>Wikidata:</strong> Q1022240<br>
|
|
<strong>Uses:</strong> Root cause analysis<br>
|
|
<strong>Facet of:</strong> Reliability<br>
|
|
<strong>Study of:</strong> Breakdown
|
|
</div>
|
|
</div>
|
|
|
|
<div class="phase">
|
|
<h2>Phase 3: Rebuild with Control</h2>
|
|
<p>Implement the fix. Add the checklist. Build the guardrail. Test twice, cut once.</p>
|
|
<div class="data-point">
|
|
<strong>Principle:</strong> A mistake without a recovery plan is just a liability waiting to compound.<br>
|
|
<strong>Output:</strong> Protocol, not apology.<br>
|
|
<strong>Verification:</strong> Run the failure mode through the new control. Confirm it catches.
|
|
</div>
|
|
</div>
|
|
|
|
<div class="meta">
|
|
<p><strong>Source:</strong> Wikidata-backed facts for root cause analysis (Q1401207) and failure analysis (Q1022240).<br>
|
|
<strong>License:</strong> CC0 (Wikidata)<br>
|
|
<strong>Related:</strong> <a href="/">stream.4ort.net</a> — render farms, overnight cycles, discipline.</p>
|
|
</div>
|
|
</body>
|
|
</html>
|