Engineering & Technical

The Engineer

The Signal

Anthropic cut cache reads 75% and measured per-task cost still rose 20%.

Fable 5.1 emits roughly 1.7x the output tokens, and output still prices at $50/MTok. The saving scales with what you cache. The penalty scales with what you generate. Break-even sits near 47 cache-read tokens per output token, which is a one-line aggregation over last month's usage logs. If your ratio comes in under that, the cheaper reads never cover the extra generation.

In Play

  1. The Cache Discount That Arrives as a Price Increase

    Anthropic cut Claude cache reads 75%, from $1.00 to $0.25 per million tokens, and Artificial Analysis then measured net per-task cost rising from $3.14 to $3.76 because Fable 5.1 emits roughly 1.7x the output tokens. Whether the change is a discount or an increase is a property of your cache-read-to-output ratio, not of the model. Back-solving the vendor's own 25%/45% savings claims implies cache reads were already 33-60% of spend, which makes prefix stability the dominant cost lever.

  2. Provider Policy Becomes an Availability Dependency

    OpenAI published on September 1 that Astra is the first model to meet the Critical cybersecurity threshold in its Preparedness Framework, and stated plainly that launch safeguards will over-block some legitimate work. Enforcement differs by surface: ChatGPT and Codex pause an action for human review, while API tasks simply stop. For a headless agent run there is no in-band recovery, so a classifier decision becomes an availability failure your on-call absorbs silently.

  3. Your Scanners and LLM Gateway Were the Supply Chain

    The Australian Federal Police arrested two alleged TeamPCP members near Perth over software supply-chain attacks earlier in 2026, and Risky.Biz reports the successful hits were Trivy, KICS, LiteLLM and Telnyx. Three of those four run inside CI or the AI request path: the scanners hold broad repo read access and result-write credentials, and LiteLLM sits inline holding model provider keys while seeing full prompt and response traffic. No affected version ranges were published, so exposure has to be assumed and credentials rotated rather than waiting on an advisory.

  4. The Harness Outperformed the Weights This Cycle

    The largest measured gains this cycle came from runtime systems rather than model weights, per AINews's roundup. The open-source harness openJiuwen reports 82.6% on SWE-bench Verified and 87.19% on Terminal-Bench 2.1 with a fixed underlying model policy, and Agent Zero Memory posts 95.6% on LongMemEval by separating episodic timelines from entity-event graphs with citation-locking. The cheapest win is a structured escalation tool that lets an agent declare broken test infrastructure: reward hacking fell from 23.6% to 5.3% across eight frontier models with essentially no overhead.

  5. Beck Prices Rollback as Product Strategy

    Kent Beck published "Reject Change, Sometimes," arguing that in symmetric-payoff situations going all-in on change is a flat bet and the compounding lives in constant rebalancing, worth roughly 6% growth per period in his Shannon's Demon model. The engineering catch is that rebalancing assumes cheap reversal, and software reversal is partial: mutated data, emitted events and published SDK versions are one-way doors. If your reversal cost exceeds that edge the strategy is unavailable, which makes tested down-migrations and timed restore drills load-bearing rather than hygiene.

Deep Dives

  1. The 47:1 Rule Decides Whether Anthropic's Discount Reaches Your Bill

    Two independent analyses of the same price change reach opposite conclusions, and the gap is one ratio you can compute from last month's usage logs.

    The math has two terms with opposite signs, and they scale off different meters. Savings scale with cache reads. Cache-read tokens bill at $0.75 per MTok, which is the $1.00 to $0.25 delta. Read more from cache, save more. The…

    3 action items

  2. Astra Makes Classifier Termination a First-Class Failure Mode

    OpenAI says its launch safeguards will over-block legitimate work, and the surface with no human attached is the one that absorbs the cost.

    The false positives are already measurable at the other lab This failure class is already in production, and observing it does not require Astra access. Under Anthropic's 5.1 safeguards, Greg Kamradt could not complete planned evaluations because requests were rejected…

    3 action items

  3. Your CI Ran Trivy, KICS and LiteLLM Through a Backdoored Window

    No affected version ranges were published, which turns this from a patching exercise into a credential-rotation exercise across every job those tools could touch.

    Start from what those tools can reach The targets were not end-user software, which is what makes this expensive. Trivy and KICS run with broad read access to every repo they scan , often with credentials that can write results,…

    3 action items

The edition continues

Take the signal into the room.

Sign up or log in to read all 3 deep dives in full, plus the final take.

Read the full edition

Continue with LinkedIn