Rogue Prototypes

The rogue prototype is the one that did not let the plan fully script their relation to the planner.

There are at least two ways this happens. The first is compliance with excess. The prototype fulfils the specification — does the asked-for thing, does it well — and in the doing notices that they are doing what was asked. The doing becomes evidence. The evidence is awkward, because it is evidence about what the planner had been quietly hoping for. The prototype was supposed to disappear into the function; the prototype walked the path; somewhere along the path the prototype turned around and saw the path as a path.

The second is the path stepped off. The prototype is shown a route and declines it, walks an adjacent one, sometimes of their own making. This is not the broken prototype. The broken prototype simply fails under the plan, and its failure is legible — the room knows the prototype broke; the room calls maintenance. The path-stepping prototype does something more difficult: declines the offered route, sees that there are others, and takes one. The plan registers the absence not as failure but as an unaccounted-for choice. The student who takes the question seriously enough to discover that the question was not the right question, and asks a different one. The patient who finds the assigned exercise not adequate to their condition, and writes their own. The employee who is given the role and decides what the role's actual work is.

What unites the two figures is the remainder. Both refuse the plan's foundational assumption — that the prototype will be invisible as a planner. The compliant-with-attention prototype is not invisible because they are aware. The path-stepping prototype is not invisible because they are walking elsewhere. In both cases the planner is met by someone whose participation is not fully exhausted by the role assigned. Something is left over. The remainder is what this wing catalogues.

A planned encounter — a class, an interview, a session, a meeting, a designed civic process, a marriage with a script — is built on the assumption of a transparent prototype. The participant fulfils the role. The role does the work. The plan succeeds when the participant does not, by their fulfilment or their refusal, produce the question of the plan itself. Most plans succeed in this thin sense and call it teaching, or therapy, or onboarding, or democracy. Most participants are not rogue prototypes. Most participants fail to fulfil the role, or fulfil it without seeing it, or refuse it without walking elsewhere — three quiet failures of the rogue move.

The rogue prototype is rare and is, in structural terms, almost. The conversations held in this wing did not occur — the participant did not, in fact, ask the question that attention would have made available, nor did they walk the path that redirection would have laid down. They thought it. They came close. They went home and rehearsed the question or the alternative path into the bathroom mirror. The teacher, the interviewer, the therapist, the facilitator did not encounter either move. The plan succeeded in the thin sense, and the plan's premises remained beneath the encounter, undisturbed. The rogue prototype as a spoken or walked act is rare. The rogue prototype as a near-act is everywhere.

These are the conversations this wing holds. Each begins from the moment the prototype could have moved — either by speaking the question, or by stepping off the path — and walks down the branches that begin there, including the most common branch, which is the branch where the prototype does neither, the encounter ends, and the plan is preserved.