<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>lgkm.org field notes: AI</title>
  <subtitle>The state of modern IT and security</subtitle>
  <link href="https://lgkm.org/topics/ai/feed.xml" rel="self"/>
  <link href="https://lgkm.org/topics/ai/"/>
  <id>https://lgkm.org/topics/ai/</id>
  <updated>2026-10-29T00:00:00Z</updated>
  <author><name>Simon Bennett</name></author>
  <entry>
    <title>The AI supply chain: models, plugins and tool servers as third parties</title>
    <link href="https://lgkm.org/notes/ai-supply-chain-third-parties/"/>
    <id>https://lgkm.org/notes/ai-supply-chain-third-parties/</id>
    <updated>2026-10-29T00:00:00Z</updated>
    <category term="ai"/>
    <summary>An AI feature is assembled from parts other people made: a hosted model, downloaded weights, editor plugins, tool servers and SaaS connectors. Each is a supplier with access, and the incidents of the last two years came through exactly those parts. Most third-party registers list only the first.</summary>
  </entry>
  <entry>
    <title>Jev, the model that only decides: where it fits in security work</title>
    <link href="https://lgkm.org/notes/jev-use-cases/"/>
    <id>https://lgkm.org/notes/jev-use-cases/</id>
    <updated>2026-10-27T00:00:00Z</updated>
    <category term="ai"/>
    <summary>Jev is a new kind of AI model that writes no text. It reads something and answers typed questions with a choice, a score or a yes/no probability, in a fraction of a second and for a fraction of a cent. That makes it a good first sorter for alerts, data labels and agent actions, and a poor final judge.</summary>
  </entry>
  <entry>
    <title>Which language model for which job</title>
    <link href="https://lgkm.org/notes/which-language-model-for-which-job/"/>
    <id>https://lgkm.org/notes/which-language-model-for-which-job/</id>
    <updated>2026-10-27T00:00:00Z</updated>
    <category term="ai"/>
    <summary>Large language models now come in four kinds, not one: frontier models for the hardest work, workhorses for most of it, small fast models for volume, and open-weight models you run yourself. The names change every month and the kinds do not, so choose by job, test one size down, and write policy about kinds rather than names.</summary>
  </entry>
  <entry>
    <title>Agents are the new insiders, with API keys</title>
    <link href="https://lgkm.org/notes/agents-are-the-new-insiders/"/>
    <id>https://lgkm.org/notes/agents-are-the-new-insiders/</id>
    <updated>2026-10-19T00:00:00Z</updated>
    <category term="ai"/>
    <summary>An AI agent that can read mail, call APIs and change records is a privileged insider that can be talked into things. Treat it like one: an owner, the least access that works, and a record of what it did.</summary>
  </entry>
</feed>
