<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Incidents on Agent-Native Ops</title>
    <link>https://jaredl.dev/tags/incidents/</link>
    <description>Recent content in Incidents on Agent-Native Ops</description>
    <image>
      <title>Agent-Native Ops</title>
      <url>https://jaredl.dev/posts/slack-native-ai-oncall-agent/thumbnail.png</url>
      <link>https://jaredl.dev/posts/slack-native-ai-oncall-agent/thumbnail.png</link>
    </image>
    <generator>Hugo -- 0.147.7</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 06 Sep 2026 11:33:56 +0800</lastBuildDate>
    <atom:link href="https://jaredl.dev/tags/incidents/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Five Phases of AI Agency: Which Decision You Moved Into the Agent</title>
      <link>https://jaredl.dev/posts/five-phases-of-ai-agency/</link>
      <pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://jaredl.dev/posts/five-phases-of-ai-agency/</guid>
      <description>Agent maturity isn&amp;#39;t how autonomous a system sounds — it&amp;#39;s which decision boundary you moved from human or code into the agent. Five phases, five boundaries.</description>
    </item>
    <item>
      <title>What Customers Want When Things Break: An On-Call Reframe</title>
      <link>https://jaredl.dev/posts/what-customers-want-when-things-break/</link>
      <pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate>
      <guid>https://jaredl.dev/posts/what-customers-want-when-things-break/</guid>
      <description>Customers want four things when things break — service works, fix fast, informed, no repeats. Every on-call layer reorganizes when the responder isn&amp;#39;t human.</description>
    </item>
    <item>
      <title>The Self-Evolving Triage Agent</title>
      <link>https://jaredl.dev/posts/self-evolving-triage-agent/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <guid>https://jaredl.dev/posts/self-evolving-triage-agent/</guid>
      <description>Two models, two jobs — one drafts triage responses, a different model audits every word and tool call. Patches self-validate, then a human cherry-picks.</description>
    </item>
    <item>
      <title>Two Boundaries: Redact Before You Prompt, Sanitize Before You Render</title>
      <link>https://jaredl.dev/posts/two-boundaries-redact-and-sanitize/</link>
      <pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://jaredl.dev/posts/two-boundaries-redact-and-sanitize/</guid>
      <description>The LLM sits between two boundaries — redact sensitive strings before you prompt, and treat output as attacker-controlled once prompt injection is on the table.</description>
    </item>
    <item>
      <title>Pre-filter, Classify, Triage: A Three-Stage Funnel for Token Budget</title>
      <link>https://jaredl.dev/posts/prefilter-classify-triage-funnel/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://jaredl.dev/posts/prefilter-classify-triage-funnel/</guid>
      <description>A cheap classifier should pay for the expensive investigator. Three stages — pre-filter, classify, triage — match cost to value on a mixed-value alert queue.</description>
    </item>
    <item>
      <title>Investigate Locally, Triage Server-Side</title>
      <link>https://jaredl.dev/posts/investigate-locally-triage-server-side/</link>
      <pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://jaredl.dev/posts/investigate-locally-triage-server-side/</guid>
      <description>Same triage agent, two deployment shapes — wide-open MCP locally for exploration, narrow direct-API client server-side for fast first-answer.</description>
    </item>
    <item>
      <title>Context Engineering for Operational AI Agents</title>
      <link>https://jaredl.dev/posts/context-engineering-operational-ai-agents/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://jaredl.dev/posts/context-engineering-operational-ai-agents/</guid>
      <description>Four techniques for context engineering operational AI agents — public MCPs, custom MCPs, CLI skills, bundling — turning a setup into a team asset.</description>
    </item>
    <item>
      <title>The Slack-Native AI On-Call Agent That Stands Shift With You</title>
      <link>https://jaredl.dev/posts/slack-native-ai-oncall-agent/</link>
      <pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://jaredl.dev/posts/slack-native-ai-oncall-agent/</guid>
      <description>An AI co-oncall pattern — the agent investigates in parallel and writes findings to a Slack thread, so the engineer arrives at a running log, not a blank slate.</description>
    </item>
    <item>
      <title>Time to Customer Awareness: the Incident KPI No One Measures</title>
      <link>https://jaredl.dev/posts/time-to-customer-awareness/</link>
      <pubDate>Sun, 01 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://jaredl.dev/posts/time-to-customer-awareness/</guid>
      <description>TTC-Aware is the window between customer impact and customer communication — where trust is earned or burned, and almost nobody measures it.</description>
    </item>
    <item>
      <title>Measuring PagerDuty Alert Noise: A Diagnostic Framework</title>
      <link>https://jaredl.dev/posts/measuring-pagerduty-alert-noise/</link>
      <pubDate>Thu, 01 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://jaredl.dev/posts/measuring-pagerduty-alert-noise/</guid>
      <description>Diagnose why an alert is noisy using three temporal axes — frequency, inter-event time, and resolution time — so the fix matches the cause.</description>
    </item>
  </channel>
</rss>
