❯ charter blog --list # 5 notes
Field notes from the agent era
Readiness, deterministic scoring, supply-chain safety — and what we learn shipping Charter.
MCP is the new unpinned dependency
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.
read the note## more notes
- 01
The harness is mostly your repo
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.
- 02
The repo is part of the prompt
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.
- 03
The score only ratchets up
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.
- 04
Introducing Charter: AI-agent readiness, scored
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.