Log InRegister
    Read Free Web Novels Online

    The security log had one hundred fourteen seconds left.

    At zero, the vault controller would compact its live transaction record into retained classifications and authenticated counts. The original requests would remain in reduced form. Their timing relationships, route fragments, and controller state would not.

    Mara kept both hands clear of the vault panel.

    Behind the blue seal, one line identified the only official evidence copy recovered from the courier:

    COPY ONE OF ONE

    The wafer remained unmounted under her sole credential. Nothing in the procedure she had proposed required opening it. The expiring evidence belonged to the vault controller, not to the source media behind the seal.

    Ilyan Roe watched Berth Six from the adjoining console. Both harbor tugs held the supply craft against the damaged capture frame. The forward actuator and station-side socket were gone. One tug carried six percent more lateral load than planned, and every correction consumed harbor attention the berth could not spare.

    “Route expansion requires separate authorization,” Roe said.

    “I’m asking for eight seconds.”

    “You’re asking me to divide protected attention.”

    “For one event, terminating at the first protected boundary. The result can remain in volatile capture after the slot closes.”

    Roe examined the harbor load bars. “No configuration history?”

    “No.”

    “Endpoint identity?”

    “No.”

    “R-17 history?”

    “Not in this request.”

    The compaction counter reached ninety-seven.

    Roe opened an authorization pane between their consoles and dictated the limits into the room record.

    “Vault metadata only. Source media remains unmounted. Select the known rejected query. Expand its route to the first protected classification and no farther. No inherited access. No traversal beyond the returned boundary.”

    He added an eight-second hard termination.

    “If either tug exceeds its temporary load ceiling, if restraint confidence falls below ninety-eight percent, or if projected drift touches the reduced envelope, the harbor core aborts before the eight seconds expire.”

    Mara read the generated authorization. It granted no continuing claim on protected attention and no authority to inspect whatever service lay behind the boundary.

    “Result held in volatile evidence memory after termination,” she said.

    Roe inserted the term and signed.

    The controller chained his mark to the active harbor session. An eight-second counter appeared beside the compaction timer.

    Mara launched the recipe.

    8.0

    The vault accepted Roe’s signature without changing the custody state of COPY ONE OF ONE.

    6.9

    Raw controller notation filled the evidence pane. Mara selected the known event by sequence number rather than scrolling through adjacent traffic.

    5.8

    The event resolved against the vault’s committed live root. It had reached the exact evidence slot forty-three seconds after sealing.

    4.6

    Its requested fields appeared: media type, declared capacity, custodian status. No mount, transfer, decryption, duplication, or source validation had been requested.

    3.3

    The route token expanded by one segment.

    LOCAL SERVICE RELAY—PROTECTED

    The routine stopped at that boundary. No internal configuration, attached service, prior traffic, or endpoint identity crossed into the result.

    1.9

    The controller copied the raw entry, route fragment, classification, timing reference, and retrieval recipe into volatile evidence memory.

    Three attribution fields remained empty: credential, registered process, operator.

    0.7

    Mara removed her hand from the launch control.

    0.0

    Roe’s authorization terminated. The route pane froze, and protected attention returned to harbor operations automatically.

    The compaction timer showed eighty-eight seconds.

    Roe turned fully to Berth Six. Tug load had risen by less than half a percent during the division. Restraint confidence held at 98.4 percent, but projected drift had moved closer to the temporary envelope.

    He ordered a two-degree correction in the reserve frame, reduced the permitted drift envelope, and waited through a complete restraint cycle. The overloaded tug returned to six percent above plan. Its paired tug accepted the redistributed impulse without oscillation. Cargo transfer remained locked.

    “Berth stable inside the revised envelope,” Roe said. “No second authorization implied.”

    “Recorded.”

    Only then did Mara begin preservation.

    Hashing the volatile capture required no harbor slot. She fixed the raw entry first, followed by the single route fragment, the controller root, Roe’s authorization, and the exact query recipe. The manifest identified each dependency and excluded the source media. COPY ONE OF ONE had contributed nothing to the route result because it had never been mounted or read.

    Roe independently compared the captured controller root with the vault’s published commitment.

    “Match.”

    He countersigned the first manifest.

    The wall recorded:

    EVENT 1 PRESERVED ROUTE SCOPE AUTHENTICATED SOURCE ACCESS: NONE

    Mara opened a custody note and separated the findings before inference could enter the language.

    The first request had addressed the exact slot forty-three seconds after sealing. It preceded the anomaly report, the later mount demand, and every accessible record identifying the slot as casualty evidence. It had crossed a protected local service relay and arrived without a displayed credential, registered process, or operator.

    None of that identified an issuer.

    Roe read the draft over her shoulder. “The relay knew the slot.”

    “The request contained the slot address.”

    He looked at the correction.

    “The record does not establish what component obtained it,” Mara said. “Or whether the relay retained it.”

    Roe nodded once. “Use that.”

    She entered the narrower statement. The distinction left malformed inventory traffic, delayed sealing traffic, queued verification, and upstream address assignment available as explanations. Suspicious timing did not remove them.

    The counter reached sixty-three seconds.

    0 chapter views

    0 Comments

    Note
    6 online