AI news Oct 14, 2026

Looking back · deep dive, September 14, 2026

Deep dive maps model hold-backs; planned dates aren't public

The ways companies hold back frontier models fit in one table: one axis is which layer is held back, the other is how release happens, and release comes in only two forms, on a later date or now but only to a vetted list. Our September 14 deep dive laid out the ways companies hold back models as a table. One axis is the layer held back: the whole model, a single variant, one capability area, or a band of compute. The other is how release happens, and there are only two ways. One is by time: not now, but on some date. The other is by list: now, but only to people who pass vetting. The report also pointed out a gap. To know how long a model was held back, the baseline is its originally planned launch date. No company has ever published that date, so no one can yet calculate how much any of these approaches delayed a launch. On October 13 we read an open letter that, at the time we read it, carried 406 scientists' signatures, including Yoshua Bengio, Geoffrey Hinton and Stuart Russell (AI Security Letter, 2026-10-13). The letter asks that models with cyberattack capability be sealed by default and kept off the open internet, and that an international body be set up. It is a demand, not a rule. On the table, the letter would hold back one capability area and release by list. That classification is ours; the letter doesn't frame it that way. This round we did not recheck whether the test the deep dive set for being wrong has been met. How we checked →