Chapter 136

The seventh office answered the traveler's request with a package of records that arrived just before the reading room closed for the afternoon.

Mara Venn placed it on the table without opening it.

“Before we begin,” she said, “what exactly are we trying to establish?”

“The identity of the missing attachment, where it went, and who decided its verification wasn't necessary.”

“And if those are three different decisions?”

“Then we'll record them separately.”

Mara gave a small nod. It was the kind of answer she had come to expect from the traveler: careful enough to be frustrating, but difficult to argue with.

They opened the package.

The first document was an attachment inventory from the seventh office. It listed five items received with the individual's request for clarification. Four were accounted for. The fifth was described as SUPPORTING DOCUMENT: PRIOR NOTICE OR CORRESPONDENCE RELATING TO DISPUTED ATTRIBUTION.

The inventory showed that the fifth item had been received and assigned a temporary reference number. It had not been included in the packet sent to the officer responsible for preparing the response.

A routing slip explained why.

Supporting document retained pending confirmation of source and status.

Below that sentence was a handwritten instruction:

No need to delay response. Refer to current determination.

The traveler examined the date. The instruction had been added on the same day the response was prepared.

“Someone separated the attachment from the response file,” Mara said.

“Yes.”

“Then instructed the office to answer without it.”

“The record shows the instruction and the result. It doesn't identify the person who wrote it.”

The handwriting was clear, but the signature field was empty. A small code had been entered in the corner: RC-8.

The traveler wrote the code on a separate sheet.

The next document was a transfer record. It showed that the attachment had been sent to the office responsible for verifying the source of supporting material. The receiving office had acknowledged the transfer, but its acknowledgment contained a qualification:

Receipt of package confirmed. Contents not verified against sending inventory.

Mara read the line twice.

“So even when the package arrived, no one confirmed that the missing item was inside.”

“Correct. We know the sending office recorded a transfer. We don't yet know whether the receiving office actually received the attachment.”

The transfer record carried another reference, this time to the Office of Personal Standing.

The traveler found the related entry in the package's index. It was brief.

Source verification referred to original submission register. Status response requested.

There was no recorded response.

Mara leaned back in her chair.

“Everything leads to an office that doesn't answer.”

“Not everything. Some offices answered. Some answered a different question. Some recorded that a question had been referred elsewhere. Those are not the same thing.”

“And sometimes the difference is enough to leave a person without an answer.”

The traveler looked again at the individual's request. The question had been direct: had the unresolved notice accompanied the account used in the review?

The response had not answered it.

Instead, the office had referred the individual to a determination that relied on the current account. The supporting document that might have clarified the dispute had been separated from the response file. Its transfer was recorded, but its contents were never verified at the receiving end.

The sequence was troubling. It still did not prove that anyone intended to conceal the notice, but it showed how the question could be passed from office to office without being resolved.

The traveler turned to the last page in the package.

It was a small register extract headed RESPONSE COMPLETION—ROUTINE CASES.

The individual's request appeared under a batch of twelve correspondence items. Each had a status code. Eleven were marked completed. The disputed-attribution request was also marked completed, though the attachment remained unverified.

Beside its entry was the same code: RC-8.

Mara pointed at it.

“That's the code on the instruction.”

“It may identify a response category, a routing procedure, or an officer's authority. We need the code register.”

The traveler submitted a request for the public description of RC-8 and any procedural rule governing its use. They also asked for the full routing history of the fifth attachment, including any receiving-office inventory and any decision to classify it as unnecessary.

They expected to wait several days.

Instead, the code register was brought out from the reference shelves less than an hour later.

It was a thin booklet, updated through a series of printed supplements. The entry for RC-8 appeared in the most recent supplement:

RC-8: RESPONSE COMPLETION WHERE SUPPORTING MATERIAL IS NOT REQUIRED FOR THE RESPONSE UNDER AN EXISTING DETERMINATION.

The traveler's eyes paused on the phrase not required.

Mara read it over their shoulder.

“So the code didn't mean the attachment was missing.”

“No. It meant the response could be completed without relying on the attachment.”

“Who was allowed to use it?”

The traveler turned to the following page.

The code could be applied by an authorized correspondence supervisor where the response concerned the procedural status of a matter already covered by an existing determination. The supervisor had to confirm that the response did not make a new finding about the underlying facts.

A note added in a later supplement was more specific:

Where the inquiry challenges the accuracy of the determination itself, RC-8 must not be used as a substitute for referral to the office responsible for reviewing that determination.

Mara looked back at the individual's request.

“They weren't asking only about the procedure. They were asking whether the evidence used in the decision had included the notice.”

“And whether the account had been treated as settled when the attribution remained disputed.”

“Which means the response may have been outside the code's proper use.”

“Possibly. We need the exact authority of the person who applied it and the version of the rule in effect on that date.”

The traveler copied the supplement's publication date and checked it against the response date. The rule had been in force for several months before the individual's request.

There was no question about that.

But there was still a question about the supervisor's authority, and whether the supervisor had understood the request as challenging the determination or merely seeking an explanation of an existing decision.

The traveler's next request went to the correspondence supervisor's public duty register.

The register contained a list of staff authorized to process routine responses during the relevant week. Three names appeared. One was a temporary supervisor covering an absence; another was a permanent correspondence officer; the third was a senior clerk authorized to sign routine completion notices.

None of the names was linked directly to the RC-8 entry.

A separate authorization ledger listed the code under a shared office account rather than an individual's name.

Mara let out a slow breath.

“Shared authority again.”

“Shared access,” the traveler corrected. “We still don't know who used it.”

“Is there a log?”

“There should be a transaction record if the system retained one.”

The ledger referred to an electronic transaction archive, but access to the archive required a case-specific request. The traveler submitted one, including the date, the attachment reference, and the code.

While they waited, Mara returned to the transfer record.

“There is something else,” she said.

She placed the transfer acknowledgment beside the attachment inventory. The inventory described the fifth item as a prior notice or correspondence relating to the disputed attribution. The receiving office had acknowledged the package without verifying its contents. Yet the next routing slip referred to the item as an “unverified historical copy.”

Mara circled the phrase.

“That isn't the same description.”

“No,” the traveler said. “The original inventory left open whether it was a notice or correspondence. The routing slip calls it a historical copy.”

“Someone changed the description before confirming what the document was.”

“Or used a provisional description based on the reference number. We need to find out.”

They traced the reference number through the source-verification register.

The number had first been assigned by the seventh office. It did not originate in the Office of Personal Standing, and it was not a permanent identifier from the original submission register.

That meant the receiving office could not use the number alone to establish the attachment's source.

A handwritten note in the source-verification register read:

Description supplied by referring office. Original document not inspected.

The traveler sat very still.

The item had been separated from the response file because its source and status needed confirmation. It had then been described as a historical copy by a routing entry written by someone who had not inspected it. The receiving office had not verified the package's contents, and no answer from Personal Standing had been recorded.

Yet the response had been marked complete.

Mara's voice lowered.

“The process treated uncertainty as a reason to exclude the document, then treated the response as complete even though the uncertainty remained.”

“That is what the records show.”

“Can we prove the document was the missing notice?”

“Not yet. We can prove the office received an item described as relating to the disputed attribution, that it was separated from the response file, and that its source was never verified in the surviving records.”

The distinction was important. The attachment might have been the notice itself, a copy of correspondence about it, or another supporting document. The records had not established which.

But the change in description mattered. Once it was called a historical copy, it could be handled as background material rather than evidence that needed to be considered before answering the individual's question.

The traveler added a note to the case file:

ATTACHMENT CLASSIFICATION CHANGED BEFORE SOURCE VERIFICATION. BASIS AND AUTHOR NOT ESTABLISHED.

A short message arrived from the transaction archive shortly before the building closed.

The archive could not release the complete transaction history without further review, but it supplied one public extract: the RC-8 completion entry had been created under the shared correspondence account at 16:42 on the day the response was issued.

The field for the individual operator's identifier was blank.

Below it was a system-generated note:

Operator detail unavailable for legacy transactions.

Mara stared at the extract.

“So we have a code, a shared account, and no individual name.”

“And an entry showing when the response was marked complete.”

“Can the archive tell us who was on duty at 16:42?”

“We have the duty register. But being on duty doesn't prove someone performed the transaction.”

The traveler placed the extract with the other records. It narrowed the timeline but did not identify the person responsible.

As they packed the files, Mara returned to the phrase that had troubled her from the beginning.

“Do you think the attachment was deliberately kept out of the response?”

“I think the record shows it was kept out. I don't yet know why.”

“Could it have been an ordinary administrative mistake?”

“Yes.”

“Could it have been a decision to avoid reopening the determination?”

“Yes.”

“And could someone have known the attachment mattered?”

“Yes.”

Mara folded her arms. “Then we still have three explanations.”

“More than three,” the traveler said. “But only one question can move us forward now.”

They wrote it on the cover sheet:

WHO CLASSIFIED THE ATTACHMENT AS A HISTORICAL COPY, AND WHAT EVIDENCE DID THEY USE?

The request would go to the source-verification office first. If its records identified the person who changed the description, the traveler could compare that person's authority with the correspondence procedure. If the office had no such record, the gap itself would become another fact to document.

Mara closed the final folder.

“An unanswered question has now become a completed response,” she said. “A supporting document has become a historical copy without anyone confirming what it is. And the person who asked the question still hasn't received an answer.”

The traveler looked at the seven-office chart. The fifth office had relied on the revised account. The seventh had asked whether the notice accompanied it. Between those two records lay a chain of transfers, classifications, and procedural closures.

The next morning, they would ask the source-verification office for its classification log.

But before leaving, the traveler noticed one final detail in the RC-8 register.

The code's original version had required the correspondence supervisor to record why supporting material was unnecessary.

In the revised version, that requirement remained.

In the individual's case, the reason field was blank.

The response had been completed. The attachment had been reclassified. The question had been redirected.

And the one field meant to explain why no further inquiry was needed contained nothing at all.