Fable
The clerk finally no longer had to carry the whole cabinet of contracts into the hall
The Cloud Bridge Post House often answered contract questions for clients. In the early years there were few contracts, and the scribe would lay several documents on the table, reading and replying as he went, which was barely enough.
Later, the client uploaded hundreds of manuals, quotations, and agreements. If the clerk brought the entire cabinet of materials into the hall, the table could not hold it; if he answered only from memory, he often missed the fine details.
The curator first asked the client to mark the key pages. The client had no idea which page the problem would fall on—marking too few missed evidence, marking too many returned to the mountain of paper.
He also had the clerk do full-text keyword searches every time. With synonyms, table descriptions and cross-page context, keywords often failed to find the truly relevant passages.
The new archivist first organizes documents into the repository, cuts them into searchable chunks, and builds an index. When a client asks a question, the system first retrieves the relevant content, then hands it to the writer to organize the answer.
The clerk's task shifted from memorizing documents to citing evidence. He had to explain which passages the answer came from, which documents were not covered, and which questions needed further investigation.
The archivist also set up an update process. New files must be re-indexed after upload, expired files must be taken down, and files from different clients must never be mixed together.
A few weeks later, the post office answered document questions much faster. The clerks no longer had to pretend to remember every document, and they no longer stuffed irrelevant files into the context. The curator understood that the value of document search is not making the machine magically read the entire cabinet, but delivering relevant evidence to the machine at the right moment. Later, an even trickier job arrived. On the surface it was just an old problem magnified, but in reality it forced out every gap 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 get by on familiarity and tacit understanding now had to be spelled out clearly. The person in charge did not urge everyone to be more careful; instead, he walked the site again. He had people record every handoff, every failure, and every recovery—which parts were merely slow, which parts could harm the result, and which parts, once wrong, would be hard to trace back. 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 disrespected. But when the next anomaly appeared, for the first time everyone could follow the traces to find where the problem occurred, instead of gathering around the result and guessing at each other.