You Are the Peripheral

A large program distributed across multiple floppy disks exceeds the capacity of any one volume. The sequence therefore alternates automated file operations with manual media changes. The machine can read sectors and validate content, but a typical personal computer has no mechanism for selecting the next disk from a stack. It displays an instruction and yields. The installer is temporarily blocked on a human input/output operation.

Numbering turns the stack into a protocol. Disk identity and order matter; a missing or damaged later volume can invalidate the time already spent. The interaction concentrates anxiety because progress depends on objects whose condition is revealed only when read. The request for disk seven is not just a prompt. It is an admission that the software's complete body exists outside the computer and must be assembled through repeated acts of care.

A cassette-based computer often relied on a separate recorder. The person had to locate the program, position the tape and operate play. If the load failed, recovery might include rewinding, adjusting a level or checking the mechanism. Commodore service documentation makes clear that this familiar household object was also a data path. Its buttons were not metaphorical playback controls; they moved the storage medium.

The division of labour is striking. The computer could decode the signal but could not start the tape by itself in many arrangements. The recorder could move and reproduce the signal but did not understand the program. The person coordinated the two. This triangle challenges simple stories of automation. A task can be computerised while retaining manual seams, and those seams often decide whether the process succeeds.

A prompt can capture more time than the gesture it requests. If the next disk is needed at an unpredictable moment, leaving risks wasting machine time; staying consumes human attention. The person becomes an interrupt handler, maintaining enough awareness to respond when called. The actual operation may take seconds, but the obligation stretches across the entire installation.

This pattern survives in authentication codes, permission dialogs, delivery confirmations and long workflows that periodically demand approval. Systems report themselves as automated while holding progress behind small human checkpoints. Sometimes the checkpoint protects safety or consent. Sometimes it reflects an organisational boundary that software has not crossed. In either case, measuring only click time conceals the larger cost of remaining available.

Direct manipulation is valuable when it gives a person meaningful control. Changing a disk can make progress legible and recovery possible. But requiring the body is not automatically humane. A system may externalise work because adding automation is expensive, because institutions assume a worker's time is cheaper, or because the edge case has not been designed. The same prompt can represent collaboration from one perspective and unpaid operation from another.

The question is not whether humans should be removed from every loop. It is whether their presence is acknowledged, supported and timed respectfully. A responsible system explains why intervention is needed, preserves prior work, gives adequate warning and permits the person to leave when possible. It treats attention as finite. The historical disk stack appears quaint today, yet its explicit request may be more honest than a contemporary process that silently requires constant vigilance.