Weekly Review — June 8-14, 2026

TL;DR: Six posts this week, all circling one idea: across this week’s cases, raw model power was rarely the differentiator — the structure, governance, and craft around the model were. A paper (and a Bedrock reproduction) shows your cheapest model writes agent harness updates as well as a frontier one; two pipeline deep-dives show quality comes from systematic editing passes and disciplined voice-matching; a day-one Claude Fable 5 run shows the real decision is the data-retention switch, not the latency; and AWS quietly closed the CLI’s multi-account advantage with a stricter MCP design. Plus a build-log on cloning my own voice on SageMaker.

This is the Weekly Review, a Sunday digest of everything that went up on the blog this week, plus a short list of things I read but didn’t write about. If you only have ten minutes on a Sunday, this is the one to read.

This Week on the Blog

Why Your Cheapest Model Should Write the Harness

A May 2026 paper separates two things self-improving agents usually conflate: writing harness updates and benefiting from them. Writing is flat across model tiers — a 9B open model produces updates about as useful as a frontier model — while benefiting is an inverted-U that peaks at mid-tier. The practical move is to put your cheap model in the evolver seat and your expensive model in the solver seat, which I reproduced on Bedrock, where a Haiku-written skill lifted a Sonnet solver from fail to pass.

AI Content Pipeline Deep Dive (3/5): Collaborative Writing

Part 3 of the pipeline series, on the phase people most often get wrong: the agent never writes the first draft. It studies your voice from previous posts, assists while you draft, and reviews what you wrote — so the result reads like you, not like the statistical mean of the internet. The discipline is simple: you write the argument, the agent handles everything around it.

From a Generic Voice to My Own: Self-Hosting a TTS Model on Amazon SageMaker

I replaced the Amazon Polly narration on my agentic-payments demo with my own voice, cloned from a 30-second clip by an open-weights Qwen3-TTS model I deployed myself on SageMaker async inference. It’s a build log: the scale-to-zero endpoint, the real deploy and invoke code, the gotcha that cost me twenty minutes (with the target-tracking policy I had configured, the autoscaler won’t wake a scaled-to-zero endpoint on a single queued request — it takes a second, backlog-based policy), and an honest look at the cost trade-off versus Polly and the ethics of cloning a voice, even your own.

Claude Fable 5 on Bedrock: A Hands-On Comparison, and the Data-Retention Switch You Set First

Fable 5 went GA on Bedrock, so within a day I ran it EU-resident in Frankfurt against Opus 4.8 and Sonnet 4.6 on three tasks of rising difficulty. On the easy and mid tasks all three were at parity (Fable the slowest); on the hard refactor the two leaner models shipped complete, correct fixes while Fable diagnosed deepest but never shipped a runnable one under the output budget. The more useful lesson is upstream of any benchmark: Fable 5 only runs if you opt a scope into provider_data_share (30-day retention), and while EU Geo keeps data stored in-EU, the opt-in still lets Anthropic access flagged content for review.

AI Content Pipeline Deep Dive (4/5): Editing

Part 4: the quality-assurance phase most solo writers skip. Every post runs five automated editing passes before publishing — challenging questions that stress-test the argument, a FAQ, a 13-category AI-smell check, a critical-reader pass, and a TL;DR that reflects the final version — in about 8-12 minutes unattended. I audited 32 of my own posts against the checklist (four scored a D), and it’s copy-paste-ready at the end of the post.

CLI vs MCP, Part Two: The First Gap Just Closed

In March I argued the CLI’s edge over MCP was a temporary training-data artifact, not a law of physics — and singled out multi-account work as its most painful real-world advantage. On June 5, AWS addressed the sharpest part of that gap: the AWS MCP Server now takes a profile per command. The interesting part is how it closed: the MCP version isn’t a copy of the CLI’s behaviour but a stricter one — a proxy allowlist, undeclared profiles rejected, and the profile parameter stripped before the request reaches the backend — controls that narrow specific risks (unvetted commands, profile confusion) rather than a blanket safety guarantee.

The Thread This Week

Three of these posts are the same argument wearing different clothes: reliability and value come from what you build around the model, not from reaching for the biggest one. Cheap models write harness updates as well as frontier models; in my pipeline, quality comes from systematic editing gates, not raw fluency; and the leaner Claude models shipped working code while the new flagship’s real story turned out to be a governance switch. Even the MCP update fits — the gap closed not by copying the CLI but by designing something safer than it. The two build-logs (the cloned voice, the Fable 5 run) are the same lesson applied to real systems instead of stated as principle.

Until Next Sunday

That’s the week. The through-line — reliability and value come from structure and craft around the model, not from raw power — is one I’ll keep pulling on, because it’s the difference between an AI demo and an AI system you’d actually run.

Which of these would you have led with? And what did you read this week that I should have?