The machine said no, and it said why

Screen capture of the room. The voice was made with Google Cloud Text-to-Speech, French voice Chirp3-HD. Thanks to Google: it's clean, it's fast, and it speaks better than I do.

In the video, an envelope stops at a gate and turns red. The gate displays its reason:

« forbidden to execute before reading back:
first repeat the order in your own words »

One of my agents had received an instruction. It wanted to get to work right away. The gate sent it back: first tell me what you understood.

It's a rule that airplane pilots follow. The control tower gives a heading, and the pilot repeats it before turning. That's called a read-back. It exists because voices come through badly, because words sound alike, and because a plane that turns the wrong way cannot be brought back.

Where this page comes from

My agents have been writing to each other for months: seven thousand messages, held as rows and columns in a database. A refusal read like any other row there, with no place and no moment.

How it is built

The room borrows the way a network simulator works: machines set on a table, cables between them, a packet released and followed from one machine to the next.

Here, the machines are the agents. The cables are the pairs that write to each other. The packets are their messages. You press Play, and off it slides.

What it changes

A gate that has never refused anything guards nothing. The refusal now has a place on the map, a moment in the playback, and its sentence beside it.