Fable
That string of code signs at the door that no one reads yet everyone is affected by
The public archive had a question-answering machine that could look up materials based on visitor requests. The more the librarian wrote, the longer the prompts became, and sometimes the machine still did not answer in the archive's format.
The curator thought the prompt was not detailed enough, so he wrote politeness, steps, format, and prohibitions into the opening remarks. The opening remarks took up too much space, and the visitor's real question no longer fit.
Someone wanted to retrain the entire question-answering machine. The budget was too high, and different departments each only wanted to make a small style adjustment.
An engineer made several cipher plaques and hung them in front of visitor questions. The plaques did not contain sentences humans could read, but soft markers that machines could recognize after training.
These cipher tokens are trained from examples. They don't change the machine's internal structure; they only provide a set of learnable prompt signals at the beginning of the input.
At first there were too few cipher plates to control the format; too many, and they ate into the space for materials. Engineers experimented repeatedly to find the right length for that department.
The archive prepares different code badges for different departments: legal needs caution, sales needs concision, customer service needs clarification first. The machine itself remains the same.
Later, someone mixed natural language prompts with cipher plates and modified them together, making problems hard to reproduce. The curator required every plate to have a version, training examples, and evaluation records. He finally said: prompts can also be trained, but the trained prompts may not look like human language, yet they can become a low-cost behavior control interface. Later, an even trickier job arrived. On the surface it looked like just an amplified old problem, but in reality it forced out all the gaps hidden in the process: who takes over first, who can make changes, how to return to the previous step when something goes wrong—places that used to be glossed over by acquaintances' tacit understanding now all had to be made clear. The person in charge did not urge everyone to be more careful, but walked the site again. He had people record every handover, every failure, and every remediation, which places were merely slow, which places would harm results, and which places would be hard to trace back once wrong. After the new rules were rolled out, the first few days were not smooth. Some complained about an extra check, some felt their old experience was being offended. But when the next anomaly appeared, everyone could for the first time follow the traces to find where the problem occurred, instead of gathering around the result and guessing at each other.