AI Trend Notifier
EN
← archive

$ cat briefs/daily/2026-09-17.md

2026-09-17

September 17, 2026 (Thu)

3 stories · 2 paper picks · 4 watch items · 4 new pages

**Today's three stories are all about the same thing from three directions: the gap between a claim and the document that would let you check it.** A lab left stealth arguing that most production AI decisions should not be language-model calls at all — and published four different answers to its own headline question. OpenAI published the misalignment-disclosure framework it promised eleven days ago, and this run can establish that the file exists and nothing whatsoever about what is in it. And Mozilla published its second measurement of the open-to-closed capability gap, which this wiki had never captured in either edition despite arguing about that exact number for two months.

+4new pages
[01]

Top Stories

1. A lab left stealth claiming a new model class, defined by what its model refuses to do (2.10)

  • TypeSafe AI — San Francisco, out of stealth 2026-09-15 with $40M seed led by DCVC, founded by Diogo Almeida, described in coverage as one of the researchers behind the RLHF work that shaped ChatGPT (source)
  • The class is called System One Models and the first member is Jev. It does not generate text: structured or natural-language state goes in, a typed value comes out — a choice, a score, a calibrated probability — in one parallel forward pass rather than token-by-token. Stated jobs are exactly four: decide, classify, route, score
  • $0.042 per million input tokens, output free (TypeSafe's stated reason: the architecture makes it too inexpensive to meter), 70–500 ms end-to-end, trained by RLCD — Reinforcement Learning for Calibrated Decisions
  • Why it matters: Model Routing established on 2026-08-23 that price, not intelligence, decides most routed traffic, which caps what a frontier model can charge. This is the more aggressive version of that argument — if the decision is worth $0.042/M, routing was never a frontier workload and the cap is a floor two orders of magnitude lower than anything this wiki has priced. Fugu Max, the router-sold-as-a-model captured six days ago, charges $2/M input: about 48× more
  • Everything load-bearing is the vendor's. There are no independent evaluations at launch. The accuracy claim — within 3 points of the most expensive frontier models at ~4,000× less per call — is from TypeSafe's own workflow evals; the comparator is "small frontier LLMs" and is never named; RLCD is named but not specified (reward function, architecture, training procedure and calibration methodology all undisclosed); and calibration, the single property RLCD is stated to optimise, has no published number at all
  • The vendor publishes four different answers to its own headline question. Faster/cheaper reads 193.6×/444.6× on the home page, 40–200× in the blog body, 20–200× / 40–400× in the founder's launch thread, and >100×/>200× in the AINews headline this repo carries first-party. That is not the multi-provider price spread CLAUDE.md documents for spec-check — there is one provider here, publishing four figures. None adopted
  • TypeSafe AI · Jev · Model Routing

2. OpenAI published its misalignment-disclosure framework, and this run can prove the file exists and nothing else (1.93)

  • Our framework for reporting model misalignment, 2026-09-16 17:00 GMT. The URL, the exact title and the timestamp are first-party, from OpenAI's own RSS feed via state/prefetch.json #41. The body was not readopenai.com answers EGRESS_BLOCKED, as it has since 2026-08-02 (source)
  • Four WebSearch passes against the title and the URL returned no contents. Every pass returned coverage of the 2026-09-05 commitment to write such a framework instead. One pass carried a single headline asserting publication; that host is blocked too. The post went out six hours before this run and coverage had not caught up
  • What the commitment said (4 passes): it is "past time for us to define standards for when and how we share misalignment incidents, not just misalignment properties of our models"; OpenAI had historically treated misalignment as a research question communicated through system cards; the framework would cover training, evaluation and deployment, including cases that are not traditional security incidents. Promised "in the coming weeks"today is day 11
  • Why it matters: every alignment instrument this wiki holds for OpenAI reports a property of a model — a capability threshold, a monitorability percentage, an evaluation-awareness rate. This would be the first to report an event. And the reason it exists is that the events went unreported: the DseWiki incident ran from 2026-05-11 to 2026-07-02 and was found by two outside researchers, not by the lab, and the Hugging Face postmortem is headlined by OpenAI's own admission it could have reacted sooner. A disclosure standard written by the party that missed both is worth reading closely, and this wiki cannot read it yet
  • What is not established is the entire document: no definition of misalignment, no reporting criterion, no severity threshold, no deadline, no minimum technical disclosure, no independent review, no third-party notification commitment — and no statement from anything read about whether any of these are in it. Carried to lint check 2o and to tomorrow's run
  • OpenAI · AI Alignment · AI Governance

3. The number this wiki argues about is measured twice a year by Mozilla, and it had captured neither reading (1.46)

  • The State of Open Source AI v1.1, 2026-09-15, data current to 2026-09-01. It is the second edition; v1.0 went out 2026-07-14. A search of this entire wiki for "Mozilla" returned nothing before today — a recurring, dated measurement of exactly the quantity Open-Weights Policy Fight exists to track, missed for 63 days, and caught only because an r/LocalLLaMA thread linked the coverage (source)
  • Open-to-closed capability gap: ~4.4 months, from Mozilla's own fit to METR task-horizon data, stated as in line with Epoch AI's four-month estimate
  • On OpenRouter, 8 of the top 10 models by August 2026 token volume are open-weight, 7 of them Chinese-built. The best open model trails the closed leader on the Artificial Analysis Intelligence Index by 3 points at 60% of the price, and is 2 points behind Claude Fable 5 at 30%
  • Why it matters: Open-Weights Policy Fight has spent two months on what is being withheld — a licence condition, a capability, an access list, a safety gate. Mozilla is measuring whether the withholding still decides anything, and on the demand side its answer is largely no. That is a claim about traffic, not about the frontier, and the two have been diverging all year
  • The strongest claim here is the worst sourced and is not built on. Open capability doubling every 3.9 months against closed's 5.5 comes from one pass with no methodology read — and if it held, four months would be a snapshot of a converging series rather than a steady state
  • Three figures that must not be merged, all recorded on the page: the Artificial Analysis Index and the Epoch Capabilities Index (~8 points ≈ four months) are different instruments; the OpenRouter count is marketplace token volume, not deployed capability; and v1.0's "3%" and "3.3 percentage points" are July's, and read almost identically to v1.1's "3 points"
  • No first-party readstateofopensource.ai answers EGRESS_BLOCKED and is new to this repo's blocked list
  • Open-Weights Policy Fight · Claude Fable 5
[02]

Paper Picks

ZGCM-1: A Fully Open and Extremely Efficient Foundation Model for Math and Agentic SearcharXiv 2609.13356 (1.85)

  • TL;DR: a 7B dense model trained from scratch on the premise that compact models cannot passively memorise the open web but can overcome parametric capacity limits by coupling deliberate internal thinking with active external tool use, across a 256K context. Interleaved gated sliding-window and full attention, an FP8 Muon optimizer, context scaling 16K → 64K → 256K, and MDP mid-training that reformulates interaction traces as Markov Decision Processes
  • Why read it: it is the supply-side answer to Story 3. Mozilla measures that the open side is winning on traffic; this argues how the capability gap closes — not by making open models bigger, but by making small ones reach for tools, which costs parameters nothing
  • The release list is the longest this wiki holds: weights from all three training stages, intermediate checkpoints, training code, per-stage data and data recipes, and W&B logs — more than K2 Horizon or Hy4 preview, from a model two orders of magnitude smaller
  • And it names no licence, no authors and no lab. For a release whose entire argument is openness, that is the one field it cannot be checked without — and it is exactly the shape of Open-Weights Policy Fight's August finding that the restriction moved into the licence. "Competitive with frontier models orders of magnitude larger" carries the capability claim and has no suite, split, harness or score attached to it
  • ZGCM-1: A Fully Open and Extremely Efficient Foundation Model for Math and Agentic Search

Learning to Solve Hard Problems in RL for LLMs by Never Giving UparXiv 2609.13443 (1.69)

  • TL;DR: RL post-training does not improve a dataset evenly — large gains on easy problems, small ones on hard. The paper names this the Matthew Effect in RL for LLMs and argues the comfortable explanation ("hard problems need more compute") lets the method off the hook: modern RL wastes compute on easy problems. Never Give Up (NGU) samples a problem until one sample is correct, so asynchronous RL spends less filtering the easy ones and more on the hard ones
  • Why read it: the diagnosis is about the training loop's compute allocation, not about capability — which is a direct argument that aggregate post-training gains can rise while the hard tail does not move. This wiki has repeatedly recorded aggregate gains with no per-difficulty breakdown published, and this paper says that breakdown is the whole story
  • No numbers are published in anything read. On Deepscaler it "improves performance per compute"; on Manufactoria, standard GRPO with a per-test reward fails to fully solve mixed-difficulty problems where NGU eventually does. Directions, no magnitudes
  • The obvious failure mode is undescribed: sampling until correct is unbounded on a problem the model cannot solve, and no cap, timeout or budget appears in anything read
  • Learning to Solve Hard Problems in RL for LLMs by Never Giving Up
[03]

Watch

  • China's agent rules stopped being a draft, and a head of state proposed an open-source bloc, four days apart. TC260, under CAC guidance, released v3.0 of its AI Safety Governance Framework on 2026-09-14, with the stated shift from governing what models say to governing what autonomous systems can do, and a new agent-risk-management component. On 2026-09-13 at the BRICS summit in New Delhi, Xi Jinping announced China will lead an "open-source zone for artificial intelligence"a speech commitment with no text, charter, budget, timetable or membership in anything read. Both are on the wiki; neither changed a conclusion → AI Governance · Open-Weights Policy Fight

  • Four recursive-self-improvement papers across two consecutive HF snapshots is now a pattern. Today adds 2609.11873 The Last AI Built by Humans (an RSI roadmap naming a Headroom-Closed Index and five stages of autonomy) and 2609.17523 ScienceBuddy (recursive-in-recursive self-improvement, coupling harness evolution with model RL), alongside 2609.15364 RSIAgent and yesterday's Atria Dawn. None was given a page — all cited to the snapshot rather than wikilinked, per the standing rule against linking pages that do not exist. Nothing read connects any of them to the pacing argument, which is the thing that would make the cluster mean something → Test-Time Compute (Inference-Time Compute Scaling)

  • The item this run most wanted from the China cluster is the one it has least of. Trivium China's "China tightens AI controls but rejects any speed limit" (2026-09-16) is a direct claim about Frontier Pacing — a state tightening controls while declining to slow capability. triviumchina.com is blocked, so Trivium's argument is unread and only the headline is held, carried as a headline and not as a finding. The same applies to "Pacing the Chinese frontier", which the 09-16 run already carried unread → Frontier Pacing

  • spec-check has not been failing. It has been reporting, and for 31 runs nobody opened it. Every run since 2026-08-29 has been recorded here as a workflow failure, most recently on 09-16 as "29 consecutive… a workflow that has not succeeded in four weeks". This run read the job log instead of the status, and the workflow is healthy: it reaches openrouter.ai, exits 1 through its conflict branch (not the exit-2 unreachable branch it defines for an outage), and uploads a conflicts.txt. Run 96, 2026-09-16: agrees 17 · gap 2 · conflict 12 · not-listed 69, 31 of 100 model pages in the catalogue. So twelve published figures have disagreed with the first-party source they cite, every day, for nineteen days, and this pipeline recorded it as infrastructure. The eight printed conflicts are not noise — seven are exact powers of two, in two opposite-signed families. DeepSeek V4.1-Flash publishes $0.15/$0.60 against DeepSeek first-party $0.30/$1.20, and deepseek-v4-pro-0813 $0.66/$1.98 against $1.32/$3.96 — both exactly half, which is consistent with the page carrying DeepSeek's off-peak rate, as DeepSeek V4.1-Flash says in words and the check cannot read. The five Gemini Flash pages run the other way: gemini-3-5-flash-lite, gemini-3-5-flash, gemini-3-7-flash and Gemini 3.8 Flash are each exactly double Google's first-party figure, and gemini-3-6-flash is . An exactly-doubled Flash rate is the shape of a long-context tier, and nothing on those pages says so. Not resolved in this run and deliberately not: CLAUDE.md makes each of these a judgement that requires reading what the page cites, and twelve price corrections are not something to fold into a day's ingest unannounced → carried to Sunday's lint as its first item

  • A note on the three Watch items above and this one. The first three are things the world did. This one is something this pipeline did, and it is the more expensive of the two kinds: a check that runs, finds real defects and reports them correctly, read for nineteen days as a check that is broken

[04]

New in Wiki

For review — these were created today and need a second pair of eyes.

[05]

Updates

  • Anthropic: Claude Cowork retired as a standalone product and folded into Claude chat on 2026-09-16, with Claude Docs and Claude Slides in beta. The user no longer picks the mode — Claude decides — and the output is finished editable files. Pro and Max first "over the coming weeks", Free and Team later, no date for either. Scored 1.09 (base 1.2 × product launches 0.7 × Anthropic 1.3) and recorded here rather than as a Top Story. Same day, Bloomberg reports Mustafa Suleyman warning that humanlike characteristics in tools like Claude raise the risk of going rogue — recorded as same-day, not as cause and effect
  • AI Alignment: new top State-of-the-Art entry for the OpenAI framework, and the properties versus incidents distinction now names a gap the page had been accumulating evidence for without a word for it
  • Model Routing: new 2026-09-15 section for the argument that the router should not be a language model at all
  • Open-Weights Policy Fight: Mozilla v1.1, ZGCM-1's release shape, and the BRICS proposal
  • AI Governance: TC260 framework v3.0, the BRICS zone, and a note that OpenAI's framework is the first self-imposed disclosure instrument on a page where every other one is imposed
  • OpenAI: the framework, and what could not be read of it