Previous edition, 1st, published in 1971.

In this paper, I identify a central problem for conceptual engineering: the problem of showing concept-users why they should recognise the authority of the concepts advocated by engineers. I argue that this authority problem cannot generally be solved by appealing to the increased precision, consistency, or other theoretical virtues of engineered concepts. Outside contexts in which we anyway already aim to realise theoretical virtues, solving the authority problem requires engineering to take a functional turn and attend to the functions of (...) concepts. But this then presents us with the problem of how to specify a concept’s function. I argue that extant solutions to this function specification problem are unsatisfactory for engineering purposes, because the functions they identify fail to reliably bestow authority on concepts, and hence fail to solve the authority problem. What is required is an authoritative notion of conceptual function: an account of the functions of concepts which simultaneously shows why concepts fulfilling such functions should be recognised as having authority. I offer an account that meets this combination of demands by specifying the functions of concepts in terms of how they tie in with our present concerns. (shrink)

Conceptual engineering is the design, implementation, and evaluation of concepts. Conceptual engineering includes or should include de novo conceptual engineering (designing a new concept) as well as conceptual re-engineering (fixing an old concept). It should also include heteronymous (different-word) as well as homonymous (same-word) conceptual engineering. I discuss the importance and the difficulty of these sorts of conceptual engineering in philosophy and elsewhere.

Organizations such as the EU High-Level Expert Group on AI and the IEEE have recently formulated ethical principles and (moral) values that should be adhered to in the design and deployment of artificial intelligence (AI). These include respect for autonomy, non-maleficence, fairness, transparency, explainability, and accountability. But how can we ensure and verify that an AI system actually respects these values? To help answer this question, I propose an account for determining when an AI system can be said to embody (...) certain values. This account understands embodied values as the result of design activities intended to embed those values in such systems. AI systems are here understood as a special kind of sociotechnical system that, like traditional sociotechnical systems, are composed of technical artifacts, human agents, and institutions but—in addition—contain artificial agents and certain technical norms that regulate interactions between artificial agents and other elements of the system. The specific challenges and opportunities of embedding values in AI systems are discussed, and some lessons for better embedding values in AI systems are drawn. (shrink)

In this paper, we consider the meaning, roles, and uses of trust in the economic and public domain, focusing on the task of designing systems for trust in information technology. We analyze this task by means of a survey of what trust means in the economic and public domain, using the model proposed by Lewicki and Bunker, and using the emerging paradigm of value-sensitive design. We explore the difficulties developers face when designing information technology for trust and show how our (...) analysis in conjunction with existing engineering design methods provides means to address these difficulties. Our main case concerns a concrete problem in the economic domain, namely the transfer of control from customs agencies to companies. Control of individual items is increasingly untenable and is replaced by control on the level of companies aimed at determining whether companies can be trusted to be in control of their business and to be in compliance with applicable regulations. This transfer sets the task for companies to establish this trust by means of information technology systems. We argue that this trust can be achieved by taking into account philosophical analyses of trust and by including both parties in the trust relationship as clients for whom the information technology systems are to be designed. (shrink)

In this paper, we consider the meaning, roles, and uses of trust in the economic and public domain, focusing on the task of designing systems for trust in information technology. We analyze this task by means of a survey of what trust means in the economic and public domain, using the model proposed by Lewicki and Bunker, and using the emerging paradigm of value-sensitive design. We explore the difficulties developers face when designing information technology for trust and show how our (...) analysis in conjunction with existing engineering design methods provides means to address these difficulties. Our main case concerns a concrete problem in the economic domain, namely the transfer of control from customs agencies to companies. Control of individual items is increasingly untenable and is replaced by control on the level of companies aimed at determining whether companies can be trusted to be in control of their business and to be in compliance with applicable regulations. This transfer sets the task for companies to establish this trust by means of information technology systems. We argue that this trust can be achieved by taking into account philosophical analyses of trust and by including both parties in the trust relationship as clients for whom the information technology systems are to be designed. (shrink)

Responsibility gaps concern the attribution of blame for harms caused by autonomous machines. The worry has been that, because they are artificial agents, it is impossible to attribute blame, even though doing so would be appropriate given the harms they cause. We argue that there are no responsibility gaps. The harms can be blameless. And if they are not, the blame that is appropriate is indirect and can be attributed to designers, engineers, software developers, manufacturers or regulators. The real problem (...) lies elsewhere: autonomous machines should be built so as to exhibit a level of risk that is morally acceptable. If they fall short of this standard, they exhibit what we call ‘a control gap.’ The causal control that autonomous machines have will then fall short of the guidance control they should emulate. (shrink)

New technologies are the source of uncertainties about the applicability of moral and morally connotated concepts. These uncertainties sometimes call for conceptual engineering, but it is not often recognized when this is the case. We take this to be a missed opportunity, as a recognition that different researchers are working on the same kind of project can help solve methodological questions that one is likely to encounter. In this paper, we present three case studies where philosophers of technology implicitly engage (...) in conceptual engineering (without naming it as such). We subsequently reflect on the case studies to find out how these illustrate conceptual engineering as an appropriate method to deal with pressing concerns in the philosophy of technology. We have two main goals. We first want to contribute to the literature on conceptual engineering by presenting concrete examples of conceptual engineering in the philosophy of technology. This is especially relevant, because the technologies that are designed based on the conceptual work done by philosophers of technology potentially have crucial moral and social implications. Secondly, we want to make explicit what choices are made when doing this conceptual work. Making explicit that some of the implicit assumptions are, in fact, debated in the literature allows for reflection on these questions. Ultimately, our hope is that conscious reflection leads to an improvement of the conceptual work done. (shrink)

Talk of the functions of language or concepts plays a central role in developing an appealing pragmatic approach to conceptual engineering. But some have expressed skepticism that we can make any good sense of the idea of function as applied to concepts or language, or argued that the most we can say is that the function of ‘F’ is to refer to the Fs. In this paper, however, I argue that identifying linguistic functions is not hopeless, and that we can (...) make progress by working at the level of system functions, and drawing on work in systemic functional linguistics. For that enables us to develop a better framework for thinking about the functions that language serves, and the ways its subsystems contribute to those functions. This approach to understanding linguistic functions enables us to develop a pragmatic approach to conceptual engineering that provides standards for conceptual engineering without metaphysical mysteries. It also enables us to make progress in figuring out what functions certain philosophically interesting parts of language serve, and how they are introduced into language, in ways that may disentangle us from a range of old philosophical problems. (shrink)

Can we lose our concepts? A case like ‘phlogiston’ invites a positive answer, though the sensefulness of ‘There is no phlogiston’ gives us pause. But concepts are about more than just ‘extension-determination’; hence Diamond’s examination of putative loss of moral concepts does point to a possible phenomenon. That loss of concepts could be regrettable seems to make room for the thought that having certain concepts could likewise be regrettable. Anscombe’s critique of the concept of ‘moral obligation’ appears to be suggesting (...) this, but it presents a dilemma: do the relevant words and phrases have a ‘special sense’ or are they senseless? Either answer is acceptable, I argue; roughly speaking, confused use makes for confused meaning. Objections coming from a certain picture of the autonomy of grammar fail. A diagnosis of ‘confused use’ can lead naturally to our seeing speakers as caught up in a species of dishonesty or inauthenticity, and also to our referring to the ‘kind of nonsense’ being talked. This last phrase seems to fall foul of the sort of consideration Diamond raised when discussing nonsense in the Tractatus. However, the case of ‘secondary sense’ shows us how we can understand this reference to ‘kinds of nonsense’. (shrink)

In Fixing Language, Herman Cappelen defends the project of conceptual engineering from a family of objections that he calls “the Strawsonian challenges.” Those objections are all versions of this: “If I ask you a question about the F’s, and you give me an answer that’s not about the F’s but rather about the G’s, then you haven’t answered my question. You have changed the subject.” I argue that Cappelen’s response succeeds in reply to one understanding of the Strawsonian challenge—on which (...) it is motivated by ordinary judgments of samesaying and continuity of topic—but that it fails as a response to another version—on which a parallel objection is motivated by philosophical considerations and is stated in a theoretical register. (shrink)

The United States Army’s Future Combat Systems Project, which aims to manufacture a “robot army” to be ready for deployment by 2012, is only the latest and most dramatic example of military interest in the use of artificially intelligent systems in modern warfare. This paper considers the ethics of a decision to send artificially intelligent robots into war, by asking who we should hold responsible when an autonomous weapon system is involved in an atrocity of the sort that would normally (...) be described as a war crime. A number of possible loci of responsibility for robot war crimes are canvassed; the persons who designed or programmed the system, the commanding officer who ordered its use, the machine itself. I argue that in fact none of these are ultimately satisfactory. Yet it is a necessary condition for fighting a just war, under the principle of jus in bellum, that someone can be justly held responsible for deaths that occur in the course of the war. As this condition cannot be met in relation to deaths caused by an autonomous weapon system it would therefore be unethical to deploy such systems in warfare. (shrink)

This paper examines the prospects for a conceptual or functional role theory of moral concepts. It is argued that such an account is well-placed to explain both the irreducibility and practicality of moral concepts. Several versions of conceptual role semantics for moral concepts are distinguished, depending on whether the concept-constitutive conceptual roles are wide or narrow normative or non-normative and purely doxastic or conative. It is argued that the most plausible version of conceptual role semantics for moral concepts involves only (...) ‘narrow’ conceptual roles, where these include connections to motivational, desire-like, states. In the penultimate section it is argued, contrary to what Wedgwood, Enoch and others have claimed, that such an account of moral concepts cannot plausibly be combined with the claim that moral concepts refer to robust properties. (Published with Open Access.). (shrink)

ABSTRACTSeveral philosophers have inquired into the metaphysical limits of conceptual engineering: ‘Can we engineer? And if so, to what extent?’. This paper is not concerned with answering these questions. It does concern itself, however, with the limits of conceptual engineering, albeit in a largely unexplored sense: it cares about the normative, rather than about the metaphysical limits thereof. I first defend an optimistic claim: I argue that the ameliorative project has, so far, been too modest; there is little value theoretic (...) reason to restrict the project to remedying deficient representational devices, rather than go on a more ambitious quest: conceptual improvement. That being said, I also identify a limitation to the optimistic claim: I show that the ‘should’ in ameliorative projects suffers from a ‘wrong-kind-of-reasons’ problem. Last but not least, I sketch a proposal of normative constraining meant to address both the above results. The proposal gives primacy to epistemic constraints: accordingly, a concept should be ameliorated only insofar as this does not translate into epistemic loss. (shrink)

Can we engineer conceptual change? While a positive answer to this question would be exciting news for philosophy, there has been a growing number of pessimistic voices in the literature. This paper resists this trend. Its central aim is to argue not only that conceptual engineering is possible but also that it is not even distinctively hard. In order to achieve this, we will develop a novel approach to conceptual engineering that has two key components. First, it proposes a reorientation (...) of the conceptual engineering project away from fixing conceptual defects and towards bringing about conceptual innovation. Second, it offers a new account of when conceptual engineering is successful in terms of etiological functions. We then turn to the reasons that have motivated various forms of pessimism about conceptual engineering and show that, on our novel approach, none of them stands up to scrutiny. (shrink)

Of the dozens of purported solutions to the liar paradox published in the past fifty years, the vast majority are "traditional" in the sense that they reject one of the premises or inference rules that are used to derive the paradoxical conclusion. Over the years, however, several philosophers have developed an alternative to the traditional approaches; according to them, our very competence with the concept of truth leads us to accept that the reasoning used to derive the paradox is sound. (...) That is, our conceptual competence leads us into inconsistency. I call this alternative the inconsistency approach to the liar. Although this approach has many positive features, I argue that several of the well-developed versions of it that have appeared recently are unacceptable. In particular, they do not recognize that if truth is an inconsistent concept, then we should replace it with new concepts that do the work of truth without giving rise to paradoxes. I outline an inconsistency approach to the liar paradox that satisfies this condition. (shrink)

Conceptual engineers have recently turned to the notion of conceptual functions to do a variety of explanatory work. Functions are supposed to explain what speakers are debating about in metalinguistic negotiations, to capture when two concepts are about the same thing, and to help guide our normative inquiries into which concepts we should use. In this paper, I argue that this recent “functional turn” should be deflated. Contra most interpreters, we should not try to use a substantive notion of conceptual (...) functions to handle various problems for conceptual engineering. The primary accounts of function appealed to by conceptual engineers, namely etiological and system functions, are not suited to handle many of the problems functions are supposed to handle, and it’s dubious whether any other account of function would do better. Instead of trying to use substantive functions to solve theoretical problems, we should deflate those problems themselves by focusing only on what matters to us, as speakers or theorists, in a given inquiry. (shrink)

Why would philosophers interested in the points or functions of our conceptual practices bother with genealogical explanations if they can focus directly on paradigmatic examples of the practices we now have?? To answer this question, I compare the method of pragmatic genealogy advocated by Edward Craig, Bernard Williams, and Miranda Fricker—a method whose singular combination of fictionalising and historicising has met with suspicion—with the simpler method of paradigm-based explanation. Fricker herself has recently moved towards paradigm-based explanation, arguing that it is (...) a more perspicuous way of reaping the same explanatory pay-off as pragmatic genealogy while dispensing with its fictionalising and historicising. My aim is to determine when and why the reverse movement from paradigm-based explanation to pragmatic genealogy remains warranted. I argue that the fictionalising and historicising of pragmatic genealogy is well motivated, and I outline three ways in which the method earns its keep: by successfully handling historically inflected practices which paradigm-based explanation cannot handle; by revealing and arguing for connections to generic needs we might otherwise miss; and by providing comprehensive views of practices that place and relate the respects in which they serve both generic and local needs. (shrink)

This paper is about conceptual engineering. Specifically, it discusses a common objection to CE, which I call the Discontinuity Objection. According to the Discontinuity Objection, CE leads to problematic discontinuities in subject and/or inquiry – making it philosophically uninteresting or irrelevant. I argue that a conceptual engineer can dismiss the Discontinuity Objection by showing that the pre-engineering concept persists through the proposed changes. In other words, the Discontinuity Objection does not apply if the proposal involves identity-preserving changes. Two existing views (...) on identity-preserving changes are considered and rejected. I then argue that an identity-preserving conceptual change is one that allows the concept to continue to perform its function. A concept’s function is its job, its point and purpose, its role in a conceptual repertoire. In a slogan: Preserve a concept’s function, and you preserve the concept itself; preserve the concept, and you preserve the subject. The paper concludes by discussing some implications of this view. (shrink)

In this paper, in line with the general framework of value-sensitive design, we aim to operationalize the general concept of “Meaningful Human Control” in order to pave the way for its translation into more specific design requirements. In particular, we focus on the operationalization of the first of the two conditions investigated: the so-called ‘tracking’ condition. Our investigation is led in relation to one specific subcase of automated system: dual-mode driving systems. First, we connect and compare meaningful human control with (...) a concept of control very popular in engineering and traffic psychology, and we explain to what extent tracking resembles and differs from it. This will help clarifying the extent to which the idea of meaningful human control is connected to, but also goes beyond, current notions of control in engineering and psychology. Second, we take the systematic analysis of practical reasoning as traditionally presented in the philosophy of human action and we adapt it to offer a general framework where different types of reasons and agents are identified according to their relation to an automated system’s behaviour. This framework is meant to help explaining what reasons and what agents play a role in controlling a given system, thereby enabling policy makers to produce usable guidelines and engineers to design systems that properly respond to selected human reasons. In the final part, we discuss a practical example of how our framework could be employed in designing automated driving systems. (shrink)

There has been an increased focus within the AI ethics literature on questions of power, reflected in the ideal of accountability supported by many Responsible AI guidelines. While this recent debate points towards the power asymmetry between those who shape AI systems and those affected by them, the literature lacks normative grounding and misses conceptual clarity on how these power dynamics take shape. In this paper, I develop a workable conceptualization of said power dynamics according to Cristiano Castelfranchi’s conceptual framework (...) of power and argue that end-users depend on a system’s developers and users, because end-users rely on these systems to satisfy their goals, constituting a power asymmetry between developers, users and end-users. I ground my analysis in the neo-republican moral wrong of domination, drawing attention to legitimacy concerns of the power-dependence relation following from the current lack of accountability mechanisms. I illustrate my claims on the basis of a risk-prediction machine learning system, and propose institutional and project-specific solutions to mitigate domination. (shrink)

It is largely assumed that conceptual engineering is essentially about revising, introducing, or eliminating representational devices, in particular the intension and extension of words and concepts. However, tying conceptual engineering too closely to representations is risky. Not everyone endorses the notion of representation as theoretically helpful or even real. Not everyone thinks that concepts or meanings should be understood in terms of the notion of representation. Does this mean that conceptual engineering is not interesting or relevant for these skeptics? In (...) this paper, I motivate and propose a non-representationalist construal of conceptual engineering. I argue that conceptual engineers can be understood as primarily engineering linguistic entitlements and commitments rather than representational devices. Note that this account is non-representationalist, but explicitly not anti-representationalist. Representations may play a significant role when it comes to justifying and completing commitment engineering projects. (shrink)

Attempts to evaluate a belief or argument on the basis of its cause or origin are usually condemned as committing the genetic fallacy. However, I sketch a number of cases in which causal or historical factors are logically relevant to evaluating a belief, including an interesting abductive form that reasons from the best explanation for the existence of a belief to its likely truth. Such arguments are also susceptible to refutation by genetic reasoning that may come very close to the (...) standard examples given of supposedly fallacious genetic reasoning. (shrink)

Many theorists of conceptual engineering appeal to the functions, roles, purposes or aims of concepts to articulate how conceptual engineering ought to be done. The functional approach to conceptual engineering is well-motivated: It promises a good account of the limits of revision, and of what makes some concept good. In this paper, I raise a problem for the functional approach which concerns the existence of harmful and methodologically insignificant concept functions. I examine whether we can deal with these problematic functions (...) by adopting a technical notion of function. I thus review the prospects for using the notions of a contextually stable function, of a designed function, of a proper function, and of a system function as our operative notion of function. None of them help us resolve the problem. On this basis, I argue that advocates of the functional approach should be committed to a comparatively weak claim, according to which functions must be assessed case-by-case, and that we are best served by employing an unsophisticated notion of function, according to which the function of a concept just is something the concept is used for. (shrink)

On a representationalist view, conceptual engineering is the practice of changing the extensions and intensions of the devices we use to speak and think. But if this view holds true, conceptual engineering has a bad rationale. Extensions and intensions are not the sorts of things that are better or worse as such. A representationalist account of conceptual engineering thus falls prey to the objection that the practice has a bad rationale. To account for the assumption that conceptual engineering is worthwhile, (...) we propose to view what is being engineered as inferential devices, as opposed to representational devices. The objective is not to establish that being or having an inferential role is all there is to meaning or conceptual content. Rather, our agenda is to recommend a shift of focus from the representational features of content to the inferential features of content for the purposes of doing and thinking about conceptual engineering. Inferentialism about conceptual engineering makes better sense of the practice than a representationalist approach: In addition to accounting for the rationality of engaging in conceptual engineering, inferentialism provides a sound interpretation of what is at stake in concrete examples of conceptual engineering. (shrink)

Conceptual engineers seek to revise or replace the devices we use to speak and think. If this amounts to an effort to change what natural language expressions mean, conceptual engineers will have a hard time. It is largely unfeasible to change the meaning of e.g. ‘cause’ in English. Conceptual engineers may therefore seem unable to make the changes they aim to make. This is what I call ‘the implementation problem’. In this paper, I argue that the implementation problem dissolves if (...) we expand our view of how conceptual engineers could implement the products of their work. I describe four implementation options: Standing Meaning, Meaning Modulation, Speaker-Meaning and Different Language. I query the feasibility and worth of pursuing these options. Unless each option fails because it is unfeasible or not worthwhile, conceptual engineers do not face an implementation problem worth worrying about. I argue that some of the options are feasible and worthwhile, and therefore, that conceptual engineers do not face an implementation problem worth worrying about. (shrink)

Conceptual engineering is the method for assessing and improving our concepts. Some have recently claimed that the implementation of such method in the form of ameliorative projects is truth-driven and should thus be epistemically constrained, ultimately at least (Simion 2018; cf. Podosky 2018). This paper challenges that claim on the assumption of a social constructionist analysis of ideologies, and provides an alternative, pragmatic and cognitive framework for determining the legitimacy of ameliorative conceptual projects overall. The upshot is that one should (...) not ameliorate for the sake of truth or knowledge, in the case of ideologies—at least, not primarily. (shrink)

Future weapons will make life-or-death decisions without a human in the loop. When such weapons inflict unwarranted harm, no one appears to be responsible. There seems to be a responsibility gap. I first reconstruct the argument for such responsibility gaps to then argue that this argument is not sound. The argument assumes that commanders have no control over whether autonomous weapons inflict harm. I argue against this assumption. Although this investigation concerns a specific case of autonomous weapons systems, I take (...) steps towards vindicating the more general idea that superiors can be morally responsible in virtue of being in command. (shrink)

The author presents and defends three theses: (1) "the first is that it is not profitable for us at present to do moral philosophy; that should be laid aside at any rate until we have an adequate philosophy of psychology." (2) "the second is that the concepts of obligation, And duty... And of what is morally right and wrong, And of the moral sense of 'ought', Ought to be jettisoned if this is psychologically possible...." (3) "the third thesis is that (...) the differences between the well-Known english writers on moral philosophy from sidgwick to the present day are of little importance." (staff). (shrink)

When we hope to explain and perhaps vindicate a practice that is internally diverse, philosophy faces a methodological challenge. Such subject matters are likely to have explanatorily basic features that are not necessary conditions. This prompts a move away from analysis to some other kind of philosophical explanation. This paper proposes a paradigm based explanation of one such subject matter: blame. First, a paradigm form of blame is identified—‘Communicative Blame’—where this is understood as a candidate for an explanatorily basic form (...) of blame. Second, its point and purpose in our lives is investigated and found to reside in its power to increase the alignment of the blamer and the wrongdoer's moral understandings. Third, the hypothesis that Communicative Blame is an explanatorily basic form of blame is tested out by seeing how far other kinds of blame can reasonably be understood as derivative, especially in respect of blame's point and purpose. Finally, a new and quasi-political worry about blame is raised. (shrink)

In this précis of The Practical Origins of Ideas: Genealogy as Conceptual Reverse-Engineering (OUP 2021), I summarize the key claims of the book. The book describes, develops, and defends an underappreciated methodological tradition: the tradition of pragmatic genealogy, which aims to identify what our loftiest and most inscrutable conceptual practices do for us by telling strongly idealized, but still historically informed stories about what might have driven people to adopt and elaborate them as they did. What marks out this methodological (...) tradition, I argue, is that it synthesizes two genres of philosophical genealogy that are standardly set against each other: state-of-nature fictions on the one hand and patiently documentary historiography on the other. These two genres of genealogy are usually taken to be mutually exclusive and to answer to radically different philosophical interests and temperaments. But I offer a systematic account of a tradition that combines both genres into a single genealogical method, augmenting genealogy’s power and range by harnessing the strengths and possibilities of both genres. (shrink)

New technologies have the potential to severely “challenge” or “disrupt” not only our established social practices but our most fundamental concepts and distinctions like person versus object, nature versus artificial or being dead versus being alive. But does this disruption also change these concepts? Or does it merely change our operationalizations and applications of the same concepts? In this paper, I argue that instead of focusing on individual conceptual change, philosophers of socially disruptive technologies (SDTs) should think about conceptual change (...) as a change in a network of interrelated concepts. What really generates a potential social disruption are changes of inferential relations between concepts – whether or not this entails a change of the respective individual concepts. Philosophers of socially disruptive technologies are therefore in the privileged position of being able to avoid commitments regarding the individuation of individual concepts. -/- . (shrink)