Chapter 143

The request for the archived decision-support register was approved the following morning.

Mara Venn received the notification while she and the traveler were reviewing the documents from Office Five. The approval came with a restriction: they could inspect the exception-review entry and its supporting references, but any personal information unrelated to the administrative question would remain withheld.

Mara read the restriction twice.

“They're allowing us to examine the procedure,” she said. “They are not allowing us to identify the person behind the correction request.”

“Which is fair,” the traveler replied. “We haven't established that the identity is necessary.”

Mara gave a small nod. “Then we stay focused on the records.”

They arrived at the archive shortly before ten.

The decision-support register was kept in a separate room from the public indexes. Unlike the general collection, which could be consulted by anyone, this register contained internal routing information, document references, and records explaining why certain decisions had proceeded despite missing or incomplete supporting materials.

An archivist named Mr. Halden met them at the entrance.

“You requested exception review ER-2,” he said. “The entry exists, but I want to clarify the limitations before you begin. The register records procedural exceptions. It does not, by itself, establish that an exception was properly authorized.”

“That is understood,” Mara replied.

“And a reference to an exception does not mean the underlying requirement was waived.”

The traveler looked at him. “Then what does it mean?”

“That an issue was identified and referred for handling under the applicable procedure. What happened afterward must be established from the associated records.”

He led them to a table and brought out a thin folder.

Its cover bore the same reference number as the notation on Office Five's decision index.

Inside were six pages.

The first was a registration sheet.

EXCEPTION REVIEW ER-2

Matter: Continued administrative arrangement involving disputed attribution.

Reason for referral: Required status reconciliation not confirmed in the active decision packet.

Action requested: Determine whether the decision may proceed, whether an unresolved-status notice is required, or whether further documentation must be obtained.

The traveler leaned forward.

“They recorded the exact problem.”

“Yes,” Mara said. “The missing reconciliation wasn't merely something we noticed afterward. Someone recorded it as an issue before the action was finalized.”

The registration date was the same day the decision-support checklist had been prepared.

Beneath the entry appeared a routing instruction:

Refer to the office responsible for determining the operative status of the correction request. Decision-support staff must not independently infer resolution from administrative closure.

Mara underlined the last sentence in her notebook.

“This is important,” she said. “It expressly prohibits the assumption we've been investigating.”

The next page showed the referral destination: the Office of Personal Standing.

A receipt stamp confirmed delivery.

For several hours, the entry had remained marked AWAITING STATUS DETERMINATION.

Then the status changed.

RESPONSE RECEIVED. EXISTING DETERMINATION REMAINS OPERATIVE.

There was no explanation attached to the change. The field asking whether the underlying attribution had been determined was blank.

The traveler turned to Mara.

“That's the same answer they sent to Office Five.”

“It appears to be the same wording,” she said. “But we need to establish whether this entry generated that response or merely recorded it afterward.”

A small reference number appeared beside the status change. It pointed to a second register maintained by the Decision Records Unit.

Mara wrote it down.

The third page contained a checklist of conditions for closing an exception review.

Four conditions were printed on the form:

The missing record has been located and reconciled.

The relevant office has confirmed the required status.

The decision has been revised to preserve the unresolved status.

The exception remains open because none of the preceding conditions has been satisfied.

Only one box had been marked.

CONDITION 4: EXCEPTION REMAINS OPEN.

Yet a closure stamp appeared at the bottom of the page.

The traveler stared at it.

“How can it be closed if the form says it remains open?”

Mara examined the stamps carefully.

“One stamp concerns the administrative referral. The other concerns the exception itself. They're dated differently.”

The referral had been closed on the afternoon the response from Personal Standing arrived. The exception-review closure stamp had been entered the next morning.

The distinction mattered. The first closure could mean that the referral had received a response. It did not necessarily mean the problem identified in the referral had been resolved.

The traveler traced the dates with a finger.

“So someone closed the referral because they received an answer, then closed the exception the next day.”

“That is what the entries show.”

“But the checklist still says the exception should remain open.”

“Unless another qualifying action occurred and was recorded elsewhere.”

Mara turned to the fourth page.

It was a continuation sheet, mostly blank except for a handwritten note.

Response received. No amendment to current determination. Proceed under existing arrangement.

Below it was a routing code: RC-8.

The traveler recognized it immediately.

“That's the code used for the response that bypassed the detailed review.”

“It's the same code,” Mara confirmed. “But the presence of the code does not establish that the same person handled both matters. We need the transaction history.”

The archivist returned to the table when Mara requested it.

“Does the register contain the original routing instruction?” she asked.

“Not in this folder. The register points to the correspondence-completion system.”

“Can we inspect the linked entry?”

“Your authorization includes it, provided we remain within the scope of the exception review.”

He left and returned with a printed transaction extract.

The extract showed that the status response had been entered under a shared correspondence account. The operator field was blank. The transaction description read:

Response completed by reference to existing determination.

The reason field contained no text.

A separate system note explained that RC-8 was permitted when a response could be completed by reference to an established determination without further supporting material.

However, where the inquiry challenged the accuracy or status of that determination, the matter had to be referred to the reviewing office.

The traveler's expression hardened.

“The question from Office Five was whether the missing notice meant the dispute had been resolved. That challenges the status of the determination.”

“It certainly raises the question,” Mara said. “But we still need the underlying inquiry and the review office's record to establish whether the routing rule was triggered and how the office handled it.”

The transaction extract included one more line.

REVIEWING OFFICE REFERENCE: PENDING CONFIRMATION.

There was no subsequent confirmation in the extract.

Mara placed the page beside the exception checklist.

“We now have two separate gaps. The exception was closed despite a checklist indicating that the underlying issue remained unresolved. And the response transaction was completed without a recorded reason, while the reviewing-office reference remained pending.”

“Could the shared account explain both?”

“No. It explains why we cannot identify an individual operator from this transaction. It does not explain why the required fields were left incomplete.”

The archivist returned to his desk, leaving them to continue.

Mara examined the fifth page, which contained the exception's closure history.

The original entry had been created at 9:12 a.m.

The referral to Personal Standing had been received at 10:06 a.m.

The status response had been recorded at 2:38 p.m.

At 9:04 a.m. the following morning, the exception was closed.

The closure basis read:

Current arrangement remains operative. Further administrative action not required.

The approval field contained a role code, DS-3, but no name.

A note beneath it stated that DS-3 authorized closure of routine decision-support exceptions once a response had been received. It did not authorize the officer to determine whether a disputed personal attribution was accurate.

The traveler looked from the role code to the checklist.

“Then the person who closed it may have had authority to close the administrative exception, but not to decide the truth of the disputed account.”

“Correct,” Mara said. “Those are separate questions. We should not accuse someone of exceeding authority merely because the closure appears questionable. We need to know precisely what the officer was asked to decide and what the closure represented.”

“Could the closure still have been valid?”

“The administrative referral might have been validly closed after receiving a response. The exception closure is harder to reconcile with the checklist, but we need the governing rule and any additional authorization before reaching a conclusion.”

The sixth page provided a new lead.

It was a cross-reference to a document titled EXCEPTION HANDLING GUIDANCE—TEMPORARY CONTINUATION.

The document had been issued several months before the disputed decision. The index described it as guidance for cases in which administrative action needed to continue while supporting records were being located.

Mara requested the guidance from the archivist.

He checked the register.

“The document is available in the public procedural collection,” he said. “I can bring you the current version and the historical version that was in force when Office Five acted.”

“Both, please.”

When he returned, Mara opened the historical version first.

The guidance permitted temporary continuation where delay would disrupt an existing arrangement. But the permission came with conditions.

The missing record had to remain identified as outstanding.

Any disputed attribution had to remain visibly unresolved.

The responsible office had to be named.

And the temporary arrangement had to be reviewed when the missing record was located or when the prescribed review period expired.

Mara read the last paragraph aloud.

“‘Temporary continuation shall not be interpreted as confirmation of the underlying attribution, and closure of an administrative referral shall not extinguish an outstanding review requirement.’”

The traveler exhaled slowly.

“That is exactly what the closure summary failed to preserve.”

“It supports the concern,” Mara said. “But we still need to establish which version of this guidance was available to the officers handling the case and whether any valid supplementary instruction applied.”

She compared the historical version with the current one.

The relevant clauses were unchanged.

On the inside cover of the historical copy, an issue register listed the departments that had received the guidance. Office Five was included. So were Personal Standing, Interim Review, and the Central Distribution Office.

The distribution date preceded the disputed decision by several months.

There could be little doubt that the guidance had been formally circulated to Office Five. What remained uncertain was whether the individual responsible for the decision had consulted it or whether the office's internal process had correctly applied it.

Mara returned to the exception register.

A final reference appeared beneath the closure history:

SUPPLEMENTARY AUTHORITY, IF ANY: SEE TEMPORARY CONTINUATION REGISTER.

The reference had been added in different handwriting from the original entry.

The traveler looked at the note.

“Someone knew there might be another authorization.”

“Or knew the procedure required us to check whether one existed,” Mara replied.

“Can we find out?”

“Yes. The temporary continuation register should show whether an additional authorization was issued, who was responsible for it, and what limits it carried.”

She copied the reference number onto a fresh inquiry sheet.

Before they left, Mara asked the archivist to certify the pages they had inspected. He checked each page against the register, stamped the copies, and recorded the date of access.

Outside the archive room, the traveler stopped beside the corridor window.

“We have a rule that says the dispute must remain unresolved, a checklist that says the exception should remain open, and a closure entry saying no further action was required.”

“We do,” Mara said.

“And we have no name attached to the closure.”

“We have a role code, not an identified officer. That is a limitation, not proof of concealment.”

The traveler looked back toward the records room.

“Every time we find the rule, we find a record showing that the rule wasn't visibly completed.”

“Then we continue examining the records,” Mara said. “We do not fill the gaps with assumptions simply because the pattern is troubling.”

She placed the certified copies in her folder.

The next register might reveal that a valid temporary authorization had been issued. It might show that someone had tried to preserve the unresolved status but failed to carry the instruction into the active file. Or it might reveal that the exception had been closed without the required authority.

For now, all three possibilities remained open.

As they reached the exit, the traveler noticed that the final page of the certified extract carried a small notation not visible in the public index.

TEMPORARY CONTINUATION REGISTER—ENTRY TC-04.

Beneath it was a date.

It was the same date the original submission had been marked outstanding.

Mara read the notation and closed the folder.

“Now,” she said, “we find out whether the continuation was authorized to protect the decision—or to protect the unresolved record while the decision continued.”

And for the first time, the investigation had a direct path to the authority behind the exception.