<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Charter Blog</title>
    <link>https://use-charter.dev/blog</link>
    <description>Notes on AI-agent readiness, deterministic scoring, supply-chain safety, and building Charter.</description>
    <language>en</language>
    <atom:link href="https://use-charter.dev/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MCP is the new unpinned dependency</title>
      <link>https://use-charter.dev/blog/mcp-is-the-new-unpinned-dependency</link>
      <guid isPermaLink="true">https://use-charter.dev/blog/mcp-is-the-new-unpinned-dependency</guid>
      <description>Agents call MCP servers with the same trust npm calls once got by default — no lockfile, no pin, no allowlist. 2026's supply-chain lesson is repeating one layer up.</description>
      <pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate>
      <category>ai-agents</category>
      <category>security</category>
      <category>mcp</category>
    </item>
    <item>
      <title>The harness is mostly your repo</title>
      <link>https://use-charter.dev/blog/the-harness-is-mostly-your-repo</link>
      <guid isPermaLink="true">https://use-charter.dev/blog/the-harness-is-mostly-your-repo</guid>
      <description>Addy Osmani frames an agent as ~10% model and 90% harness. A large slice of that harness lives in your repository — and repo-readiness should be measured, not vibed.</description>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <category>ai-agents</category>
      <category>engineering</category>
    </item>
    <item>
      <title>The repo is part of the prompt</title>
      <link>https://use-charter.dev/blog/the-repo-is-part-of-the-prompt</link>
      <guid isPermaLink="true">https://use-charter.dev/blog/the-repo-is-part-of-the-prompt</guid>
      <description>A coding agent never works on an abstract problem — it works in your repository, and inherits every gap in it. When agents fail, the repo is often the reason. Why agent-readiness belongs in CI.</description>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <category>ai-agents</category>
      <category>philosophy</category>
    </item>
    <item>
      <title>The score only ratchets up</title>
      <link>https://use-charter.dev/blog/the-score-only-ratchets-up</link>
      <guid isPermaLink="true">https://use-charter.dev/blog/the-score-only-ratchets-up</guid>
      <description>Readiness isn't a one-time cleanup. Here's how Charter turns a repo from an honest baseline into a wall every pull request has to clear — and why the hard caps matter more than the formula.</description>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <category>engineering</category>
      <category>philosophy</category>
    </item>
    <item>
      <title>Introducing Charter: AI-agent readiness, scored</title>
      <link>https://use-charter.dev/blog/introducing-charter</link>
      <guid isPermaLink="true">https://use-charter.dev/blog/introducing-charter</guid>
      <description>AI coding agents are only as good as the repo they work in. Charter grades any repository 0–100 on how safely an agent can operate in it — offline, deterministic, and with a concrete fix for every gap.</description>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <category>launch</category>
      <category>ai-agents</category>
    </item>
  </channel>
</rss>
