Conceptual Engineering

From metaphor use to recalibration

This perspective is built from parts one and two of Change and Stability, treated as a single developing artifact. Part one assembles the devices from familiar materials: the operating system becomes a penguin or a puzzle, a piece of software becomes a written document. Part two puts those devices to work — installation, removal, updates, the system's shape and state — and, crucially, shows where each one stops carrying the distinction we need.

That movement is why the marker sits at Iterative Recalibration rather than its nearest neighbor, Concept Evaluation. The puzzle makes modularity and changes of shape visible, but struggles with state. The penguin can show health and impairment at a glance. The written document clarifies updates and downgrades — and loses the state again. Instead of declaring one device the winner, the artifact switches, recovers, and combines. Evaluation feeds another round of design, right there in the recorded work. The same evidence grounds the Plural Repertoire: replacement stays local to a purpose, and useful older devices remain on the shelf.

Evaluation, reach, and medium

Practical Intelligibility is the primary test because these devices succeed only if a non-specialist reader can use them to tell technical situations apart and navigate them. Multimodal Representation records how that test is run: prose, illustrations, and visual metaphor sharing the load, with language no longer carrying the apparatus alone.

Implementation stops at Authored Artifact. The piece enacts the practice it calls conceptual engineering, but it doesn't ask any community to adopt the term. If it ever did change how a domain speaks, that would justify recalibrating this coordinate — the map is allowed to grow, too.

This perspective is built from one text alone — Chalmers's What Is Conceptual Engineering and What Should It Be? — not from the author's wider philosophical corpus. The paper explicitly organizes conceptual engineering around designing, implementing, and evaluating concepts, which puts the marker at Concept Evaluation. Engineering is described as an intertwined, potentially recurring process, but the paper never shows an evaluated concept going back through another round of design — so Iterative Recalibration would overclaim.

The Plural Repertoire selection follows from the paper's generous scope: de novo construction and conceptual re-engineering, combined with role-sensitive pluralism. Repair or replacement is too narrow — an inherited concept need not disappear just because another one serves a different purpose better. Explanatory Fruitfulness is the nearest evaluative seat, because the paper's central tests of fitness are the roles a concept plays and the theses and questions it makes available.

For implementation, the paper moves beyond private specification toward actual use of an expression by a relevant community. The map seats that demand at Domain Community Uptake — while keeping the paper's own caveat that entrenched usage makes this socially difficult. The mechanism is principally Discursive Use: use the expression accordingly, and bring others into the practice. These coordinates describe the account developed in this one paper; they don't claim that every kind of conceptual engineering has to travel the same medium or the same distance.