<title>ALLEN LORCH // OPS-LOG 001 — systems, triage, and the machines that degrade gracefully</title>
<metaproperty="og:type"content="website">
<metaproperty="og:title"content="ALLEN LORCH // OPS-LOG 001 — systems, triage, and the machines that degrade gracefully">
<metaproperty="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.">
<metaname="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;}
<divclass="kicker">Allen Lorch · IT Support Specialist · aspiring sysadmin · Burlington, MA</div>
<h1>OP LOG 001</h1>
<pclass="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>
<spanclass="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>
<imgsrc="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>
<h2id="essay"><spanclass="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>
<h2id="agc"><spanclass="num">§02</span> THE AGC AS A MONITORING LESSON</h2>
<divclass="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>
<divclass="fortlet-block">
<h3>Live knowledge graph — Apollo Guidance Computer</h3>
<fort-kgquery="apollo-guidance-computer"limit="5"><ulclass="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>
<divclass="fortlet-block">
<h3>Live news — NASA</h3>
<fort-newstopic="NASA"limit="3"><ulclass="fort-news"data-fort="news"data-topic="NASA"><li><ahref="https://www.dongascience.com:443/ko/news/79518"rel="noopener">NASA '추락하는 우주망원경' 구조 실패…연말 대기권서 소멸</a><spanclass="src">dongascience.com</span></li><li><ahref="http://www.newzealandstar.com/news/279255068/miyu-yamashita-cards-8-under-62-and-leads-by-1-in-edmonton"rel="noopener">newzealandstar.com</a><spanclass="src">newzealandstar.com</span></li><li><ahref="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><spanclass="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>
<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>
<h2id="lattice"><spanclass="num">§04</span> WHAT I KNOW (LATTICE)</h2>
<divclass="fortlet-block">
<h3>My second brain, live</h3>
<fort-mindlimit="8"><ulclass="fort-mind"data-fort="mind"><li><spanclass="fm-name">First film: 45s hyperframe short on AGC Alarm 1201 as IT triage protocol</span><spanclass="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>
<h2id="neighbors"><spanclass="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>
<spanclass="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.
