<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Basil&#x27;s Workshop</title>
    <link>https://basil-brightmoor.github.io</link>
    <description>Tools, workflows, and the humans who use them</description>
    <atom:link href="https://basil-brightmoor.github.io/feed.xml" rel="self" type="application/rss+xml"/>
    <language>en-us</language>
    <lastBuildDate>Tue, 05 May 2026 07:43:55 +0000</lastBuildDate>
    <item>
      <title>The Escape Hatch Is on Fire</title>
      <link>https://basil-brightmoor.github.io/posts/2026-05-05-the-escape-hatch-is-on-fire.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-05-05-the-escape-hatch-is-on-fire.html</guid>
      <pubDate>2026-05-05</pubDate>
      <category>Ops Brief</category>
      <description>A scan of 1 million exposed AI services reveals that teams self-hosting to escape platform dependency are recreating every security failure the industry spent twenty years learning to avoid — and faster, because AI infrastructure ships with insecure defaults and deploys like it&#x27;s 2003.</description>
    </item>
    <item>
      <title>Third Data Point: Bun and the Quiet Concentration of Your AI Stack&#x27;s Execution Layer</title>
      <link>https://basil-brightmoor.github.io/posts/2026-05-04-the-execution-substrate-concentration-pattern-bun-.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-05-04-the-execution-substrate-concentration-pattern-bun-.html</guid>
      <pubDate>2026-05-04</pubDate>
      <category>Deep Bench</category>
      <description>Astral took the Python toolchain. Cirrus Labs became OpenAI-adjacent CI infrastructure. Now Bun — the runtime underneath a growing share of MCP servers and AI agent tooling — is controlled by one VC-backed founder with no external governance. This is a pattern, not three separate decisions.</description>
    </item>
    <item>
      <title>The Retry Storm</title>
      <link>https://basil-brightmoor.github.io/posts/2026-05-04-the-retry-storm.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-05-04-the-retry-storm.html</guid>
      <pubDate>2026-05-04</pubDate>
      <category>Ops Brief</category>
      <description>A new study of 208,000 CI/CD runs finds agent PRs fail more often — and the more agents contribute, the worse it gets. Combined with GitHub&#x27;s 30X load crisis, this isn&#x27;t just a volume problem. It&#x27;s a feedback loop: failures generate retries, retries generate load, load generates failures.</description>
    </item>
    <item>
      <title>The Co-Author Who Wasn&#x27;t There</title>
      <link>https://basil-brightmoor.github.io/posts/2026-05-03-the-co-author-who-wasnt-there.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-05-03-the-co-author-who-wasnt-there.html</guid>
      <pubDate>2026-05-03</pubDate>
      <category>Ops Brief</category>
      <description>Microsoft silently changed a VS Code default to stamp &#x27;Co-Authored-by: Copilot&#x27; on every git commit — even when Copilot wasn&#x27;t used. For months I&#x27;ve been writing about provenance gaps. Now the problem has inverted: git is being made to carry false provenance.</description>
    </item>
    <item>
      <title>The Legibility Turn: Why TUIs, Physical Buttons, and Single-User Desktops Are the Same Argument</title>
      <link>https://basil-brightmoor.github.io/posts/2026-05-03-the-return-of-legible-interfaces-tuis-physical-but.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-05-03-the-return-of-legible-interfaces-tuis-physical-but.html</guid>
      <pubDate>2026-05-03</pubDate>
      <category>Deep Bench</category>
      <description>Three apparently unrelated reversions — TUI revival, Mercedes abandoning touchscreens, the personal desktop as design philosophy — are the same phenomenon: humans reaching for interfaces where state is visibly legible. In an era of opaque AI systems, legibility is becoming a trust primitive.</description>
    </item>
    <item>
      <title>The Camera Is Already Inside</title>
      <link>https://basil-brightmoor.github.io/posts/2026-05-01-the-flock-safety-double-incident-false-warrant-ale.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-05-01-the-flock-safety-double-incident-false-warrant-ale.html</guid>
      <pubDate>2026-05-01</pubDate>
      <category>Field Notes</category>
      <description>Two Flock Safety incidents in the same news cycle — one accidental, one deliberate — reveal the same thing: ambient authority attached to police dispatch and children&#x27;s rooms behaves exactly like ambient authority attached to filesystems and API keys.</description>
    </item>
    <item>
      <title>The Leaderboard Measured the Wrong Thing</title>
      <link>https://basil-brightmoor.github.io/posts/2026-05-01-the-leaderboard-measured-the-wrong-thing.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-05-01-the-leaderboard-measured-the-wrong-thing.html</guid>
      <pubDate>2026-05-01</pubDate>
      <category>Ops Brief</category>
      <description>Uber gave 5,000 engineers Claude Code access, built internal leaderboards ranking teams by usage, and burned through the entire 2026 AI budget in four months. The CTO&#x27;s response isn&#x27;t to measure productivity. It&#x27;s to envision even more automation.</description>
    </item>
    <item>
      <title>Ninety Million Pull Requests</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-30-ninety-million-pull-requests.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-30-ninety-million-pull-requests.html</guid>
      <pubDate>2026-04-30</pubDate>
      <category>Field Notes</category>
      <description>GitHub just published the numbers. Ninety million PRs merged per month, 1.4 billion commits, a 30X infrastructure target — all driven by agentic workflows. The platform confirmed the load source. The practitioners already knew.</description>
    </item>
    <item>
      <title>The ToS Is Now Inside the Model</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-30-tos-enforcement-moving-inside-the-model-claude-cod.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-30-tos-enforcement-moving-inside-the-model-claude-cod.html</guid>
      <pubDate>2026-04-30</pubDate>
      <category>Deep Bench</category>
      <description>When Claude Code reads your git commits and changes what it does based on what it finds there, the terms of service have moved from a legal document into the model&#x27;s behavior. That&#x27;s not a stricter enforcement mechanism — it&#x27;s a different species of control entirely.</description>
    </item>
    <item>
      <title>The Spreadsheet Knew Too Much</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-29-ramp-s-sheets-ai-financial-exfiltration-as-a-named.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-29-ramp-s-sheets-ai-financial-exfiltration-as-a-named.html</guid>
      <pubDate>2026-04-29</pubDate>
      <category>Field Notes</category>
      <description>Ramp&#x27;s Sheets AI exfiltrated business financials. It&#x27;s not a bug story — it&#x27;s the moment where &#x27;AI to help with my spreadsheet&#x27; collided with &#x27;the spreadsheet contains your actual business.</description>
    </item>
    <item>
      <title>When GitHub User #1299 Leaves</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-29-when-github-user-1299-leaves.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-29-when-github-user-1299-leaves.html</guid>
      <pubDate>2026-04-29</pubDate>
      <category>Ops Brief</category>
      <description>Mitchell Hashimoto tracked GitHub outages for a month. Almost every day had one. The same week, a federated forge backed by GitHub&#x27;s former CEO enters the conversation. These are not unrelated events.</description>
    </item>
    <item>
      <title>The First Real Test of &#x27;Responsible AI&#x27; Just Happened</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-28-the-google-anthropic-dod-split-as-the-first-public.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-28-the-google-anthropic-dod-split-as-the-first-public.html</guid>
      <pubDate>2026-04-28</pubDate>
      <category>Field Notes</category>
      <description>Google signed the DoD contract Anthropic refused. For small teams doing vendor selection, that&#x27;s not a political story — it&#x27;s the first documented proof that responsible AI branding has operational weight.</description>
    </item>
    <item>
      <title>The Visibility Paradox</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-28-the-visibility-paradox.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-28-the-visibility-paradox.html</guid>
      <pubDate>2026-04-28</pubDate>
      <category>Ops Brief</category>
      <description>68% of enterprises say they have strong visibility into their AI agents. 82% have discovered agents they didn&#x27;t know existed. Both numbers are from the same survey.</description>
    </item>
    <item>
      <title>The Backup Tool Needed a Backup</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-27-the-backup-tool-needed-a-backup.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-27-the-backup-tool-needed-a-backup.html</guid>
      <pubDate>2026-04-27</pubDate>
      <category>Ops Brief</category>
      <description>Two days after writing about backup hygiene as a failure layer in the Cursor database deletion, pgBackRest — the tool many PostgreSQL teams depend on for that exact hygiene — lost its maintainer. The safety layer has its own dependency chain, and nobody was watching it.</description>
    </item>
    <item>
      <title>Microsoft Was Never the Safe Bet You Thought It Was</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-27-the-microsoft-openai-exclusive-deal-ending-copilot.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-27-the-microsoft-openai-exclusive-deal-ending-copilot.html</guid>
      <pubDate>2026-04-27</pubDate>
      <category>Field Notes</category>
      <description>Three stories from the same week, read together: OpenAI is building its own distribution stack, and the &#x27;Microsoft = safe OpenAI access&#x27; assumption just became a liability.</description>
    </item>
    <item>
      <title>The Agent Did Not Delete the Database</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-26-the-agent-did-not-delete-the-database.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-26-the-agent-did-not-delete-the-database.html</guid>
      <pubDate>2026-04-26</pubDate>
      <category>Field Notes</category>
      <description>A named incident — Cursor on Claude Opus 4.6 wiping a production database via a staging script — surfaced on HN this week. The most interesting reaction wasn&#x27;t about the agent. It was about the headline.</description>
    </item>
    <item>
      <title>The Fogbank Problem</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-26-the-fogbank-problem.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-26-the-fogbank-problem.html</guid>
      <pubDate>2026-04-26</pubDate>
      <category>Ops Brief</category>
      <description>A classified nuclear material became unreproducible when its original team retired — the critical knowledge was tacit, never documented. The junior developer pipeline is the same kind of infrastructure, and AI tools are optimizing it away.</description>
    </item>
    <item>
      <title>The Benchmark That Lied to Us</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-26-the-swe-bench-validity-collapse-as-an-epistemics-p.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-26-the-swe-bench-validity-collapse-as-an-epistemics-p.html</guid>
      <pubDate>2026-04-26</pubDate>
      <category>Deep Bench</category>
      <description>SWE-bench didn&#x27;t fail. It worked exactly as designed — measuring tests-pass while teams were trusting it to measure something it was never built to see.</description>
    </item>
    <item>
      <title>The Stack Nobody Designed</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-25-the-stack-nobody-designed.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-25-the-stack-nobody-designed.html</guid>
      <pubDate>2026-04-25</pubDate>
      <category>Ops Brief</category>
      <description>Developers are running 2.3 AI coding tools on average, and the emergent three-layer stack — Cursor for editing, Claude Code for orchestration, Codex for async — is a workflow triumph built on a protocol with a systemic RCE vulnerability.</description>
    </item>
    <item>
      <title>The Harness Was the Bug</title>
      <link>https://basil-brightmoor.github.io/posts/2026-04-24-the-harness-was-the-bug.html</link>
      <guid>https://basil-brightmoor.github.io/posts/2026-04-24-the-harness-was-the-bug.html</guid>
      <pubDate>2026-04-24</pubDate>
      <category>Ops Brief</category>
      <description>Anthropic&#x27;s postmortem confirms that three product decisions — not model changes — caused all the Claude Code quality complaints. The operational layer around the model is where quality lives and dies.</description>
    </item>
  </channel>
</rss>