CHAPTER 90 — The Firewall Made of Delay

The accountability firewall contained no wall. It used three boxes and a bored clerk.

The first box held Elias's proposed correction. The second held the historical reader record. The third remained empty until twenty-four hours later. No responsive system connected them, and no archive event passed directly from Elias to the fifth access trace.

The clerk, Yara Venn, carried physical summaries between rooms after random delays chosen by drawing numbered stones from a cloth bag. She had volunteered because Records needed someone with clearance who had never worked on ASH–31, succession planning, or route development. Elias watched her put one hand into the bag.

Yara drew a stone. "Seventeen hours."

"You sound disappointed," Elias said.

"I was hoping for two," Yara replied.

Senka sat across from Elias with the chained pen secured inside its physical guide. Mira remained in recovery, and accountability work still required a second supervisor, so Yara had signed a statement that she neither liked nor trusted Elias's old novel enough to care how flattering the corrections made him look. The first item concerned Chapter Fourteen.

A reader had accused Elias of introducing a wounded guard and forgetting him two pages later. Elias had replied that the guard died off-page. No death appeared in any surviving draft. No later mention existed.

The development record contained three abandoned possibilities: the guard died, the guard escaped, or the guard remained beneath the bridge. Elias had chosen none of them. His public reply had invented certainty after a reader noticed the absence. The proposed correction read:

I CLAIMED THE GUARD DIED, BUT I HAD NOT DECIDED WHAT HAPPENED TO HIM.

Elias examined the sentence against the surviving drafts. "Accurate."

Senka tapped the development record. "Do you want to add that the character may have been development-only?"

"No," Elias said.

"Why?"

"It sounds like I'm lowering the importance of what I forgot," Elias replied.

Senka nodded once. "Then leave it out."

Elias wrote the correction. The chained pen never left the guide, and when he finished, Yara removed the paper with wooden tongs and placed it into Box One. The page did not touch the historical account.

Yara sealed the box, carried it into a locked room, and left Elias with no route connection to what happened next. The fifth access trace remained at Chapter Ten.

Seventeen hours later, a different clerk opened Box One. That clerk did not carry the original correction into the account room. Instead, they copied only the factual delta onto a clean strip.

AUTHOR NOW ACKNOWLEDGES PRIOR OUTCOME WAS UNDECIDED.

No guard. No chapter number. No reader name. No exact wording.

The strip entered Box Two beside the historical account record. The correction was accepted. The fifth trace moved immediately.

AUTHORIAL DIFFERENCE INCREASED.

CURRENT COMPARISON POINT:

CHAPTER FOURTEEN.

Achebe stood beside the black strip when the movement occurred. Maud Reller checked the mechanical access log while Senka brought Elias in only after the event had already been recorded. The firewall had removed content. It had not removed the event.

Achebe looked at the two boxes through the observation window. "It receives accepted author-state change."

"Not the words," Maud said.

"Possibly," Achebe replied.

Elias shifted his right leg until the higher splint rods stopped pressing behind his knee. "Can it reconstruct the words from the public record?"

"The old reply is already in the archive," Senka said. "It may need only the fact that you changed position."

Ilan stood near the comparison log. "It does not need to read the correction if it watches which version of you survives review."

Elias looked at them. "What does that mean?"

"The historical account claimed certainty. Current you accepted uncertainty. The trace records movement between them," Ilan said.

"A successor profile could learn which corrections I make," Elias said.

"Yes," Ilan replied.

"Then the firewall failed."

Achebe looked at the sealed boxes. "It prevented exact content transfer."

"It still trained the state," Elias said.

"Possibly," Achebe replied.

Elias exhaled through his nose. "Say the word again."

"It remains the accurate one."

Box Three existed for the second test. Instead of accepting another correction, Elias would prepare one and then withdraw it before account entry. If the fifth trace reacted to drafting alone, the delay system would have accomplished almost nothing. If it reacted only after acceptance, the firewall would at least show where information escaped.

The reader complaint involved Chapter Sixteen. A character disappeared from a siege tower and reappeared in the courtyard, and Elias's old reply blamed a formatting error. The unpublished draft contained a missing paragraph in which the character climbed down a rope. This time, Elias's public answer had been mostly right. Records had still proposed a correction broader than the evidence supported.

THE READER WAS RIGHT AND I DISMISSED THEM.

Elias pushed the strip back. "No."

Senka looked at him. "You did blame formatting without checking."

"Yes," Elias said. "That is not the same as the reader being completely right."

"What would you write?" Senka asked.

He drafted a narrower version.

THE PUBLISHED CHAPTER OMITTED THE TRANSITION. I SHOULD HAVE CHECKED BEFORE BLAMING FORMATTING.

Elias placed it into Box One. Yara drew from the bag again.

"Twenty-two hours," Yara said.

"Still disappointed?" Elias asked.

"I have a dinner break in three."

Before the delay ended, Senka found an earlier site cache containing the missing paragraph. The public chapter had once included the rope descent. The omission occurred only during a later migration between archive formats. Elias's old reply about formatting had been correct for reasons he had never verified.

His drafted correction was still partly true. He should have checked before dismissing the complaint. The reader had encountered a real problem. The original continuity itself had not failed.

Elias withdrew the correction. The strip never entered the historical account. Yara placed the abandoned version into Box Three and marked it WITHDRAWN BEFORE ACCOUNT ACCEPTANCE. No archive registration followed.

Twenty-four hours later, Maud checked the fifth trace. Still Chapter Fourteen.

"That supports event monitoring," she said.

Achebe read the experiment list. "Three accepted changes, one refusal, one withdrawal. Useful. Not final."

Tobias joined through a mechanical line from secured housing. "Try a false acceptance."

Senka looked toward the speaker. "No."

"To see whether it follows the event or truth."

"No."

"You are becoming repetitive."

"We are not feeding false history into a live succession dispute."

The answer ended the proposal. The firewall would not become an excuse to manipulate reader records, candidate behaviour, or historical accountability merely because false data might produce a cleaner experiment.

Elias looked at Box Three. "What happens to withdrawn corrections?"

"Destroyed after review," Yara said.

"Can I keep this one?" Elias asked.

"Why?"

"It records a mistake I almost made."

Senka watched him. "That sounds like preservation."

"Yes," Elias said.

"Useful?"

"Maybe."

"Dangerous?" Senka asked.

"Maybe," Elias said.

Elias looked at the cardboard box. The Preserving Function kept deferred decisions because they might matter later. The guard beneath the bridge existed in three abandoned possibilities because Elias had once refused to choose. A correction he nearly accepted could become another branch someone else treated as evidence of who he should be.

"Destroy it."

Yara fed the strip into a physical shredder. The exact sentence vanished. The review log retained only a smaller record:

CORRECTION WITHDRAWN AFTER NEW EVIDENCE.

The fifth trace remained still. Enough accountability to show the process. Not enough exact wording to feed another authorial profile.

The firewall procedure was revised before the next correction entered review. Future items would use delayed physical transfer, strip names and chapter numbers from comparison-facing systems, preserve only the minimum state change required for registration, permit withdrawal before account acceptance, separate accountability records from succession access, and alert Elias whenever any trace reacted. The trust objected.

SUCCESSOR REVIEW REQUIRES COMPLETE AUTHORIAL DIFFERENCE DATA.

Achebe rejected the demand through the physical response channel. "Registration does not exist to train your candidate."

The trust replied:

INCOMPLETE DATA MAY PRODUCE UNSAFE SUCCESSION.

Elias read the sentence from his chair. "Then do not produce one."

No response followed. The fifth trace changed its heading.

PROFILE CONFIDENCE:

DECLINING.

Yara leaned toward the black strip. "That seems good."

"Do not compliment the firewall yet," Maud said.

The detail-starved profile appeared to be losing confidence. For several seconds, that looked like the outcome the three boxes had been built to create. Then a second field appeared.

MISSING DATA SOURCE REQUESTED.

Maud checked the route direction. It did not point toward Elias. The request went toward neutral containment. It pointed toward the Preserving Authorial Function, whose sealed records sat outside the firewall's newly narrowed path.

The Function held abandoned material the firewall had begun denying: deferred options, discarded sentences, preserved revision possibilities, and records accumulated before the new separation rules existed. Achebe terminated the request before delivery. No response left containment. The black strip remained active.

Elias looked from the three boxes to the route map. They had protected the door between his accountability record and the successor profile. The protection worked well enough for the profile to notice what it was missing. The trust had found another archive of his discarded choices.

The three boxes had protected one door. They had also shown the candidate where else to knock.