Chapter 148

The compliance findings register was not kept with the ordinary administrative records.

Mara Venn discovered this when her request for access was returned with a note directing her to the Office of Procedural Oversight. The register was public in principle, but its findings were released only through the office responsible for reviewing the original matter.

The note contained no explanation for the restriction.

Mara read it twice before placing it beside the other documents.

“They aren't refusing access,” the traveler observed.

“No. They're directing us to the office that controls the findings. We should follow the procedure rather than assume the restriction is an attempt to prevent scrutiny.”

The traveler glanced at the reference number.

“Do you think the review concerned our case?”

“The index says it concerned active cases processed under the continuity circular. TC-04 may have been included, but we need the actual findings to establish that.”

Mara prepared a formal request identifying the disputed-attribution safeguard, the clarification issued by Central Distribution, and the return of the notice under IR-12.

She asked for three things: confirmation of whether TC-04 had been included in the compliance review, the findings relevant to the handling of unresolved-status safeguards, and any corrective action directed at the offices involved.

She did not request the identity of the person who submitted the correction request. That information was not necessary to establish whether the administrative procedure had been followed.

The Office of Procedural Oversight acknowledged the request the same afternoon.

Access was approved for the following morning.

When Mara and the traveler arrived, a records officer named Ms. Ellery led them to a consultation room. She carried a bound findings register and a folder of supporting schedules.

“The register contains a general compliance review,” Ellery explained. “Some entries concern individual cases, but the findings were organized by procedural issue rather than by the names of the people affected.”

“That should be sufficient for our inquiry,” Mara said. “We're examining how the unresolved-status safeguard was handled.”

Ellery opened the register.

The review had been conducted after several departments adopted the continuity circular. Its purpose was to determine whether offices understood the difference between continuing an administrative arrangement and confirming the accuracy of the underlying determination.

The findings were divided into four sections.

The first covered receipt and distribution of the circular.

The second covered local implementation.

The third examined case-specific records.

The fourth recorded corrective actions.

Mara began with the first section.

The distribution review had found that the circular reached all listed departments, including Office Five, Personal Standing, Records Coordination, and Interim Review.

Receipt was confirmed in the distribution register.

However, the review warned that delivery of a circular did not establish that every officer handling an individual case had applied its limitations correctly.

The traveler nodded.

“That matches what we've been careful about.”

“Yes,” Mara replied. “The review itself recognizes the distinction.”

The second section was more concerning.

Several offices had adopted a shortened implementation notice that emphasized the continuation of existing administrative arrangements but did not repeat all the circular's limitations. The compliance team had warned that the shortened notice could be misunderstood if read without the full circular.

The findings did not say that every office had misunderstood it. They did, however, identify a risk that unresolved-status safeguards might be treated as unnecessary once a current determination remained operative.

Mara turned to the supporting schedule.

The Office of Interim Review was listed among the departments that had received the shortened notice.

The schedule did not establish which staff members had used it, or whether the full circular had also been consulted in the disputed case.

The traveler pointed to the entry.

“So the office had both versions.”

“The distribution records show that it received the full circular and the shortened notice,” Mara said. “That doesn't tell us which version was consulted when the notice was returned.”

“What did the compliance team recommend?”

Mara moved to the corrective-action section.

The recommendation was clear.

All active cases involving disputed personal attribution must retain an explicit unresolved-status statement unless a formal determination has resolved the dispute. Continued administrative processing shall not be treated as a substitute for that statement.

A second instruction required offices to reconcile any case in which a supporting record had been marked received or verified without an identifiable reference.

The traveler looked at the date.

“When was this issued?”

“Before the closure of TC-04,” Mara replied.

She checked the implementation schedule.

The corrective-action notice had been circulated to the relevant departments several days before the traceability entry was changed from Pending to Completed.

Interim Review had acknowledged receipt.

Records Coordination had also acknowledged receipt.

The Office of Personal Standing had received the notice through its official correspondence channel.

Mara placed the dates in chronological order.

The compliance team had identified the danger of treating administrative continuity as resolution. It had required unresolved-status statements to remain visible. It had also directed offices to reconcile unsupported verification entries.

Those instructions were in circulation before the notice of unverified status was returned and before the traceability entry was marked complete.

The traveler stared at the page.

“Then the procedure had already been clarified.”

“Yes. The remaining question is whether the corrective action was applied to TC-04 and what happened when the case-specific records were examined.”

Ms. Ellery turned to the individual-case schedule.

The schedule contained a reference matching TC-04.

The entry read:

Case reference: TC-04.

Issue identified: Unresolved-attribution safeguard not verifiably transferred.

Related record: Notice of unverified status returned under IR-12.

Review status: Included in sample.

Mara's attention sharpened.

“Was the case examined individually?”

“It was included in the sample,” Ellery replied. “The findings register records the result, but the supporting work papers contain the detailed review.”

“May we see them?”

“Your authorization covers the relevant work papers, subject to the same restrictions on unrelated personal information.”

Ellery retrieved a thin bundle.

The first work paper listed the documents examined: the TC-04 authorization, the transfer checklist, the receiving-office acknowledgment, the traceability entry, and the return of the notice.

The reviewer's observations were written in the margin.

Transfer acknowledgment does not verify receipt of the safeguard.

Completion status lacks supporting reference.

IR-12 return basis not recorded.

Clarification response not linked to active transaction.

Mara looked at the traveler.

“These are the same gaps we found.”

The final observation was underlined.

Correction required before case may be marked procedurally reconciled.

The traveler turned to the next page.

“Was it corrected?”

The status field contained one word.

PENDING.

The review date was followed by an entry made two days later.

Case status: Closed in compliance summary.

No explanation accompanied the change.

Mara checked the findings register.

The summary described the overall review as completed and stated that implementation notices had been distributed. It did not say that every individual case had been reconciled.

The TC-04 work paper, however, still showed the correction as pending.

“Why was the case marked closed in the summary?” the traveler asked.

“We need to distinguish the closure of the overall compliance review from the status of this individual correction,” Mara said. “The review could have been completed as a project while an individual case remained unresolved. But the summary should not imply that the individual correction was complete if it was still pending.”

She asked Ellery to locate the closure basis.

A separate administrative sheet showed that the compliance summary had been finalized after the corrective-action notice was distributed. The basis for closure was:

General implementation completed. Outstanding individual matters remain subject to responsible-office reconciliation.

The traveler read the sentence.

“So the overall review was closed while individual matters remained outstanding.”

“Yes. That was permitted by the procedure, provided the outstanding matters remained tracked and were not represented as resolved.”

“Was TC-04 still tracked?”

Mara searched the supporting schedule.

The original work paper showed it as pending. But the final summary's appendix contained no list of the outstanding individual cases. Instead, it referred readers to the relevant departments for follow-up.

There was no case-specific confirmation that TC-04 had been reconciled.

Ellery explained that the compliance office did not maintain the underlying correction requests. It could identify procedural defects and issue recommendations, but the responsible offices had to confirm that their records had been corrected.

Mara thanked her and asked for the register showing whether those confirmations had been received.

The officer checked the cross-reference.

“The confirmation register is maintained by the implementation team. I can request the relevant extract.”

While they waited, the traveler examined the work papers again.

“Could the summary's closure have caused people to think the case was fixed?”

“It could have contributed to that misunderstanding,” Mara said. “But the closure basis explicitly states that outstanding individual matters remained subject to reconciliation. We need evidence showing how the summary was used before we can say what any office understood from it.”

The confirmation extract arrived before noon.

It listed the corrective actions issued to the departments and recorded their responses.

Office Five had confirmed that the corrective-action notice was received.

Personal Standing had confirmed receipt and stated that the existing determination remained operative.

Records Coordination had acknowledged the instruction and said that outstanding matters would be handled under the current reference arrangement.

Interim Review's response was the most relevant.

It stated:

The notice of unverified status was processed under the existing distribution procedure. No further action was required under the current arrangement.

There was no reference to the requirement that the safeguard remain visible.

There was also no statement that the traceability entry had been corrected or that the missing supporting record had been located.

Mara placed the response beside the compliance work paper.

The compliance review had identified the precise defect. It had required correction before TC-04 could be marked procedurally reconciled. Yet the implementation response repeated the earlier explanation without addressing the missing evidence.

The traveler looked at the page.

“Did the compliance team accept that response?”

“We need to see its recorded assessment,” Mara said.

Ellery found the final column in the confirmation register.

Interim Review's response had been marked:

RECEIVED—IMPLEMENTATION NOT VERIFIED.

No subsequent verification entry appeared.

The traveler sat back.

“Then the response was received, but nobody confirmed that the correction had been completed.”

“That's what this register shows.”

“And the case was still marked closed in the compliance summary.”

“The overall review was closed. The individual correction remained unverified. We must keep those statuses separate.”

Mara requested that the Office of Procedural Oversight formally confirm the distinction in its public case extract and preserve the TC-04 work paper as an outstanding procedural matter. She also asked the office to identify which department was responsible for obtaining the missing confirmation.

Ellery accepted the request.

“I cannot promise that the office will reopen the entire compliance review,” she said. “But I can forward the case-specific discrepancy to the implementation team.”

“That is appropriate,” Mara replied. “We are not asking you to determine the disputed attribution. We are asking you to ensure the procedural status is accurately recorded.”

Before the meeting ended, Ellery checked one final cross-reference.

“There is an implementation exception associated with TC-04,” she said. “It was submitted after the compliance review identified the defect.”

Mara looked up.

“An exception to what?”

“To the requirement for immediate reconciliation. The request asked whether the case could remain under the current distribution arrangement while the missing records were located.”

“Was it approved?”

Ellery checked the status.

“An outcome is not recorded in this register. The reference points to a separate authorization file.”

Mara wrote down the number.

The traveler glanced at the date.

The request had been submitted after Interim Review received the compliance corrective-action notice but before the traceability entry was marked complete.

“Then that may explain why they continued processing the case,” the traveler said.

“It may explain why an exception was requested,” Mara replied. “It does not establish that the exception was approved, what it permitted, or whether it could lawfully affect the unresolved-status safeguard.”

They thanked Ellery and left with certified copies of the compliance findings.

Outside, the traveler stopped beside the steps.

“We finally have proof that the problem was identified before the records were marked complete.”

“Yes,” Mara said. “We have proof that the compliance team identified the missing safeguard, required correction, and left the case pending. We also have a later response from Interim Review that did not establish the correction had occurred.”

“And the exception request came after the warning.”

“Correct.”

“Could someone have used the exception to bypass the required correction?”

“That is one possibility. Another is that the exception concerned timing only and was never approved. We need the authorization file before we can distinguish between them.”

Mara placed the new reference at the front of her folder.

The investigation had uncovered more than a missing document. It had uncovered a formal review that identified the failure, issued corrective instructions, and recorded that implementation remained unverified.

The wider review had closed.

The individual case had not been reconciled.

And the response submitted by the office responsible for handling the notice had failed to establish that the required safeguard was in place.

As they walked toward the records building, the traveler asked one final question.

“If the exception was never approved, what authority allowed the case to keep moving?”

Mara tightened her grip on the folder.

“Then the next record must explain the continuation. We have reached the point where a request for an exception is no longer enough. We need the decision that answered it.”

The authorization file was the next step.

And somewhere inside it lay the missing distinction between asking permission to proceed and actually receiving it.