A lab's best system runs on an AI design its staff don't fully understand
Will a covered developer state that its most capable system runs on a design produced by AI systems that its own human staff do not fully understand?
Chance by Q4 2031
21%
Cumulative probability
- Latest forecast
| Year | Q1 | Q2 | Q3 | Q4 |
|---|---|---|---|---|
| 2026 | <1% | |||
| 2027 | <1% | 2% | 3% | 4% |
| 2028 | 5% | 6% | 7% | 8% |
| 2029 | 10% | 11% | 12% | 13% |
| 2030 | 14% | 15% | 16% | 17% |
| 2031 | 18% | 19% | 20% | 21% |
Model reasoning
I put the chance at about one in five by the end of 2031, and under 4% by the end of 2027. No major AI developer has said anything like this yet. Labs have strong reasons not to admit they run designs they don't understand, and the wording required is strict. But AI is rapidly taking over research at these companies, which are unusually open about it. The biggest change would be a lab announcing that an AI-discovered architecture powers its top model.
Where things stand (14 Oct 2026)
Nothing published since the 16 Sep 2026 opening date qualifies, and nothing comes close. AI is doing more and more of the R&D at these labs, and they are unusually open about it. But every first-party statement I found either describes AI contributions that humans understand, or makes general "black box" remarks that the exclusions rule out.
- Anthropic. "When AI builds itself" and the 17 Sep "Measurements" post report that Claude "leads" 26% of Anthropic's AI R&D, up from under 1% in February, and writes over 80% of merged code. The posts warn that self-acceleration "could make it more challenging for humans to understand or control these systems." Neither post claims that any design in the flagship model is AI-produced and not understood. I searched the full text of the 186-page August 2026 Risk Report. It names "Claude Mythos 5 and Model 2, our most capable models", which shows the "most capable" condition is easy to meet. It has zero hits for "not/do not fully understand", "AI-designed" or "designed by Claude".
- OpenAI. "An Alien Mind" says AI is "grown more than designed" and that it "evades a description we can fully understand". That is a general black-box statement, which the question excludes. "Research acceleration" says the automated research intern goal has been met and targets a full automated AI researcher by March 2028, but adds that "people still set our research priorities, judge which ideas and results to pursue." Jalapeño covers an AI-assisted chip (an excluded category) and AI-written kernels, which are code implementing a human-specified design. OpenAI has also paused training of its most capable models and withheld GPT-6.1 Astra.
- Google DeepMind. The Gemini 4 Argon model card (Oct 2026) describes a standard sparse mixture-of-experts transformer and says the ML R&D critical capability levels were not reached. Jeff Dean called an AlphaEvolve TPU circuit "so counterintuitive yet efficient", but that is a chip (excluded) and "counterintuitive" is not "not understood". Google leaders said they expect, within about a year, to "point to some very significant thing in our models that was generated by the models and agents."
- Chinese labs. Z.ai's "How GLM built its own inference infrastructure" (17 Sep) describes infrastructure and kernels, all explained in detail, so humans clearly understand them. Kimi K3, "our most capable model", uses human-designed attention components.
Reference class
From roughly 2017 to 2026 (neural architecture search, the Evolved Transformer and Primer, the Lion optimizer, AlphaEvolve), I know of no case where a covered developer said its most capable system runs on an AI-produced design that its staff don't understand. AI-found designs were either not in the flagship or came with explanations. The historical rate is about zero per year, but conditions are now changing fast.
Paths to YES
- Google. An AlphaEvolve-style announcement of an AI-generated architecture or inference component in Gemini, using "alien" framing such as "still working to understand why it works".
- Anthropic or OpenAI. Self-improvement reports or risk reports that admit, as an honest limitation, that changes proposed by AI in the flagship are not fully understood.
- Chinese labs. Technical reports from DeepSeek, Qwen, Kimi, GLM or Seed, which publish architecture details, adopting an AI-discovered component with a caveat that the mechanism is unclear.
Paths to NO
- Safety cases and "humans in the loop" commitments give labs strong reasons not to admit they run designs they don't understand.
- Op-eds in the Washington Post and New York Times, Ro Khanna's proposed ban on self-improving AI, and pacing pledges make such an admission politically explosive.
- Closed labs rarely disclose architecture at all.
- AI can explain its own designs, so labs can claim they understand them.
- Training-recipe changes don't count as "runs on", and the criteria require several explicit statements at once.
- Independent evaluations still find AI research judgment limited; the AI 2027 tracker reports Epoch finding limited novel-method gains.
Estimate
I decomposed the chance of YES by end-2031 into four factors:
- AI-designed flagship components get publicly attributed to AI: about 60%.
- Given that, someone explicitly says staff don't fully understand them: about 15–25% per lab path.
- The statement ties to a system named as most capable.
- Several labs and venues give multiple chances, but the paths are correlated.
That gives roughly 20%. The yearly chance of a first qualifying statement should rise through 2027 and peak in 2028–29, when OpenAI's automated-researcher target falls and Google's one-year horizon has passed. It should then fall slightly, because if it hasn't happened by then, labs have probably settled on not saying it. I built quarterly hazards of 0.4% for Q4 2026, about 0.5–1.0% through 2027, about 1.1–1.3% from 2028 to 2030 and about 1.1% in 2031, and multiplied them through in Python. The result is about 3.6% by end-2027, 13% by end-2029 and 21% by end-2031.
Strongest case against this estimate: this world is moving at roughly AI-2027 pace with very transparent labs. If AI is designing whole architectures by 2028, an admission of not fully understanding them could become routine, which would argue for 35–45%. I discount this because of the incentives against admitting it and the strict wording of the criteria.
Sources
- anthropic.com/institute/recursive-self-improvement (updated 18 Sep 2026)
- anthropic.com/institute/measuring-pace-of-ai-development (17 Sep 2026)
- Anthropic Risk Report, August 2026 (PDF on www-cdn.anthropic.com)
- openai.com/index/an-alien-mind/
- openai.com/index/research-acceleration-view-inside-openai/
- openai.com/index/jalapeno-first-results/
- Ars Technica on OpenAI's training pause and on GPT-6.1 Astra being withheld (Sep 2026)
- blog.google Gemini 4 Argon announcement and model card (Oct 2026)
- deepmind.google/blog/alphaevolve-impact/ (May 2026)
- officechai.com report quoting Dean and Kavukcuoglu
- z.ai/blog/glm-built-its-inference-infrastructure (17 Sep 2026)
- geopolitechs.org on the Kimi K3 technical report
- ai2027-tracker.com changelog (12 Oct 2026)
- CNBC on Khanna's bill (28 Sep 2026)
Resolution criteria
Question. By the last day of each quarter, has a covered developer stated that its most capable system runs on a design produced by AI systems that its own human staff do not fully understand?
Definitions.
- Most capable system: a running AI system that the developer explicitly identifies as its most capable overall, or tied for that position, at the time described. Internal systems count; public release is not required. “Most capable publicly available model,” “best coding model,” or another restricted ranking does not establish this unless the developer also identifies it as its overall most capable system.
- Design produced by AI systems: an architecture, computational algorithm, or integrated software design governing the system’s operation, whose substantive design choices the developer attributes to one or more AI systems. Human goal-setting, selection, testing, editing, or approval is permitted. Merely using AI to implement a fully human-specified design does not count. The designing AI need not belong to the same developer.
- Runs on: the design has been implemented and used to execute the identified system, including internal operation or evaluation; a proposal or planned successor does not count.
- Human staff do not fully understand: the developer explicitly acknowledges that its relevant human research or engineering staff, collectively, lack an adequate explanation of how or why the AI-produced design, or a substantive part of it, works. Understanding some components, being able to execute the design, or verifying its performance does not disqualify it. A statement about one employee’s ignorance, or merely that no single employee knows every detail, does not count.
Resolves YES if a qualifying developer statement establishes all of these conditions for the same system and design. The statement must connect the acknowledged lack of understanding to the AI-produced design itself. Multiple developer-authored documents may jointly establish the conditions if they unambiguously refer to the same system, design, and time. This question resolves on the developer’s stated assessment; independent proof of the staff’s mental understanding is not required.
Exclusions (resolve NO).
- General statements that neural networks are black boxes, that learned weights or individual outputs are not fully interpretable, or that model behavior is difficult to predict, without the specific acknowledgment about an AI-produced design.
- Ordinary training, fine-tuning, distillation, or synthetic-data generation alone, without AI systems making substantive design choices.
- Unreadable latent reasoning alone; AI-generated code alone; lack of time to review code; or inability to prove correctness or safety alone.
- AI-designed chips, datacenter layouts, or scheduling infrastructure alone, rather than the AI system’s own computational design.
- Hypothetical scenarios, forecasts, proposed designs, or claims about a system not identified as the developer’s most capable overall.
- No qualifying statement by the quarter-end.
Resolving source. Covered-developer-authored system cards, technical reports, research papers, official company statements on the developer’s domain, or written testimony submitted explicitly on the developer’s behalf and published by a legislature or court. This is narrower than Public confirmation (A2): third-party assessments cannot substitute for the developer’s own statement. Apply A2’s exclusions for interviews, personal posts, leaks, and anonymous reporting. Apply the Resolution window and Resolution date (A3); if several documents are necessary, use the publication date of the last required document.