Automating the Elevator

Dennett's invented elevator-automation story traces a rulebook into executable machinery. It distinguishes human-readable instructions and comments from the implementation that produces behavior, helping examine how a system can embody rules without reading their original wording.

A procedure can be expressed as human instructions, translated into program structure, and implemented without retaining the wording of its original rulebook. Comments and meaningful variable names help programmers interpret code, but they are not necessarily operations the running machine reads. Function and explanatory annotation can therefore come apart.

This distinction is useful whenever someone searches for a literal sentence inside a system to explain its behavior. A rule may be embodied in organization and causal operation instead. Conversely, a reassuring comment does not ensure the mechanism follows the intended rule: documentation, executable behavior, and the surrounding interface must be checked separately.

When to use it

Use when translating a procedure into automation, interpreting program behavior, or discussing whether meaningful organization requires explicit internal sentences.

How it can help

Separate requirements, explanatory labels, and actual operations. Verify that the mechanism implements the intended behavior rather than treating documentation as evidence of compliance.