Chapter 146

The title of the document was troubling enough.

NOTICE OF UNVERIFIED STATUS—RETURNED WITHOUT ACTION.

Mara Venn wrote the reference number on the first page of her notebook and circled it. Then she checked it against the traceability register, the correspondence-completion history, and the exception-review index.

All three records pointed to the same notice.

It had been created after a request for proof that the unresolved-attribution safeguard had been transferred. It had been routed to the office responsible for handling the exception. And it had been returned without action.

But none of the three records explained why.

“We have to be careful,” Mara said, closing the notebook. “The title tells us the status was unverified. It doesn't tell us who read the notice or why it was returned.”

The traveler sat opposite her in the reading room.

“Could it have been returned because the information was already recorded somewhere else?”

“Possibly. If so, the return record should identify the alternative record or explain why further action was unnecessary.”

“And if it doesn't?”

“Then we have another procedural gap.”

Mara prepared a request for the original notice, its routing slip, and the return authorization. She also requested the applicable handling rule and any linked correspondence.

The archive acknowledged the request within an hour.

The documents would be available the following morning.

That evening, Mara reviewed the sequence they had already established. The general reference arrangement had allowed processing to continue while records remained outstanding. It had not confirmed receipt of the safeguard. Nevertheless, the traceability register had been marked complete. A follow-up request for supporting evidence had been closed without a recorded response.

Now they had discovered a notice created specifically to identify the unverified status.

If the notice had reached the responsible office, its return might explain why the uncertainty never appeared in the later decision records.

But the route still had to be established.

The next morning, the archivist placed a small brown folder on their table.

“The original notice is here,” he said. “The return authorization is attached. The routing history was stored separately, so I have included that as well.”

Mara thanked him and opened the folder.

The notice consisted of one page.

NOTICE OF UNVERIFIED STATUS

Reference: TC-04 / Entry 6B.

Matter: Unresolved-attribution safeguard.

Finding: No verified record located confirming receipt by the responsible office.

Required action: Identify the office responsible for preserving the safeguard and confirm whether the unresolved status remains visible in records used for consequential decisions.

Restriction: This notice does not determine the accuracy of the disputed attribution and does not authorize closure of the underlying correction request.

The traveler read the final sentence aloud.

“They made it clear that the notice wasn't deciding the dispute.”

“Yes,” Mara said. “It was asking for the missing procedural confirmation. Nothing more.”

The notice was dated one day after the follow-up request had been closed. It referred to the blank confirmation field in entry 6B and the absence of a supporting document number.

At the bottom, a box marked ACTION REQUIRED had been checked.

A separate box marked UNDERLYING MATTER RESOLVED remained empty.

Mara turned the page over.

There was no additional text.

The routing slip was more revealing.

The notice had first been sent to the Records Coordination Unit. A receiving stamp showed that it arrived at 9:18 a.m.

At 10:02 a.m., it was forwarded to the Office of Interim Review with the instruction:

Please confirm whether an authorized alternative record satisfies the outstanding traceability requirement.

The Office of Interim Review returned it that afternoon.

Its reason was typed into the return field:

The existing administrative arrangement remains operative. No further action is required under the current distribution procedure.

The traveler stared at the sentence.

“That's the same answer again.”

“It is similar,” Mara replied. “But this time, the question was whether an authorized alternative record satisfied a specific requirement. The response does not identify any such record.”

“Did Interim Review have the authority to answer that question?”

Mara checked the routing instructions.

“The office could determine whether the relevant procedural requirement had been met, but it could not decide whether the underlying attribution was true. That distinction matters.”

“So it was allowed to check the safeguard.”

“Yes. We need to know whether it actually checked the supporting records before returning the notice.”

The routing slip included a reference to an internal review entry, but the document itself was absent.

Mara copied the number and asked the archivist to retrieve it.

While they waited, she examined the return authorization.

It had been processed under code IR-12.

The procedural index described IR-12 as a routine return code for notices that duplicated an existing instruction, referred to an issue outside the receiving office's jurisdiction, or required no additional action under an established procedure.

Three reasons were listed, but the authorization did not identify which one applied.

The field marked SPECIFIC BASIS FOR RETURN was blank.

The traveler leaned over the form.

“Could IR-12 be used simply because the existing arrangement was still in force?”

“Only if the notice genuinely duplicated an instruction or required no further action under the relevant procedure,” Mara said. “The code does not itself prove that condition was met.”

“Then why was the notice returned?”

“We don't know yet.”

The archivist returned with a second folder.

The internal review entry showed that Interim Review had received the notice at 10:02 a.m. It had been assigned a temporary reference and placed in the queue for procedural verification.

The first status entry read:

DOCUMENT STATUS: UNVERIFIED.

The second read:

ALTERNATIVE RECORD: NOT IDENTIFIED.

A third entry appeared twenty-three minutes later:

RETURN AUTHORIZED UNDER IR-12.

No intervening verification result was recorded.

The traveler looked at the three lines.

“They recorded that no alternative record had been identified, then returned the notice.”

“That's the sequence,” Mara said. “It does not establish whether the reviewer consulted another register or whether a supporting record was held elsewhere. But the review entry itself does not document the required verification.”

The approval field contained a role code, not a name. The code permitted authorized officers to return routine notices, but only where the applicable return condition had been established.

Mara requested the full IR-12 handling rule.

The archivist retrieved the historical procedure.

It required the reviewing officer to record the specific reason for return and identify the reference that supported that reason. If no alternative record could be found, the officer had to return the notice to the originating office with the status marked unresolved.

The traveler read the final instruction twice.

“Then this notice should have gone back marked unresolved.”

“If the review could not identify an alternative record, yes.”

“But it was returned with a statement that no further action was required.”

“That is the discrepancy we must investigate.”

Mara compared the handling rule with the return authorization. The rule required a specific basis and a supporting reference. The authorization contained neither.

There was no attached evidence that the safeguard had been transferred, no record showing that the notice was duplicative, and no explanation that the issue fell outside the office's jurisdiction.

The response referred instead to the existing administrative arrangement.

Mara wrote a note.

IR-12 used. Specific basis blank. Supporting reference absent. Review entry shows alternative record not identified.

The traveler watched her write.

“Can we say the notice was improperly returned?”

“We can say the recorded return does not demonstrate compliance with the stated procedure. A formal finding about the validity of the return requires the office to explain the missing fields and any supporting record it relied on.”

“What if it cannot?”

“Then the record should be corrected to reflect that the status was not verified.”

The archivist cleared his throat.

“There is one more linked document,” he said. “The system index refers to a quality-control review opened after the return. It is not attached to the original notice, but it shares the same reference.”

Mara immediately requested it.

The quality-control review had been opened two days later by the central correspondence unit. Its purpose was to examine whether notices returned under IR-12 contained the required reason and supporting reference.

The entry for TC-04 was brief.

Review item: Notice of unverified status.

Defect observed: Specific return basis not recorded.

Supporting reference: None listed.

Action: Refer to responsible office for clarification.

For a moment, the traveler seemed relieved.

“Someone caught it.”

“Yes,” Mara said. “The quality-control process identified the defect.”

The next line removed some of that relief.

Referral outcome: Closed under existing distribution arrangement.

There was no explanation.

The quality-control reviewer had identified the missing basis and supporting reference. The matter had been referred for clarification. The referral had then been closed using the same general phrase that appeared in the earlier records.

The traveler looked down at the page.

“So the warning was noticed, but the question was never answered.”

“That is what the available record indicates. We still need the referral correspondence to establish whether an explanation was sent and not attached, or whether none was received.”

Mara requested the correspondence history.

It showed that the quality-control referral had been sent to the Office of Interim Review. A receipt was recorded the same day.

Three days later, the referral was marked closed.

No response document number appeared in the closure field.

The closure reason was:

No further action required under current distribution procedure.

Mara placed the quality-control record beside the original notice.

The same phrase had now appeared in several different contexts: the traceability entry, the return authorization, and the quality-control referral.

Yet each process had asked a different question.

The traceability entry required confirmation that the safeguard had been received.

The notice asked which office was responsible for preserving the unresolved status.

The quality-control review asked why the notice had been returned without the required basis and supporting reference.

The repeated response answered none of those questions directly.

“Could all these closures have been generated from one instruction?” the traveler asked.

“They could have relied on the same general arrangement,” Mara said. “But we haven't found an instruction that specifically authorized these individual closures. The authorization we examined explicitly stated that the arrangement did not confirm receipt of any particular safeguard.”

“So the general arrangement became an answer to every question.”

“That's the pattern in the records. We still need to determine how it was applied and by whom.”

Mara requested a formal explanation from the Office of Interim Review. Her letter listed the missing supporting reference, the blank return-basis field, and the quality-control finding. She asked whether any alternative record had been identified, whether the return complied with IR-12, and what document supported the later closure of the quality-control referral.

She also requested correction of the traceability entry if no valid confirmation could be produced.

The request did not accuse the office of deliberately hiding information. It simply required the office to reconcile its actions with the written procedure.

Before leaving, Mara asked the archivist to certify the original notice and all linked entries.

He stamped the copies and entered their reference numbers in the access register.

As he finished, he paused over the quality-control closure.

“There is a note here that was not included in the printed extract,” he said.

Mara leaned closer.

The note had been entered in the margin, beside the closure date.

The notice was returned because the status question had already been addressed by the current arrangement.

The traveler looked at the words.

“Who wrote that?”

The handwriting was not identified. The entry had no author field, and the system history showed only that the note was added during the closure process.

Mara compared the wording with the earlier responses.

It was different, but its meaning was familiar. Rather than identifying an alternative record or explaining why the safeguard had been received, it asserted that the question had already been addressed.

“It's a claim,” Mara said, “not the evidence supporting the claim.”

The traveler looked at the certified copy of the original notice.

The document had clearly stated that the safeguard remained unverified. The reviewing office had recorded that no alternative record was identified. The notice was returned without a specific basis. A quality-control review noticed the missing explanation, but its referral was closed without a response attached.

Nothing in the chain established that the safeguard had ever reached a responsible office.

As they walked out of the archive, the traveler asked, “What happens if Interim Review cannot produce the missing record?”

“Then we ask the records authority to preserve the unresolved status formally and reopen the question of who was responsible for the safeguard.”

“And the correction request?”

“That remains a separate issue. We cannot decide whether the disputed attribution was accurate simply because the procedure was mishandled.”

The traveler nodded.

They had finally found the notice that documented the uncertainty. They had also found the process that returned it without resolving that uncertainty.

What they had not found was the evidence that anyone had corrected the problem.

Mara placed the folder in her bag.

The next response would have to answer a narrow question that had followed them from one office to another:

What specific record allowed Interim Review to say the status question had already been addressed when its own register showed that no alternative record had been identified?

Until that question was answered, the notice remained returned, the safeguard remained unverified, and the disputed attribution remained unresolved.