Chapter 145

The words remained in Mara Venn's mind long after they left the archive.

Confirmation assumed from existing arrangement.

Someone had entered those words beside a closure stamp, but the register did not identify who had made the assumption or what evidence had supported it.

By the time Mara and the traveler reached the public reading room, she had written the phrase three times in her notebook.

The traveler watched her underline it.

“Do you think that sentence explains everything?”

“No,” Mara replied. “It explains why we need another record. It does not explain who made the assumption, whether it was permitted, or whether the missing confirmation existed somewhere else.”

“Then what are we looking for?”

“The traceability register. We need to establish whether anyone ever accepted responsibility for preserving the unresolved-attribution safeguard after TC-04 closed.”

Mara opened the folder containing their certified copies.

The documents now formed a clear sequence. A correction request had been submitted. The original supporting material became unavailable. Temporary continuation was authorized, allowing administrative work to proceed while the missing material was located. The revised account circulated without the disputed-attribution notice. Later, the continuation closed, but the required safeguard transfer remained unverified.

The correction review itself had subsequently been closed pending further disclosure.

Each action had a record.

What remained missing was proof that the responsibility for the unresolved matter had passed properly from one office to another.

Mara drafted a request to the Records Coordination Unit, asking for the complete traceability register, the history of entry 6B, and any documents used to confirm receipt of the outstanding safeguard.

She added a separate request for the identity of the office that had entered the phrase confirmation assumed from existing arrangement, while making clear that they were not seeking the protected identity of the person who submitted the correction.

The requests were sent before midday.

An answer arrived that afternoon.

Records Coordination had approved access to the register but warned that the relevant entry had been amended more than once. The office would provide the original entry, its amendment history, and the final status record.

Mara read the response to the traveler.

“At least they are providing the history,” she said.

“Does that mean the original entry still exists?”

“It should, if their response is accurate. We will confirm that when we inspect it.”

They returned to the archive the next morning.

This time, the archivist brought a ledger, a set of loose continuation sheets, and a printed history generated from the records system.

He placed them on the table in that order.

“The ledger is the original register,” he explained. “The continuation sheets were added when the original pages lacked sufficient space. The printed history records later amendments. None should be treated as a complete account without comparison to the others.”

Mara thanked him and opened the ledger.

Entry 6B occupied half a page.

Matter: Temporary continuation TC-04.

Outstanding requirement: Transfer unresolved-attribution safeguard to responsible office.

Receiving office: Records Coordination Unit.

Confirmation: Pending.

The entry was dated one day after the continuation closed.

The traveler pointed to the receiving-office field.

“So Records Coordination was named.”

“Yes,” Mara said. “That answers one question. But it does not prove the unit accepted the safeguard or understood what it was required to preserve.”

The next line read:

Interim processing permitted pending confirmation.

Below it was the same handwritten note they had found in the earlier extract.

Confirmation assumed from existing arrangement.

The handwriting differed from the original entry, but the ledger did not identify the writer.

Mara examined the amendment history.

Two days after the note was entered, the confirmation field had changed from Pending to Completed.

No supporting document number accompanied the change.

The next amendment, entered later that week, stated:

Traceability requirement satisfied under current reference arrangement.

Again, no supporting document was listed.

The traveler leaned back.

“The status changed twice, but there's no confirmation attached.”

“Correct,” Mara said. “That is a significant gap. But we need to see whether the amendment history identifies a valid source outside this ledger.”

The printed system history provided more detail.

The first change had been made through a shared Records Coordination account. The operator field was blank. The transaction reason stated: Administrative status update.

The second change had been entered by a separate records-maintenance function. Its reason field contained the phrase Reference arrangement established.

Neither transaction included a document reference.

Mara turned to the archivist.

“Does the system require a supporting reference when a pending confirmation is marked completed?”

“For this category, yes,” he replied. “Unless a recognized exception applies.”

“Is there a recognized exception here?”

“Not in the history provided. There may be a separate authorization, but the transaction itself does not identify one.”

The traveler looked at Mara.

“Then the system accepted a completed status without showing what confirmed it.”

“That is what the available history shows. It does not establish whether a supporting document existed elsewhere, but the required reference is absent from these entries.”

Mara asked for the amendment rules in force at the time.

The archivist retrieved a procedural manual from a nearby shelf.

The relevant section explained that traceability entries could be updated only after one of three events:

The receiving office acknowledged the specific outstanding requirement.

A verified transfer record demonstrated that the requirement had been assigned to the receiving office.

An authorized reviewer approved an alternative method of preserving traceability.

A general acknowledgment of a file transfer was insufficient.

Mara read the rule aloud.

“The receiving office had acknowledged the transfer references but explicitly said the contents were not verified. That acknowledgment could not, by itself, satisfy the first condition.”

“And the transfer checklist had no destination for the safeguard,” the traveler added.

“Exactly.”

The second condition also appeared unmet in the documents they had seen. The checklist named no destination, and the receiving-office acknowledgment did not confirm receipt of the safeguard itself.

That left the possibility of an alternative authorization.

Mara requested a search of the authorization register using the transaction dates and both reference codes.

The archivist worked through the index while they waited.

When he returned, he carried a single-page extract.

“One authorization is linked to the relevant period,” he said. “It is listed under a general reference rather than TC-04.”

Mara took the page.

The authorization was titled REFERENCE ARRANGEMENT—ADMINISTRATIVE CONTINUITY.

Its purpose was to allow records offices to use an established reference arrangement when routine transfer documentation had not yet been reconciled. It permitted administrative processing to continue while a missing reference was investigated.

However, the final paragraph stated:

This authorization does not constitute confirmation that any specific document, notice, correction request, or unresolved-status safeguard has been received. Individual receipt must be recorded where required by the applicable procedure.

The traveler read the sentence twice.

“This authorization allowed them to continue working, but it did not allow them to mark the safeguard as received.”

“Correct,” Mara said.

The authorization had been issued by a central administrative office and distributed to several departments. Records Coordination was among the recipients.

But the document did not mention TC-04, the correction request, or entry 6B.

It established that a general arrangement existed. It did not establish that the safeguard had been transferred.

Mara compared the authorization date with the amendment history.

The general authorization had been issued before the traceability entry was changed to Completed.

“That could explain the phrase ‘reference arrangement established,’” the traveler said.

“It could explain why someone thought the arrangement was sufficient for continued processing,” Mara replied. “But the authorization explicitly says it is not confirmation of receipt. It cannot support that conclusion.”

“Then whoever changed the status misunderstood the rule.”

“Possibly. Or the amendment may have relied on another record we haven't found. We cannot determine which from this evidence alone.”

Mara requested the transaction's source reference from the system administrator.

The archivist explained that older transactions sometimes retained a separate audit trail, particularly where a status change had been entered through a shared account.

He submitted the request.

While they waited, Mara turned to the loose continuation sheets.

One sheet had been filed behind entry 6B but was not mentioned in the printed history. Its heading read:

FOLLOW-UP REQUIRED: OUTSTANDING SAFEGUARD.

The date was three days after the first status amendment.

The text was short:

The transfer acknowledgment does not confirm receipt of the unresolved-attribution safeguard. Please identify the responsible office and provide evidence of acceptance before traceability entry is finalized.

The request had been sent to Records Coordination.

A receiving stamp showed that it arrived the same day.

There was no response attached.

The traveler stared at the page.

“Someone recognized that the confirmation was missing.”

“Yes,” Mara said. “And someone requested evidence of acceptance after the status had already been changed to completed.”

“Was the entry reopened?”

Mara checked the amendment history.

No reopening had been recorded.

The follow-up request was indexed under correspondence, not under the traceability entry. Its status was listed as Awaiting response, then later changed to Closed under current reference arrangement.

No reply from Records Coordination was included.

The traveler shook their head.

“So they asked for proof, received no recorded answer, and closed the request anyway.”

“That is the sequence recorded here. We still need the correspondence-completion history to determine how the request was closed and what basis was entered.”

“Could it be another shared-account transaction?”

“It could. We should not assume it, but we should check.”

The archivist returned with the system administrator's response.

The original transaction history was available, but one field required a separate authorization because it contained internal operator information. The office had approved release of the role code and transaction rationale, but not the individual name unless a formal review established that identification was necessary.

Mara accepted the limitation.

They did not need the operator's identity to establish whether the required procedure had been followed.

The audit extract showed that the first change from Pending to Completed had been entered under a shared account. The reason field was blank. The later amendment had been entered under a records-maintenance role whose authority permitted correction of indexing errors but did not permit a substantive determination that an outstanding requirement had been fulfilled.

The follow-up request had been closed through a routine correspondence process. Its closure basis was Reference arrangement in effect. No response document was linked.

Mara set the papers down.

“The record does not show that the safeguard was received. It shows that someone asked for proof, that no response was linked, and that the follow-up was closed by reference to the general arrangement.”

“Which specifically said it wasn't proof of receipt,” the traveler said.

“Yes.”

For several seconds, neither spoke.

They had found no document proving deliberate interference. They had not identified the person who submitted the correction request, the person who made the original decision, or the individual who removed the unresolved notice from the revised account.

But they had established something more precise than suspicion.

The system's own rules required specific confirmation. The general authorization did not supply it. The traceability entry had nevertheless been marked complete. A later request for proof had received no recorded answer, and that request had also been closed by reference to the same general arrangement.

The unresolved status had not been formally settled.

Yet the records had progressively lost the information needed to show where responsibility for preserving it belonged.

Mara gathered the certified extracts.

“We need to ask Records Coordination to identify the document that supported the completion status,” she said. “If no such document exists, we need a formal explanation of the amendment and the closure of the follow-up request.”

“And we should ask whether the status can be corrected.”

“Yes. The register should not continue to state that receipt was confirmed unless the required evidence exists.”

She drafted the request carefully. It did not accuse the unit of misconduct. It identified the missing document reference, the uncompleted follow-up, and the procedural distinction between continued administrative processing and confirmation that a specific safeguard had been received.

Before leaving, the traveler looked once more at entry 6B.

The original field still read Confirmation pending.

The later amendment said Completed.

Between them lay a blank reason field and no supporting document reference.

“Which entry is the truth?” the traveler asked.

Mara closed the ledger.

“The first tells us what was known when the record was created. The second tells us what someone later decided the status should be. Without the required supporting evidence, we cannot treat the later entry as proof that the missing confirmation occurred.”

They stepped into the corridor, carrying the certified pages.

At the end of the hall, the archivist called after them.

“One more thing. The follow-up request has a linked reference that wasn't included in the extract.”

Mara returned to the desk.

The archivist pointed to a small number written in the margin.

It referred to a document in the Exception Review Collection, dated the day after the follow-up request was closed.

The title was brief:

NOTICE OF UNVERIFIED STATUS—RETURNED WITHOUT ACTION.

The traveler felt the investigation shift once more.

Someone had not merely failed to record confirmation.

A notice explicitly identifying the status as unverified had been created, routed, and returned without action.

Mara copied the reference number.

“We need the notice itself,” she said.

The archivist wrote the retrieval request into the register.

As they left, the traveler glanced back at the closed ledger.

For weeks, the investigation had been asking why the disputed-attribution notice disappeared from the account.

Now a different question stood before them.

When a document warned that the safeguard had never been verified, who had decided it required no action—and on what authority?