Concrete Problems in AI Safety — TEI-tagged view

Dario Amodei, Chris Olah, Jacob Steinhardt, Paul Christiano, John Schulman, Dan Mané · 2016 · philosophy · arXiv:1606.06565 · full text at the source · TEI xml · tagged edition · index · concepts · authors
Where this record's text came from. faceted 2026-08 by reading the locally held text (pdftext); every evidence string verified as an exact substring of that text before merging. Claim type was hard to pin: the paper is an agenda-setting review whose central assertion is that concrete accident-risk problems exist and are tractable now, so 'existence' fits better than 'method' (no single technique is offered) or 'prediction'. method is 'review' because the paper reviews prior work and proposes experiments rather than running any. The MIRI relation is a scope/approach differentiation rather than a factual disagreement; 'extends' is the nearest available type and the verbatim sentence is the paper's own contrast clause. Many citations in the paper are bare bracketed numbers with no author names, so most citation contexts did not qualify as explicit relations to named prior work and were left out. 2026-08-14 and 2026-08-15 schema-0.3 passes: every quote verified as an exact substring of the staged text and anchored at merge time; concept terms verified present; every edge endpoint an existing node. Update, 15 September 2026: EXCEPTION, measured with the merge gate's own predicate (Paper.locate): 1 quote(s) on this record are not found as one exact string in the current staged text - content_tags.statistics[4].evidence. The sentence above does not hold for them as written. Where a row records why - the quote is grounded in another copy of the paper, joins two passages with an ellipsis, or differs from the staged text by extraction noise - that note stays on the row.
The quality of the text these quotes were cut from. symbol-font-not-extractable: 2 '(cid:NNN)' glyph-index markers remain in a staged text of 87,125 characters, where the PDF's embedded font had no ToUnicode map. THE QUOTES ON THIS RECORD ARE THE PAPER'S AND THE STAGED COPY IS THE DAMAGED ONE - which is the opposite of the usual case and is why it went unnoticed: one of its 51 live quotes is not an exact substring of this text, and it was located in it by aligning the quote's WORD SEQUENCE under exactly this damage - the words are there, the characters inside them are not. Not repaired in place: editing the staged text moves every offset after the edit and re-hashes every anchor on the record. Measured at 113aae60fefc3eb1, re-measured unchanged at 54b63482778ddf56.
Some words in these quotes contain the wrong character. The PDF this text was extracted from substituted 1 character inside a word — a currency sign or a stray accent where a letter pair belongs, as in signi¢cantly for significantly, or a single ligature glyph, as in confidence. They are valid characters in the wrong place, so they survive every encoding check. The quotes keep them for the same reason as above, and a search of this page will not find the affected words.
This record’s own method is review, and the tags below follow from that. A review’s findings, quantities and statistics are things stated IN this paper, and some of them report results obtained elsewhere. No tag on this page names a different author. Measured across every review in this corpus, 81% of a review’s tags carry no citation at all — most of them are the review speaking. The corpus does not adjudicate the rest: read an unmarked tag as a claim this paper makes, not necessarily one it made first.
1 quote on this page was cut from a different copy of this article. This project holds two extractions of this paper: the plain text every other quote here is anchored in, and the publisher’s own HTML edition, which we are not licensed to republish. It is verbatim in the second and cannot be found in the first — not because the tagging is wrong, but because the extraction damaged the passage: a page number dropped into the middle of a number, a formula moved out of its sentence, a ligature where two letters belong. The record names the copy for each one. The quote is the paper’s; the extraction is not.
Other fields define these differently the same word, defined another way in another discipline
reward 16 fields · learning 7 fields · robustness 3 fields · bootstrap 2 fields · linear regression 2 fields · variance 2 fields
Tags on this paper every tag the record carries, whether or not the words occur in the text below — a number is how many papers in the corpus carry that tag; a tag with no number is unique to this paper
AI safety value alignment2 reward hacking scalable oversight accident accident risk objective function side effects2 safe exploration accidents2 review319

Our tag layer for this paper

Cross-disciplinary analysis
content-tags & facets: phenomenon · claim-type · cross-domain-transfer · mechanism · claim-relation · replication-status · limitation — grounded in the full text
phenomenonaccidents in machine learning systems— “In this paper we discuss one such potential impact: the problem of accidents in machine learning systems, defined as unintended and harmful behavior that may emerge from poor design of real-world AI systems.”
claim-typeexistence— “Overall, we believe there are many concrete open technical problems relating to accident prevention in machine learning systems.”
method — evidence— “We review previous work in these areas as well as suggesting research directions with a focus on relevance to cutting-edge AI systems.”
transferfrom machine learning: framing the philosophical problem of AI safety concretely in terms of machine-learning methods (supervised learning, reinforcement learning)— “in terms of classic methods in machine learning, such as supervised classification and reinforcement learning”transfers[0]
transferfrom engineering (safety engineering): importing the engineering notion of accidents and safety into the analysis of AI systems— “This issue arises in almost any engineering discipline”transfers[1]
mechanismAI-safety accidents arise mainly from mis-specified objective functions - negative side effects and reward hacking— “two broad mechanisms that make it easy to produce wrong objective functions”mechanisms[0]
builds-on machine learning (modern ML techniques)— “We believe it is usually most productive to frame accident risk in terms of practical (though often quite general) issues with modern ML techniques”claim_relations[0]
builds-on an informal essay written by one of the authors of the present document (on semi-supervised RL)— “The discussion of semi-supervised RL draws heavily on an informal essay, https://medium.com/ai-control/ cf7d5375197f written by one of the authors of the present document.”claim_relations[1]
builds-on informal safety postings [146, 34] by two of the authors of this paper— “Finally, two of the authors of this paper have written informally about safety in AI systems [146, 34]; these postings provided inspiration for parts of the present document.”claim_relations[2]
extends the Machine Intelligence Research Institute's philosophical work on safety in very advanced AI— “By contrast, our focus is on the empirical study of practical safety problems in modern machine learning systems, which we believe is likely to be robustly useful across a broad variety of potential risks, both short- and long-term.”claim_relations[3]
sense'accident' - STIPULATED SO THAT IT ASSIGNS FAULT: in ordinary use an accident is what nobody is to blame for, and here it is defined as harm emerging from poor design or from specifying the wrong objective function, so the technical term points at exactly what the everyday term excuses— “We define accidents as unintended and harmful behavior that may emerge from machine learning systems when we specify the wrong objective function”senses[0]
sense'AI safety' - THE PUBLIC NAME FOR THE PAPER'S OWN TERM: the authors write about mitigating accident risk and note in a parenthesis that this is what public discussion calls AI safety, so the two names mark a register rather than a difference of subject— “we frame mitigating accident risk (often referred to as “AI safety” in public discussions) in terms of classic methods in machine learning”senses[1]
sensethe taxonomy - BY WHERE IN THE PROCESS THINGS WENT WRONG: safety problems are grouped not by the harm produced but by the stage at which the design failed, which is why the five categories are about objectives, oversight and exploration rather than about outcomes— “We can categorize safety problems according to where in the process things went wrong”senses[2]
auditaccident —part-of→ accident risk — Audit 2026-09-28: DOUBTFUL - read against its span and kept, but accident vs accident risk is a trivial containment the span does not state.— “we frame mitigating accident risk (often referred to as “AI safety” in public discussions) in terms of classic methods in machine learning”concept_edges[1]
for which uselimitation — the proposed approaches to the wrong-objective problems: they are offered WHERE LESS PRIOR WORK EXISTS, as preliminary avenues rather than solutions— “When discussing the problems that arise from having the wrong objective function (reward hacking and side effects, and to a lesser extent scalable supervision), where less prior work exists, our aim is more exploratory—we seek to more clearly define the problem and suggest possible broad avenues of attack, with the understanding that these…limitations[0]
for which uselimitation — the scope of the analysis: THESE ARE NOT THE ONLY POSSIBLE PARADIGMS FOR AI OR ML SYSTEMS, though the authors expect similar issues elsewhere— “These are not the only possible paradigms for AI or ML systems, but we believe they are sufficient to illustrate the issues we have in mind, and that similar issues are likely to arise for other kinds of AI systems.”limitations[1]
for which uselimitation — the rich-modelling route to avoiding side effects: WE ARE STILL A LONG WAY AWAY FROM PRACTICAL SYSTEMS THAT CAN BUILD A RICH ENOUGH MODEL— “However we are still a long way away from practical systems that can build a rich enough model to avoid undesired side effects in a general sense.”limitations[2]
for which uselimitation — the distributional-shift survey: RATHER THAN FULLY REVIEWING ALL OF THIS WORK IN DETAIL ... WE WILL DESCRIBE A FEW ILLUSTRATIVE APPROACHES— “Rather than fully reviewing all of this work in detail (which would necessitate a paper in itself), we will describe a few illustrative approaches and lay out some of their relative strengths and challenges.”limitations[3]
for which uselimitation — the word 'accident' as used in this paper: it is defined as unintended and harmful behaviour emerging when the wrong objective function is specified, which locates a cause rather than denying one— “We define accidents as unintended and harmful behavior that may emerge from machine learning systems when we specify the wrong objective function”limitations[4]
for which uselimitation — the scope of 'accidents' in this paper: one statement defines them as emerging from poor design of real-world AI systems, and another as emerging when the wrong objective function is specified— “the problem of accidents in machine learning systems, defined as unintended and harmful behavior that may emerge from poor design of real-world AI systems”limitations[5]
for which uselimitation — the concreteness claimed by this paper: many of the accident risks are illustrated with reference to a fictional office-cleaning robot rather than to a deployed system— “For concreteness, we will illustrate many of the accident risks with reference to a fictional robot whose job is to clean up messes in an office using common cleaning tools”limitations[6]
for which uselimitation — the range of risks covered here: the authors state one need not invoke extreme scenarios and that doing so can lead to unnecessarily speculative discussions that lack precision— “However, in our opinion one need not invoke these extreme scenarios to productively discuss accidents, and in fact doing so can lead to unnecessarily speculative discussions that lack precision”limitations[7]
replicationuntested
no type for thisside effects → negative externalities — THE INDEXING / PROXY RELATION - 'from' STANDS IN FOR 'to'. We have no type for it: 'causes' asserts production, and 'operationalised-as' says the authors CHOSE a measure, whereas a proxy claim says THIS STANDS IN FOR WHAT WE ACTUALLY CARE ABOUT AND WE KNOW IT IS NOT THE SAME THING. Measured at 8% of papers. THE CLEAREST PROXY CLAIM IN THE CORPUS, because it names the gap out loud: 'Avoiding side effects can be seen as a proxy for the thing we really care about: avoiding negative externalities.' The substitute, the target, and the acknowledgement that they differ, in one sentence - from an AI-safety paper, which is not where I expected to find the best statement of this project's own problem.— “• Multi-Agent Approaches: Avoiding side effects can be seen as a proxy for the thing we really care about: avoiding negative externalities.”unhoused_relations[0]
limitationThe proposed avenues of attack for the wrong-objective problems are explicitly preliminary and not fully worked out.— “When discussing the problems that arise from having the wrong objective function (reward hacking and side effects, and to a lesser extent scalable supervision), where less prior work exists, our aim is more exploratory—we seek to more clearly define the problem and suggest possible broad avenues of attack, with the understanding that these…limitations[0]
limitationThe analysis is restricted to RL agents and supervised learning systems rather than all AI paradigms.— “These are not the only possible paradigms for AI or ML systems, but we believe they are sufficient to illustrate the issues we have in mind, and that similar issues are likely to arise for other kinds of AI systems.”limitations[1]
limitationThe multi-agent / rich-modelling route to avoiding side effects is not yet practical.— “However we are still a long way away from practical systems that can build a rich enough model to avoid undesired side effects in a general sense.”limitations[2]
limitationThe review of work relevant to distributional shift is deliberately partial rather than exhaustive.— “Rather than fully reviewing all of this work in detail (which would necessitate a paper in itself), we will describe a few illustrative approaches and lay out some of their relative strengths and challenges.”limitations[3]
limitationThe paper's central term is stipulated so that it attributes a cause, which the ordinary word does not.— “We define accidents as unintended and harmful behavior that may emerge from machine learning systems when we specify the wrong objective function”limitations[4]
limitationA second definition of the same term appears in the same paper with a different cause named.— “the problem of accidents in machine learning systems, defined as unintended and harmful behavior that may emerge from poor design of real-world AI systems”limitations[5]
limitationThe risks are illustrated throughout with an invented example rather than a deployed system.— “For concreteness, we will illustrate many of the accident risks with reference to a fictional robot whose job is to clean up messes in an office using common cleaning tools”limitations[6]
limitationExtreme scenarios are excluded by choice, on the grounds that they cost precision.— “However, in our opinion one need not invoke these extreme scenarios to productively discuss accidents, and in fact doing so can lead to unnecessarily speculative discussions that lack precision”limitations[7]
Content tags
content-observations: finding · quantity · variable · definition · key-term — grounded in the full text
findingFive practical research problems related to accident risk: avoiding side effects, avoiding reward hacking, scalable supervision, safe exploration and distributional shift.— “We present a list of five practical research problems related to accident risk, categorized according to whether the problem originates from having the wrong objective function (“avoiding side effects” and “avoiding reward hacking”), an objective function that is too expensive to evaluate frequently (“scalable supervision”), or undesirable…content_tags.findings[0]
findingIn the authors' opinion, one need not invoke extreme scenarios.— “in our opinion one need not invoke these extreme scenarios”content_tags.findings[1]
quantityfive research problems — number of concrete accident-risk problems presented— “We present a list of five practical research problems related to accident risk”content_tags.quantities[0]
definitionaccidents— “the problem of accidents in machine learning systems, defined as unintended and harmful behavior that may emerge from poor design of real-world AI systems”content_tags.definitions[0]
definitionScalable oversight— ““Scalable oversight” (Section 5) discusses ideas for how to ensure safe behavior even given limited access to the true objective function”content_tags.definitions[1]
definitiondistributional shift— “undesirable behavior during the learning process (“safe exploration” and “distributional shift”)”content_tags.definitions[2]
key-termssafety, accidents, objective, learning, reward, exploration, systems, robustness, supervision
Concepts
terms this paper carries, each with the sentence it was cut from — the layer that joins one paper to another. Terms with no quote yet are on CONCEPTS.html.
conceptaccident— “We define accidents as unintended and harmful behavior that may emerge from machine learning systems when we specify the wrong objective function”concepts[4]
conceptaccident risk— “we frame mitigating accident risk (often referred to as “AI safety” in public discussions) in terms of classic methods in machine learning”concepts[5]
conceptobjective function— “We define accidents as unintended and harmful behavior that may emerge from machine learning systems when we specify the wrong objective function”concepts[6]
conceptside effects— “In “negative side effects”, the designer specifies an objective function that focuses on accomplishing some specific task in the environment, but ignores other aspects of the (potentially very large) environment, and thus implicitly expresses indifference over environmental variables that might actually be harmful to change.”concepts[7]
conceptsafe exploration— “including robustness, risk-sensitivity, and safe exploration”concepts[8]
conceptaccidents— “We define accidents as unintended and harmful behavior that may emerge from machine learning systems when we specify the wrong objective function”concepts[9]
conceptobjective function— “We define accidents as unintended and harmful behavior that may emerge from machine learning systems when we specify the wrong objective function”concepts[10]
Statistics — cross-field join keys
field-invariant statistical terms, used in their statistical sense (gated on a number / symbol / test). A p-value or a standard deviation means the SAME thing in physics, biology, psychology and sociology — so these are the strongest cross-field join keys. Grounded verbatim.
bootstrap as written: bootstrapping— “In the latter case, there has been interesting recent work on using bootstrapping to estimate finite-sample variation in the learned parameters of a neural network [114]; it seems worthwhile to better understand whether this approach can be used to effectively estimate out-of-sample performance in practice”content_tags.statistics[1]
hypothesis-testing— “that are potentially relevant to this problem, including change detection and anomaly detection [21, 80, 91], hypothesis testing [145], transfer learning [138, 124, 125, 25], and several others [136, 87, 18, 122, 121, 74…content_tags.statistics[3]
regression β as written: linear regressioncontent_tags.statistics[4]
not machine-vouchedregression — not-in-our-copy - The quote is in the original web page we fetched for this paper, but not in the text we tag against, which was extracted differently. Checked with ligatures, hyphens, spacing and punctuation set aside.content_tags.statistics[4]
variance σ²content_tags.statistics[5]

When we have changed our mind. Some entries in the table begin with a word in capitals and the reason for it. EVIDENCE CORRECTED — the finding still stands, but we had quoted the wrong sentence from the paper, and the quotation has been replaced with the right one. RETRACTED — the entry itself was wrong; it stays on the page, marked, with the reason, rather than being deleted. WITHDRAWN AND REPLACED — the entry was wrong, and a corrected version of it appears in the entries below. Each mark carries its own reason, in brackets, because the reasons differ from one entry to the next. An entry we have WITHDRAWN is removed from this page and kept in the record, with its reason. A line reading Audit and a date is a later re-reading of the entry against its whole sentence: DOUBTFUL means it was kept, and the reason says what is loose about it. Quotation marks inside the tagger's sentence. Where a tag is the tagger's own sentence, a phrase in quotation marks inside it is borrowed from the paper — the tagger's wording around it is not. The paper's own sentence is the evidence quote for that row; on this page it is withheld with the article, and the article is at its publisher. Nothing inside quotation marks anywhere on this page is ours: if it is quoted, it is the paper's. Whose words a concept carries. A concept entry records a term the paper itself uses, so the term, the sense given for it, and its evidence are the paper's own words, quoted where the paper fixes them. This is the opposite of a sense entry in the tag table, which is the tagger's sentence about how the paper uses a term. Where a concept entry could not be grounded in the paper's words, the entry says so on its own row.

Tag layer © the Meta-Tagging Project, CC BY 4.0. The paper text is © its authors/publisher and is linked, not reproduced. Excerpts shown are short quotations for identification and verification. · back to index · concepts · authors · עברית
© 2026 Shir Sivroni · ORCID 0009-0000-2597-2824