Log InRegister
    Read Free Web Novels Online

    Mara removed the roster request before Sen could object to it.

    The application pane marked the deletion in amber.

    SB-R2 DUTY ROSTER — WITHDRAWN.

    Below it, she struck the demand for the final-disposition partition.

    DOWNSTREAM DISPOSITION RECORDS — WITHDRAWN.

    Ilyan watched both lines disappear. His suspended credential lay dark against his wrist.

    “You are surrendering the two records that could name who acted and what happened.”

    “I am refusing records we cannot compel.”

    The adjudication chamber smelled of stale air and overheated seal polymer. A transfer pump vibrated through the deck beneath Mara’s chair, just irregularly enough to sharpen the pulse behind her right eye. She kept one hand flat on the console until the room stopped shifting.

    Sen stood beside the independent evidence cradle. Its seal indicators had changed from blue to white as the chamber brought his preserved package into the filing environment without opening it.

    Mara entered the remedy that remained.

    One production of the endpoint-validation receipt identified by authenticated checksum RC-B. No roster data. No identity correlation. No authorization payload. No endpoint topology. No final disposition.

    Sen read the line twice.

    “You are not asking the adjudicator to infer that RC-B is an endpoint receipt?”

    “No. I am asking the registry to return the discrete object whose native checksum matches RC-B, if such an object exists.”

    “And if the object is embedded in a protected partition?”

    “They may redact excluded fields. They may not substitute another object.”

    Ilyan leaned toward the pane. “If RC-B returns nothing, this application is spent.”

    “Yes.”

    “We already have RC-A.”

    “RC-A is the queue receipt.”

    “A queue receipt that proves the commitment entered processing.”

    “It proves queue acceptance. It does not prove endpoint validation.”

    Mara attached Sen’s custody certificate. The filing system requested the comparison originals, and Sen placed his hand over the cradle control.

    “Authority for submission?” he asked.

    “Comparison only,” Mara said. “No waiver of independent custody. No permission to alter, normalize, or derive identity data.”

    “Purpose?”

    “To establish that RC-B identifies a responsive record separable from the roster partition.”

    Sen released the package.

    The cradle grew warm as its internal seals authenticated. On the chamber display, the preserved contents appeared only as inventory: the original RC-A queue receipt, checksum records RC-A and RC-B, the authenticated SB-R2 commitment, the prior production limit, and Sen’s closing hash.

    A notice flashed at the edge of Mara’s console.

    CASUALTY ADMINISTRATION: TOMAS VALE — EFFECTS DISPOSITION AUTHORIZATION OVERDUE.

    The system had linked the notice because the filing referenced the collision review that contained his death record. For half a second she saw his paper notebook held open beneath a dispatch lamp, his thumb marking a page he had promised to explain after shift.

    Mara classified the notice as unrelated administrative material, suppressed it from the adjudication display, and entered a deferred-response timestamp.

    Sen saw the motion. He said nothing.

    She submitted the application.

    The request crossed the relay in measured stages. Registry acknowledgment took 1.4 seconds. The adjudicator’s chamber received it after another 1.3. No one filled the delay with speech.

    The transfer registry representative appeared as a narrow projection above the opposing console, her image resolving from the face outward.

    “The registry objects,” she said. “The applicant describes the requested object as separable, but endpoint-validation receipts inherit duty metadata from the validating service. Production by checksum may expose branch assignment, countermark provenance, service rotation, or partition structure even if personal identity fields are suppressed.”

    Mara opened the package inventory rather than the evidence itself.

    “The objection assumes every inherited field is roster data.”

    “The inherited fields can permit roster reconstruction.”

    “Then redact reconstructive fields.”

    “Redaction changes the object whose checksum you rely upon.”

    “The produced view may be redacted. The source object can be matched inside the audited environment before excluded fields are suppressed.”

    The representative’s answer arrived after the relay pause. “That process would confirm that the registry possesses a record associated with a protected endpoint.”

    “The registry already confirmed preservation of RC-B.”

    “Preservation does not establish record type.”

    “No. That is why I am requesting the receipt rather than asserting what RC-B contains.”

    Ilyan shifted behind her. Mara could feel his impatience without looking at him.

    The registry representative continued. “The applicant also possesses RC-A, a responsive queue receipt. The demand for RC-B risks duplicative access to the same protected routing event.”

    Mara brought RC-A’s certified header onto the pane.

    “RC-A identifies queue acceptance. Its issuing service is the reserve queue. It contains no endpoint-validation signature. RC-B has a different checksum, a different protected reference, and independent preservation status. I am not asking the registry to explain the difference. I am asking it to produce the discrete RC-B object if that object is a validation receipt.”

    “And if production exposes the validator branch?”

    “Branch identity is not human identity.”

    “It may narrow the duty roster.”

    “Then the ruling can bar correlation and derivative inquiry. A possible later inference is not grounds to withhold a separable record now.”

    Sen glanced at Mara when she said it. The roster reference remained crossed out on her application.

    The adjudicator entered the channel without ceremony. Only a seal and a voice appeared.

    “Custodian Sen, can substitution occur without breaking your preserved package?”

    “No,” Sen said. “RC-B was sealed before this application. A returned object must close against the preserved checksum or fail comparison.”

    “Can you perform that comparison without disclosing excluded source fields to the applicants?”

    “Yes. The registry can expose the source object to the chamber verifier. I can certify checksum closure after the authorized view is generated.”

    The adjudicator addressed the registry. “Is the receipt stored as a distinct object?”

    A longer delay followed.

    “It is logically distinct,” the representative said. “Its metadata dependencies are not.”

    “That was not the question.”

    0 chapter views

    0 Comments

    Note
    6 online