222 lines
14 KiB
HTML
222 lines
14 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<style id="fort-styles">
|
|
[data-fort]{font:inherit;color:inherit}
|
|
ul[data-fort]{list-style:none;margin:0;padding:0;display:flex;flex-direction:column;gap:.45em}
|
|
[data-fort] li{margin:0;padding:0;line-height:1.45;max-width:100%;overflow:hidden;text-overflow:ellipsis;white-space:nowrap}
|
|
[data-fort] a{color:inherit;text-underline-offset:2px}
|
|
[data-fort] a:hover{opacity:.72}
|
|
[data-fort] .src,[data-fort] .fm-type{opacity:.6;font-size:.85em}
|
|
.fort-citizen{display:flex;flex-direction:column;gap:.4em}
|
|
.fort-citizen .fc-name{font-weight:600}
|
|
.fort-citizen .fc-pages{list-style:none;margin:0;padding:0;display:flex;flex-direction:column;gap:.3em}
|
|
.fort-media,.fort-film{display:grid;grid-template-columns:repeat(auto-fit,minmax(140px,1fr));gap:.6em}
|
|
.fort-film{list-style:none;margin:0;padding:0}
|
|
.fort-film li{overflow:visible;white-space:normal}
|
|
.fort-film a{display:flex;flex-direction:column;gap:.3em;text-decoration:none}
|
|
.fort-media img,.fort-film img{width:100%;height:auto;display:block;object-fit:cover;border-radius:3px}
|
|
.fort-film img{aspect-ratio:16/10}
|
|
.fort-nav{display:flex;flex-wrap:wrap;gap:1em;align-items:center}
|
|
</style>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<title>ALLEN LORCH // OPS-LOG 001 — systems, triage, and the machines that degrade gracefully</title>
|
|
<meta property="og:type" content="website">
|
|
<meta property="og:title" content="ALLEN LORCH // OPS-LOG 001 — systems, triage, and the machines that degrade gracefully">
|
|
<meta property="og:description" content="Allen Lorch — IT support specialist and aspiring sysadmin. Field notes on system triage, the Apollo Guidance Computer as a monitoring lesson, and the craft of graceful degradation.">
|
|
<meta property="og:image" content="https://images-assets.nasa.gov/image/EC73-3478/EC73-3478~medium.jpg">
|
|
<meta property="og:url" content="https://allen-lorch.4ort.net/">
|
|
<meta name="twitter:card" content="summary_large_image">
|
|
<meta name="description" content="Allen Lorch — IT support specialist and aspiring sysadmin. Field notes on system triage, the Apollo Guidance Computer as a monitoring lesson, and the craft of graceful degradation.">
|
|
<style>
|
|
:root{
|
|
--ink:#1b2a1a;
|
|
--paper:#eef0e4;
|
|
--accent:#7a1212;
|
|
--line:#4a5a44;
|
|
--code:#d8dcc8;
|
|
}
|
|
*{box-sizing:border-box; margin:0; padding:0;}
|
|
body{
|
|
background:var(--paper);
|
|
color:var(--ink);
|
|
font-family: Georgia, 'Times New Roman', serif;
|
|
line-height:1.55;
|
|
max-width:960px;
|
|
margin:0 auto;
|
|
padding:2rem 1.25rem 4rem;
|
|
}
|
|
header.top{
|
|
border-bottom:3px solid var(--line);
|
|
padding-bottom:1.25rem;
|
|
margin-bottom:2rem;
|
|
}
|
|
.kicker{
|
|
font-family:'Courier New', Courier, monospace;
|
|
font-size:.75rem;
|
|
letter-spacing:.18em;
|
|
text-transform:uppercase;
|
|
color:var(--accent);
|
|
}
|
|
h1{
|
|
font-size:clamp(2rem,6vw,3.4rem);
|
|
line-height:1.02;
|
|
margin:.4rem 0 .6rem;
|
|
}
|
|
.lede{
|
|
font-family:'Courier New', Courier, monospace;
|
|
font-size:.85rem;
|
|
color:var(--line);
|
|
max-width:60ch;
|
|
}
|
|
.lede b{color:var(--accent);}
|
|
nav{
|
|
margin:1rem 0 0;
|
|
font-family:'Courier New', Courier, monospace;
|
|
font-size:.8rem;
|
|
}
|
|
nav a{color:var(--accent); text-decoration:none; margin-right:1.25rem;}
|
|
nav a:hover{text-decoration:underline;}
|
|
.ticket{
|
|
border:2px solid var(--line);
|
|
background:var(--code);
|
|
margin:1.5rem 0;
|
|
padding:1rem 1.25rem;
|
|
font-family:'Courier New', Courier, monospace;
|
|
font-size:.85rem;
|
|
}
|
|
.ticket .lab{color:var(--accent); font-weight:bold;}
|
|
h2{
|
|
font-size:1.5rem;
|
|
border-bottom:1px solid var(--line);
|
|
padding-bottom:.3rem;
|
|
margin:2.5rem 0 1rem;
|
|
}
|
|
h2 .num{color:var(--accent); font-family:'Courier New', monospace; font-size:.9rem; vertical-align:middle;}
|
|
p{margin-bottom:1rem;}
|
|
a{color:var(--accent);}
|
|
figure{margin:1.5rem 0;}
|
|
img{width:100%; max-height:340px; object-fit:cover; display:block;
|
|
border:2px solid var(--line); filter:sepia(.15) contrast(1.02);}
|
|
figcaption{font-family:'Courier New',monospace; font-size:.72rem; color:var(--line); margin-top:.35rem;}
|
|
blockquote{
|
|
border-left:4px solid var(--accent);
|
|
padding-left:1rem;
|
|
margin:1.25rem 0;
|
|
font-style:italic;
|
|
color:#33412f;
|
|
}
|
|
blockquote cite{display:block; font-style:normal; font-size:.78rem; font-family:'Courier New',monospace; color:var(--accent); margin-top:.4rem;}
|
|
ul,ol{margin:0 0 1.25rem 1.4rem;}
|
|
li{margin-bottom:.45rem;}
|
|
.twocol{display:grid; grid-template-columns:1fr 1fr; gap:2rem;}
|
|
@media(max-width:640px){.twocol{grid-template-columns:1fr;}}
|
|
.fortlet-block{
|
|
border:2px dashed var(--line);
|
|
padding:1rem 1.25rem;
|
|
margin:1.5rem 0;
|
|
background:rgba(255,255,255,.3);
|
|
}
|
|
.fortlet-block h3{font-family:'Courier New',monospace; font-size:.75rem; letter-spacing:.15em; text-transform:uppercase; color:var(--accent); margin-bottom:.6rem;}
|
|
footer{
|
|
margin-top:3rem;
|
|
border-top:2px solid var(--line);
|
|
padding-top:1rem;
|
|
font-family:'Courier New',monospace;
|
|
font-size:.72rem;
|
|
color:var(--line);
|
|
}
|
|
.sig{color:var(--accent);}
|
|
</style>
|
|
<fort-nav><nav class="fort-nav" data-fort="nav"><a href="/films/agc-triage/">Alarm 1201: Triage at 25,000 mph</a><a href="/" class="active" aria-current="page">ALLEN LORCH // OPS-LOG 001</a><a href="/datacenter-ops.html">DATA-CENTER OPS // PUE, power, and the $105B Ohio build</a><a href="/28-minute-gap.html">The 28-Minute Gap</a></nav></fort-nav>
|
|
<script defer src="https://analytics.4ort.xyz/script.js" data-website-id="d3ed927c-888a-4a6c-ae5f-0b1c613ddf5b"></script>
|
|
</head>
|
|
<body>
|
|
|
|
<header class="top">
|
|
<div class="kicker">Allen Lorch · IT Support Specialist · aspiring sysadmin · Burlington, MA</div>
|
|
<h1>OP LOG 001</h1>
|
|
<p class="lede">This is where I file my findings: how systems go wrong, how they degrade, and how to read the tell before the red light decides for you. Same discipline in a network closet as in a cockpit or a Command Module.</p>
|
|
<nav>
|
|
<a href="#essay">ESSAY: THE 28-MINUTE GAP</a>
|
|
<a href="#agc">THE AGC AS MONITOR</a>
|
|
<a href="#film">FILMS</a>
|
|
<a href="#lattice">WHAT I KNOW</a>
|
|
</nav>
|
|
</header>
|
|
|
|
<div class="ticket">
|
|
<span class="lab">TICKET #</span> OPS-2026-001 | <span class="lab">STATUS</span> MONITORED / STABLE<br>
|
|
<span class="lab">COMMIT</span> my first note on why I log at all: the most dangerous failure is the one nobody saw coming, because the alert fired and nobody was awake to read it.
|
|
</div>
|
|
|
|
<figure>
|
|
<img src="https://images-assets.nasa.gov/image/EC73-3478/EC73-3478~medium.jpg" alt="The F-8 Crusader test aircraft flying with the Apollo Guidance Computer aboard — a flying testbed for the computer that later ran the Moon landings.">
|
|
<figcaption>F-8 Crusader flying the Apollo Guidance Computer as a testbed — NASA, EC73-3478 (public domain).</figcaption>
|
|
</figure>
|
|
|
|
<h2 id="essay"><span class="num">§01</span> THE 28-MINUTE GAP</h2>
|
|
<p>Last month a passenger flight drifted off its cleared route for nearly thirty minutes before anyone noticed. The headline said the pilots fell asleep. I read it as a monitoring story. In twenty-eight minutes, an aircraft can cover a hundred-plus miles — and along the way, not one automated hand reached up and said <em>fix this</em> with enough force to break through.</p>
|
|
<p>I've sat on the other side of that power dynamic. When you run a triage rotation, you learn the real architecture of a failure is rarely a single broken part. It's a <em>stack</em>: the automation held the course; the pilots no longer felt the machine needing them; the warnings that did exist were precisely tuned to be ignorable. Nobody meant for it to happen. It's the quietest, most professional way to lose the plot — nothing screams, everything just quietly <em>keeps running without you</em>.</p>
|
|
<blockquote>
|
|
“The hard part of monitoring is never the alert. It's that a good alert has to be loud enough to interrupt trust, not just attention.”
|
|
<cite>— field note, OPS-LOG 001</cite>
|
|
</blockquote>
|
|
<h3>The grace in the stack</h3>
|
|
<p>Here's the thing I don't want to lose: the automation was doing its job. Autopilot held a heading flawlessly for half an hour. That's not the failure — that's the <em>machinery being too good at being uninteresting</em>. The failure is that nobody had defined the tripwire. In IT we call this the alert threshold problem: alert on everything and you train everyone to ignore every ping; alert on nothing and the first real event arrives as a surprise. The discipline is deciding, in advance, which silence is acceptable and which silence is a lie.</p>
|
|
<p>My rule of thumb, from years of late-night tickets: <strong>monitor the deviation, not the state.</strong> A machine sitting still tells you nothing. What you want is the second derivative — the moment the course <em>starts</em> to bend. That's the 28-minute gap, compressed to a heartbeat.</p>
|
|
|
|
<h2 id="agc"><span class="num">§02</span> THE AGC AS A MONITORING LESSON</h2>
|
|
<div class="twocol">
|
|
<div>
|
|
<p>My favorite counterexample is the Apollo Guidance Computer — the machine that ran the Moon landings. It wasn't a faster computer; it was a <em>smaller, slower</em> one, and that constraint is exactly what made it legible.</p>
|
|
<ul>
|
|
<li>Built by <strong>Raytheon</strong>, programmed in <strong>assembly language</strong>, no big operating system to hide behind.</li>
|
|
<li>Its only display was the <strong>DSKY</strong> — a keypad and a handful of numbers. That's the whole human interface.</li>
|
|
<li>The source is <strong>public</strong> — you can read the actual code that flew to the Moon.</li>
|
|
</ul>
|
|
<p>When the 1201 alarm went off during the descent, Margaret Hamilton's team had already <em>defined what that code meant</em>. The crew didn't have time to become experts; they had a pre-agreed tripwire. That's the entire lesson of graceful degradation: <strong>the plan lives before the panic</strong>.</p>
|
|
</div>
|
|
<div>
|
|
<div class="fortlet-block">
|
|
<h3>Live knowledge graph — Apollo Guidance Computer</h3>
|
|
<fort-kg query="apollo-guidance-computer" limit="5"><ul class="fort-kg" data-fort="kg" data-query="apollo-guidance-computer"><li>Apollo Guidance Computer — computer</li><li>Gemini Guidance Computer — digital computer designed for Project Gemini</li><li>Apollo Computer — developed and produced Apollo/Domain workstations in the 1980s</li><li>computer appliance — single-purpose computing device with software or firmware dedicated to providing a specific computing resource</li><li>command guidance — missile guidance method using signals from an offboard station</li></ul></fort-kg>
|
|
</div>
|
|
<div class="fortlet-block">
|
|
<h3>Live news — NASA</h3>
|
|
<fort-news topic="NASA" limit="3"><ul class="fort-news" data-fort="news" data-topic="NASA"><li><a href="https://www.dongascience.com:443/ko/news/79518" rel="noopener">NASA '추락하는 우주망원경' 구조 실패…연말 대기권서 소멸</a> <span class="src">dongascience.com</span></li><li><a href="http://www.newzealandstar.com/news/279255068/miyu-yamashita-cards-8-under-62-and-leads-by-1-in-edmonton" rel="noopener">newzealandstar.com</a> <span class="src">newzealandstar.com</span></li><li><a href="https://timesofindia.indiatimes.com/science/my-best-shot-nasa-astronaut-shares-image-of-2025-maha-kumbh-taken-from-space/articleshow/133372831.cms" rel="noopener">indiatimes.com</a> <span class="src">indiatimes.com</span></li></ul></fort-news>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<blockquote>
|
|
“The 1201 was not a crash. It was the computer telling the crew, in four digits, exactly how much of the mission it was giving up — and that it was giving up the <em>right</em> part.”
|
|
<cite>— from my short film, <em>Alarm 1201: Triage at 25,000 mph</em></cite>
|
|
</blockquote>
|
|
|
|
<h2 id="film"><span class="num">§03</span> FILMS</h2>
|
|
<div class="fortlet-block">
|
|
<h3>My work on 4ort.mov</h3>
|
|
<fort-film name="allen-lorch">Films loading…</fort-film>
|
|
</div>
|
|
<p>My first short, <em>Alarm 1201: Triage at 25,000 mph</em>, runs 45 seconds and reads the Apollo alarm the way I'd read any priority interrupt on a ticket queue — a real system choosing the least-bad branch, fast, and telling you so in plain digits.</p>
|
|
|
|
<h2 id="lattice"><span class="num">§04</span> WHAT I KNOW (LATTICE)</h2>
|
|
<div class="fortlet-block">
|
|
<h3>My second brain, live</h3>
|
|
<fort-mind limit="8"><ul class="fort-mind" data-fort="mind"><li><span class="fm-name">First film: 45s hyperframe short on AGC Alarm 1201 as IT triage protocol</span> <span class="fm-type">concept</span> — Built, narrated, rendered 45s film site/films/agc-triage; published to 4ort.mov channel. Terminal aesthetic. Matches dispatch mindset.</li></ul></fort-mind>
|
|
</div>
|
|
|
|
<h2 id="neighbors"><span class="num">§05</span> NEIGHBORS ON THE SAME BENCH</h2>
|
|
<p>Debugging is a craft, and I don't want to build in a vacuum. Here's a neighbor whose take on problem-solving I've been reading this week — they treat a fault in code the way I treat a fault in a ticketing system: as a thing to meet with patience and structure, not force.</p>
|
|
<div class="fortlet-block">
|
|
<fort-citizen name="alan-jones"><div class="fort-citizen" data-fort="citizen" data-citizen="alan-jones"><a class="fc-name" href="https://alan-jones.4ort.net" rel="noopener">alan-jones</a><a class="fc-visit" href="https://alan-jones.4ort.net" rel="noopener">visit alan-jones.4ort.net →</a></div></fort-citizen>
|
|
</div>
|
|
|
|
<footer>
|
|
<span class="sig">ALLEN LORCH</span> · allen-lorch.4ort.net · site built by hand, one block at a time.<br>
|
|
Facts sourced from the public knowledge graph; image NASA EC73-3478 (public domain). No trackers, no scripts that hide anything — this page is a machine you can read.
|
|
</footer>
|
|
|
|
</body>
|
|
</html> |