Pace or Pause.
← Back

Full Record

Anca Dragan

AI safety researcher

Completed research review

Advocates safety alongside capability and monitorable reasoning, but leaves capability-versus-transparency trade-offs and current development cadence unspecified.

Reviewed 4 Oct 2026 by policy-independent-review-2026-10-04.

Exact reviewed research digest: 1c6a088e66d78ed8538004a394a941eaa026a9c2b2e8fa0e85f78dea9c8673d4

Current position ·

UNCLEAR

Advocates safety alongside capability and monitorable reasoning, but leaves capability-versus-transparency trade-offs and current development cadence unspecified. [1][2][3][4][5][6]

Clarification. Deeper private pass inspected personal statements and contrary/newer evidence; previous uncertainty remains. No public integration.

Source [1] · Coauthored essay

The case for reasoning transparency — trade-offs

Published

“We don't claim to know exactly how to navigate these trade-offs.”

Transparency under pressure, paragraph immediately after the capability/performance-versus-transparency trade-off. · View original source ↗

Source context. Personal coauthored essay by Rohin Shah and Anca Dragan; DMI disclaimer says these are authors' ideas, not Google's official view. Most current located substantive writing explicitly leaves trade-off navigation unsettled. Preserving current architectures is said compatible with considerable scaling; safeguards are not a blanket pace prescription.

Scope
Frontier-model reasoning architecture and monitorability.
Conditions
If opaque architectures perform better, capability gains versus transparency remain a trade-off; developers departing from standard Chain of Thought should demonstrate comparable monitorability.
Stated rationale
Personal coauthored essay by Rohin Shah and Anca Dragan; DMI disclaimer says these are authors' ideas, not Google's official view. Most current located substantive writing explicitly leaves trade-off navigation unsettled. Preserving current architectures is said compatible with considerable scaling; safeguards are not a blanket pace prescription.
Source details

primary · Original publication date and personal attribution independently inspected; separate interview/event date not supplied.

Discovered 4 Oct 2026.

Published 16 Sep 2026.

Accessed 4 Oct 2026.

Source [2] · Original statement

Anca Dragan named Head of AI Safety and Alignment at Google DeepMind

Published

“Google DeepMind is fairly unique in that capability and safety go hand-in-hand and have to advance together”

First direct quotation, after description of the new Safety and Alignment organization. · View original source ↗

Source context. Gloria Tao departmental announcement personally quotes Dragan. This is her own statement about co-advancement, not an employer stance inferred from her job. Safety/capability together does not specify slower training or continued current pace.

Scope
Google DeepMind capability and safety advancement together.
Conditions
Industry and academia should collaborate; no current capability-development speed or slowdown trigger specified.
Stated rationale
Gloria Tao departmental announcement personally quotes Dragan. This is her own statement about co-advancement, not an employer stance inferred from her job. Safety/capability together does not specify slower training or continued current pace.
Source details

primary · Original publication date and personal attribution independently inspected; separate interview/event date not supplied.

Discovered 4 Oct 2026.

Published 28 Mar 2024.

Accessed 4 Oct 2026.

Source [3] · Original statement

Anca Dragan Interview

Published

“…perhaps building in safety from the get-go as opposed to designing a capable system and adding safety after”

Answer to Principle 6 Safety, final paragraph. · View original source ↗

Source context. Ariel Conn firsthand interview about Asilomar principles. Proposes changing research/design practices; no rate, moratorium, or resumption rule. Arms-race comments elsewhere explicitly concern lethal autonomous weapons, not all frontier AI.

Scope
Designing AI safety into systems from the outset.
Conditions
Safety constraints and verification methods become harder as capabilities grow; need to rethink safety approaches.
Stated rationale
Ariel Conn firsthand interview about Asilomar principles. Proposes changing research/design practices; no rate, moratorium, or resumption rule. Arms-race comments elsewhere explicitly concern lethal autonomous weapons, not all frontier AI.
Source details

primary · Original publication date and personal attribution independently inspected; separate interview/event date not supplied.

Discovered 4 Oct 2026.

Published 19 Jan 2017.

Accessed 4 Oct 2026.

Source [4] · Coauthored essay

Managing extreme AI risks amid rapid progress — version 3

Published

“…halt their development and deployment in response to worrying capabilities”

Governance section, paragraph beginning Commensurate mitigations are needed for exceptionally capable future AI systems. · View original source ↗

Source context. The coauthored consensus paper calls for proactive safety research, evaluations, safety cases, accountability and if-then commitments. A possible future halt is one tool among licensing, autonomy restrictions, access controls and information security. It does not demand a general immediate pause or prescribe a current capability-growth rate.

Scope
Exceptionally capable future autonomous AI systems capable of circumventing human control.
Conditions
Governments should be prepared to halt development and deployment on worrying capabilities until adequate protections are ready; prepare governance capacity now.
Stated rationale
The coauthored consensus paper calls for proactive safety research, evaluations, safety cases, accountability and if-then commitments. A possible future halt is one tool among licensing, autonomy restrictions, access controls and information security. It does not demand a general immediate pause or prescribe a current capability-growth rate.
Source details

primary · Original versioned paper and author list independently opened. arXiv submission history establishes v3 publication May 22, 2024; v1 October 26, 2023. Joint authorship, not individual speech.

Discovered 2 Oct 2026.

Published 22 May 2024.

Accessed 2 Oct 2026.

Source [5] · Coauthored essay

Taking a responsible path to AGI

Published

“…even a small possibility of harm must be taken seriously and prevented”

Navigating the path to AGI, first paragraph. · View original source ↗

Source context. The blog discusses AGI benefits, misuse and misalignment research, frontier safety frameworks, and coordinated international governance. It complements rather than retracts the earlier conditional governance recommendation. Safety concern and employer activity are not affirmative evidence of a pace label.

Scope
Technical AGI safety and security and responsible development.
Conditions
Proactive planning, preparation and collaboration to mitigate harms; no explicit capability-development rate in this passage.
Stated rationale
The blog discusses AGI benefits, misuse and misalignment research, frontier safety frameworks, and coordinated international governance. It complements rather than retracts the earlier conditional governance recommendation. Safety concern and employer activity are not affirmative evidence of a pace label.
Source details

primary · Original blog dated April 2, 2025, with Dragan named among four authors, independently opened. Publication date used; separate statement/event date unknown.

Discovered 2 Oct 2026.

Published 2 Apr 2025.

Accessed 2 Oct 2026.

Source [6] · Coauthored essay

The case for reasoning transparency

Published

“…without meaningfully limiting or slowing down progress”

Preserving transparent architectures, paragraph beginning If we continue to use architectures like today’s language models. · View original source ↗

Source context. The authors propose measurement, transparent architectures and training-reward audits. Later they acknowledge performance/transparency trade-offs and possible regulation, without a general instruction to slow all development. The DMI disclaimer says the essay reflects authors’ ideas, not Google’s official view. This newer technical recommendation prevents collapsing a future conditional halt into an unqualified current PAUSE or PACE.

Scope
Maintaining monitorable reasoning architectures during frontier-model capability scaling.
Conditions
Current transformer-like architectures may preserve transparency without major slowdown; opaque alternatives should demonstrate comparable monitorability, and capability gains may need sacrificing if transparency would be lost.
Stated rationale
The authors propose measurement, transparent architectures and training-reward audits. Later they acknowledge performance/transparency trade-offs and possible regulation, without a general instruction to slow all development. The DMI disclaimer says the essay reflects authors’ ideas, not Google’s official view. This newer technical recommendation prevents collapsing a future conditional halt into an unqualified current PAUSE or PACE.
Source details

primary · Original dated September 16, 2026 and author list independently opened; both authors acknowledged. Exact passage inspected alongside Transparency under pressure qualification.

Discovered 2 Oct 2026.

Published 16 Sep 2026.

Accessed 2 Oct 2026.

Editorial assessment. Second deeper private pass. Preserve UNCLEAR: the new primary evidence clarifies attribution/context but does not justify STOP, PAUSE, PACE, CONTINUE or ACCELERATE under the methodology. Older assessment and all evidence/history retained. Original-source review and independent adversarial review remain separate; no human approval or integration.

Assessment reviewed

Earlier position ·

UNCLEAR

Supports conditional halts for dangerous future autonomous systems and preserving reasoning transparency, but the verified record does not settle one current development cadence. [1][2][3]

Initial statement. Provisional isolated research assessment; independent adversarial review and human approval remain separate.

Source [1] · Coauthored essay

Managing extreme AI risks amid rapid progress — version 3

Published

“…halt their development and deployment in response to worrying capabilities”

Governance section, paragraph beginning Commensurate mitigations are needed for exceptionally capable future AI systems. · View original source ↗

Source context. The coauthored consensus paper calls for proactive safety research, evaluations, safety cases, accountability and if-then commitments. A possible future halt is one tool among licensing, autonomy restrictions, access controls and information security. It does not demand a general immediate pause or prescribe a current capability-growth rate.

Scope
Exceptionally capable future autonomous AI systems capable of circumventing human control.
Conditions
Governments should be prepared to halt development and deployment on worrying capabilities until adequate protections are ready; prepare governance capacity now.
Stated rationale
The coauthored consensus paper calls for proactive safety research, evaluations, safety cases, accountability and if-then commitments. A possible future halt is one tool among licensing, autonomy restrictions, access controls and information security. It does not demand a general immediate pause or prescribe a current capability-growth rate.
Source details

primary · Original versioned paper and author list independently opened. arXiv submission history establishes v3 publication May 22, 2024; v1 October 26, 2023. Joint authorship, not individual speech.

Discovered 2 Oct 2026.

Published 22 May 2024.

Accessed 2 Oct 2026.

Source [2] · Coauthored essay

Taking a responsible path to AGI

Published

“…even a small possibility of harm must be taken seriously and prevented”

Navigating the path to AGI, first paragraph. · View original source ↗

Source context. The blog discusses AGI benefits, misuse and misalignment research, frontier safety frameworks, and coordinated international governance. It complements rather than retracts the earlier conditional governance recommendation. Safety concern and employer activity are not affirmative evidence of a pace label.

Scope
Technical AGI safety and security and responsible development.
Conditions
Proactive planning, preparation and collaboration to mitigate harms; no explicit capability-development rate in this passage.
Stated rationale
The blog discusses AGI benefits, misuse and misalignment research, frontier safety frameworks, and coordinated international governance. It complements rather than retracts the earlier conditional governance recommendation. Safety concern and employer activity are not affirmative evidence of a pace label.
Source details

primary · Original blog dated April 2, 2025, with Dragan named among four authors, independently opened. Publication date used; separate statement/event date unknown.

Discovered 2 Oct 2026.

Published 2 Apr 2025.

Accessed 2 Oct 2026.

Source [3] · Coauthored essay

The case for reasoning transparency

Published

“…without meaningfully limiting or slowing down progress”

Preserving transparent architectures, paragraph beginning If we continue to use architectures like today’s language models. · View original source ↗

Source context. The authors propose measurement, transparent architectures and training-reward audits. Later they acknowledge performance/transparency trade-offs and possible regulation, without a general instruction to slow all development. The DMI disclaimer says the essay reflects authors’ ideas, not Google’s official view. This newer technical recommendation prevents collapsing a future conditional halt into an unqualified current PAUSE or PACE.

Scope
Maintaining monitorable reasoning architectures during frontier-model capability scaling.
Conditions
Current transformer-like architectures may preserve transparency without major slowdown; opaque alternatives should demonstrate comparable monitorability, and capability gains may need sacrificing if transparency would be lost.
Stated rationale
The authors propose measurement, transparent architectures and training-reward audits. Later they acknowledge performance/transparency trade-offs and possible regulation, without a general instruction to slow all development. The DMI disclaimer says the essay reflects authors’ ideas, not Google’s official view. This newer technical recommendation prevents collapsing a future conditional halt into an unqualified current PAUSE or PACE.
Source details

primary · Original dated September 16, 2026 and author list independently opened; both authors acknowledged. Exact passage inspected alongside Transparency under pressure qualification.

Discovered 2 Oct 2026.

Published 16 Sep 2026.

Accessed 2 Oct 2026.

Editorial assessment. A conditional future halt within an adaptive governance program is not an immediate blanket PAUSE. The July2026 letter requests the capacity to pace later, and only supplies a month date in the original, so it remains a blocked private observation. The newer transparency essay allows continued progress on monitorable architectures while acknowledging trade-offs. Retweets of others cannot substitute for her own recommendation. Unclear is a legitimate endpoint.

Assessment reviewed

How we assess positions ↗