The Unmarked Luna

Chapter 25: The Original Log

The original log arrived in a case Adrian was not allowed to open.

At 8:03 on Monday, November twenty-four, the independent system custodian entered the evidence facility carrying a sealed hardware container and a source declaration. Adrian walked behind him with empty hands.

He still wore the signet.

The primary signet system kept its native audit archive in an offline root store. As current officeholder, Adrian could lawfully require a full export. He had signed that request after the nine-evidence index was filed four days earlier, directing the system custodian to deliver the result straight to the independent evidence repository. His office received only a service receipt. It did not receive the export or a controllable copy.

I watched through the intake glass while the custodian photographed the seals, verified the container identifier, and matched the source declaration to the root-store export record.

“Who selected the date range?” I asked.

“The production order,” the system custodian said. “The export includes the full continuity-key history from creation through the preservation cutoff, plus the primary authorization records required to interpret it.”

“Any filters applied by Alpha Kane’s office?”

“None. His office transmitted the order and authorization. The root system generated the export.”

Adrian stood far enough back that his reflection did not touch the case in the glass.

“Do you retain a copy?” I asked him.

“No.”

“Can your office revoke or overwrite this export?”

“No.”

“Can you direct whether I submit it?”

His eyes met mine. “No.”

The intake officer recorded each answer.

Only after the container entered independent custody did the technician mount the read-only image. We checked the native format against the system certificate, counted the record blocks, verified continuity counters, and compared the root signature to the public verification key already held by the custodian. No block was missing from the declared range. No unexplained reset appeared in the sequence.

At 9:26, after receipt—not before—the technician generated the file hash.

`6b29b2cf3da57d82ef23e1de0efacf0053a50de056453c0c183fdc02c0a19c15`

The value went onto the custody form, the technical declaration, and the sealed media label. E-04-P remained in the case as the path that had justified production. The new object received its own designation.

E-04-O.

I compared the new manifest to the red line in the nine-evidence index filed four days earlier. The source field now named the offline root store. The acquisition field carried the 8:03 receipt. The integrity field carried a real hash generated at 9:26. The custodian field named the independent repository. The access field listed protected parties and technical reviewers. The status changed from yellow to green for authentication only.

I refused the clerk’s proposed shorthand, complete evidence.

“Write original authenticated; merits untested,” I said.

The phrase was less satisfying. It was also true.

I began with completeness, not blame.

The native log showed Adrian’s primary credential creating continuity authority for the security committee. It showed the secondary credential activating through a device authorization assigned to the vice-chair office. It showed placement-administration override requests entering under Victor’s administrative certificate and receiving continuity approval through that secondary path.

I asked the technician to reconstruct the sequence without names first.

Primary authorization created the secondary credential. The vice-chair device group activated it. Placement administration submitted an override. The secondary credential approved it. The active list version changed. A transport authorization followed.

The pattern repeated eleven times.

Only after the event order was fixed did we add account mappings. That prevented a familiar name from dictating what we thought the machine had done.

The technician tested for deleted blocks, counter resets, duplicate event numbers, and clock drift. The root archive’s internal counters rose without gaps. Its timestamps matched the server mirror within the documented system offset. The restricted September stay-hearing excerpt and the October allocation records matched corresponding entries in the native log, while remaining separate exhibits.

“Could the export generator omit an event and renumber the rest?” I asked.

“Not without breaking the root signature and counter chain.”

“Could an administrator alter the displayed account label after the event?”

“The label in the interface, possibly. The signed account identifier in this archive, no—not without invalidating the record.”

Those answers fixed the archive's integrity and left intent for the hearing.

The sequence was complete enough to hurt everyone accurately.

Adrian had not personally approved the individual transfers in the log. He had created and failed to audit the authority that made them possible.

Victor’s certificate had initiated the placement overrides. The log did not tell me which person sat at the terminal for every submission.

The secondary credential mapped to Julian’s assigned office account and authorized device group. The signed mapping fixed that technical fact; personal use, delegation, and knowledge still required adversarial testing.

I wrote every limitation beside every conclusion.

Adrian read nothing. He remained outside the protected review area until the custodian called him in to acknowledge that his authorization appeared in an adverse record.

“Do you contest that the primary delegation is yours?” I asked.

“No.”

“Do you contest that you failed to require an independent audit?”

“No.”

“Do you claim that absence of your personal approval on each transfer removes your supervisory responsibility?”

His jaw tightened. “No.”

The three answers were not a final ruling. They were a man declining three exits.

When Adrian stepped back outside the review line, the technician asked whether I wanted the authorization map displayed with names or evidence labels during the party inspection.

“Labels first,” I said. “Names only after the sequence is fixed and only in the protected room.”

Adrian heard me through the glass. He did not object to becoming a label before becoming a husband.

That restraint reached somewhere my anger still guarded. I let it reach without turning it into pardon.

Evelyn reviewed the proposed access and disclosure order that afternoon. She did not rule on the merits of the log. She approved full protected production to the parties for adversarial testing, with security architecture, juvenile identifiers, and protected witness links restricted under the existing orders. The public version would follow the confirmed hearing record on the established forty-eight-hour schedule, subject only to specific protection findings.

Victor objected that exposing the account mappings, even in a protected room, would compromise active administrative systems. Julian objected that the vice-chair assignment proved only office continuity. Adrian filed no objection to the portions that harmed him.

I answered the first two and not the third. The protected review could replace live key strings with stable evidence labels while retaining the signed identifiers in the sealed original. The hearing could test office assignment, device authorization, and actual sequence without publishing a reusable credential. Julian was correct that office assignment alone did not prove his hand; that was why the index separated technical fact from final responsibility.

Evelyn adopted those limits. She refused Victor’s request to withhold the entire mapping and refused my request to place any merits finding in the access order.

“Authentication opens the record to challenge,” she said. “The access order decides no merits.”

No political responsibility could be blacked out merely because the technical path was sensitive.

Julian’s office received notice that an original log had entered custody. It did not receive the protected account mapping outside the authorized review room. Victor received the same notice and access terms.

The hearing would decide what the records meant after challenge.

The records would not vanish before then.

When the work ended, Adrian and I stood in the quiet corridor between the evidence room and the public elevators. His ring caught the late light.

“You knew this could end your office,” I said.

“I knew it should be able to.”

“That is not the same as wanting the result.”

“No.” His voice roughened. “I want to keep the authority. I want to believe I can repair what I failed to see without losing everything attached to it.”

It was the first selfish sentence he had given me in weeks.

I trusted it more than another performance of noble surrender.

“And you still delivered the log.”

“Because wanting the ring cannot decide what the evidence says.”

I looked at his left hand. On September second, that silver had been a threat, a promise, and a clue. Now it was evidence waiting for judgment.

I touched two fingers to the back of his hand, above the ring, and felt him go completely still.

The contact offered neither forgiveness nor permission to return to the case. It was one true thing I chose while the evidence remained intact.

He did not turn his hand over or try to hold mine.

“Not yet,” I said.

“I know.”

I stepped away first.

At 5:42, the independent repository issued the final custody receipt. It listed the source, native format, verified hash, protection level, and hearing schedule.

Under AFFECTED AUTHORIZING OFFICIAL, it named Adrian Kane.

The sealed E-04-O container waited beside the nine-evidence index.

For the first time, every category had something real behind its label.

None of it had been tested in the final hearing yet.

I left the evidence building alone. Adrian did not follow, and I did not ask him to. The restraint between us felt less like distance than a bridge neither of us was entitled to cross quickly. Behind me, the original log remained sealed, complete, and beyond either spouse’s control.

For tonight, that was enough truth to carry.

Back to book

Sign in or create an account

Sign in with Google to keep your library and reading progress on every device.

Continue with Google

By continuing you agree to our Terms and Privacy.