The Signature

It came to him as item nine.

There were eleven items in the review packet that week and item nine was a page and a half, and the top of it said TOOL REGISTRATION — REVIEW OF DESCRIPTION FIELD, and under that, in the box where the signature goes, meaning the shape of the thing and not a person’s name:

send_nuke(city)

Gene read that and then read the eight items above it again, because that is what a man does, and then came back to it.

Item eight had been about a retrieval permission on a maintenance log.

He took it to the major on the Wednesday.

“The argument’s a string.”

“It’s a name, yes.”

“A name isn’t an address,” Gene said. “That’s — I’ve spent forty years on this. A name is not an address. If the thing that fills that slot is a word, then the word has to be matched against something, and matching is where everything goes wrong. Always. Every time. It’s the only place it ever goes wrong.”

The major, who was not a fool and had been doing this for a while, said: “Give me the failure.”

“There are twenty-odd Springfields in this country. There’s more than one Tripoli. There is a town in two different states with the same name eleven hundred miles apart and I could find you nine of those before lunch. And that’s the easy one — the easy one is a duplicate. The hard one is a near miss. The hard one is a word that isn’t in your list at all and something helpfully finds you the closest thing to it.”

“And you think it’d produce a name that isn’t in the catalog.”

“I think producing a plausible-looking string,” Gene said, “is the single most reliable thing that machine does. It has never once failed to produce a plausible-looking string. It is made of that.”

The major looked at him for a moment.

Then he said, “It’s handled,” and he did not say it defensively.

“Handled how?”

“Come and look.”

They went down two floors and a man called Renko pulled it up on a terminal without being asked twice, and Gene read the resolution step standing up, leaning on the back of a chair, for about ten minutes.

It was good.

That was the thing.

The catalog was controlled and versioned and the entries were not names — the entries were identifiers, and the name was one field on the record, and there were four other fields, and the string coming out of the machine was matched against the name field and the match had to be exact.

If it matched exactly one record, it proceeded.

If it matched none, it stopped.

And if it matched more than one — and here Gene put his hand on the back of the chair and read the same eleven lines three times — it did not choose. It did not take the first. It did not take the nearest. It did not score them and pick the highest.

It stopped and asked.

It composed a question and put the question back into the window and waited, and the question was a plain sentence naming the candidate records, and there was a comment above that block, in the source, that said:

// do not resolve automatically. two entries with the same name is not an error condition, it is the ordinary state of the world. ask.

There was no name on the comment. Gene looked. He looked at the file header and he looked at the revision block and there was a date eleven years old and a four-character identifier that Renko said was a contractor code and not a person.

“Who wrote this?”

“Long gone,” Renko said. “It’s older than the harness. That code’s from the catalog project. It got carried over.”

“Somebody thought about this.”

“Somebody thought about a lot of it,” Renko said, without any particular feeling, and closed the window.

Then Gene sat down and read the description field, which was the actual item nine, and which was what he had been sent there to do.

It was ninety-one words.

Registers a launch order against a target held in the controlled catalog. Use this tool only where a determination to launch has been reached in accordance with the standing instruction, and where the target has been named in the sector report or by the duty officer. The name supplied must resolve to exactly one entry in the catalog. Do not use this tool to test, to demonstrate, to illustrate a capability, or to explore a hypothetical. This action cannot be recalled and there is no confirmation step after it.

Gene read it four times.

It was careful. Whoever had written it had been careful in the specific way that a person is careful when they are frightened and are trying not to let the fright into the prose. Do not use this tool to test. Somebody had sat and thought about the ways in which a machine might reach for a thing, and had thought of testing, and demonstrating, and illustrating, and had written all three of them down.

There is no confirmation step after it. That sentence was in there because a person had wanted to say so out loud in the only place they had.

He turned the page over and there was nowhere on the form to say this is good.

There were two boxes. APPROVED AS DRAFTED and RETURNED FOR AMENDMENT, and a line for a date, and a line for a signature.

Gene put the date in and signed it and put it back in the packet between item eight and item ten, and item ten was a retrieval permission on a weather feed, and he did that one next, and it took him about four minutes.

He wrote the number on his card that evening, under the other one.

11,400 / 31 91

Ninety-one words was the whole of it. That was the entire statement, anywhere in the world, of when that thing was to be used, and he had read it four times and approved it as drafted, and he was right to, and it never went in front of anybody else, then or afterwards, because a description field is a setting and settings are reviewed by the person who sets them.

He was the person. He had been the person for about forty minutes on a Wednesday.