Signature vs. Password

In The You On AI Encyclopedia

The signature presupposed the individual as its reference. It was the graphical trace of a unique hand, bound to a specific body, difficult to forge and personally inscribed in every instance of its use. Banks, contracts, legal documents, and institutional records operated through signatures precisely because they depended on the presumption of indivisible persons whose identity could be verified through this embodied trace. The signature made the individual legible to power as a whole person.

The password has none of these properties. It is not bound to a body but to a database. It is not unique to a person but assigned by a system. It can be given to another person, stored in a password manager, generated and revoked automatically, and — critically — it has no reference to who you are, only to what you can access. The password is the atomic unit of the dividual; it fragments identity into access rights that can be granted and revoked independently of the person.

The analytical power of this distinction becomes clear in the AI context. When a developer works with Claude Code or another AI platform, the relationship is mediated entirely by passwords: API keys, subscription credentials, authentication tokens, terms-of-service agreements. The system does not know the developer as a whole person. It knows the dividual assembled from the developer's interactions, and it grants or revokes access through codes that bear no necessary relationship to the developer's identity. A credential violation can suspend the developer's access without notice, as the Deleuze volume documents in its account of the São Paulo developer whose work was mid-stream when her API access was revoked. The walls did not close in; the door simply ceased to exist.

The password architecture also reshapes the phenomenology of exclusion. Disciplinary exclusion was visible and contestable: the locked gate, the barred door, the wall that could be scaled or torn down. Contestation required a body in a space, a presence that could be made visible to others. Password-based exclusion is invisible and non-spatial: the authentication failure happens silently, in the moment between typing a credential and receiving a response. There is no gate to stand at, no door to block, no wall to scale. There is only the code that works or does not work.

Origin

Deleuze introduced the distinction in the Postscript's central paragraph: In the disciplinary societies one was always starting again (from school to the barracks, from the barracks to the factory), while in the societies of control one is never finished with anything... the key thing is no longer a signature or a number, but a code: the code is a password. The formulation draws on Foucault's analyses of the signature in disciplinary record-keeping while extending them toward a mode of power Foucault did not live to analyze.

Key Ideas

The signature identifies; the password authenticates. Identity requires that power know who you are; authentication only requires that power verify that the credential is valid.

The signature belongs to the person; the password belongs to the system. A signature is an embodied trace that the individual produces; a password is a system-generated credential that the person merely possesses.

Passwords can be revoked; signatures cannot. The shift from signature to password transfers control over identity from the person to the institution that manages the credential.

The password architecture makes exclusion invisible. Disciplinary exclusion produced visible sites of resistance; password-based exclusion happens silently, without an architecture to picket or occupy.

Every AI interaction is password-mediated. The entire infrastructure of AI-augmented work operates through codes — API keys, subscriptions, tokens, terms of service — that can be modulated without warning.