Chapter 92: The Page I Printed
I had carried the six lines into our shared house myself, one careless print command at a time.
At 09:00 on Thursday, an independent technician opened the limited device report before my solicitor and me.
The review room contained no printer, only a sealed evidence drive and two blank monitors.
That felt deservedly austere: a room designed to remove the family story and leave only timed technical facts.
The technician began with my personal laptop's outbound print record.
On 8 September at 07:16 BST, my device had sent one job to the shared household printer.
Its page count was one.
Its derived hash matched the protected extract already listed in my custody note.
The report did not display unrelated documents or household folders.
I confirmed the command had been mine and that the laptop had been under my ordinary control when it was sent.
No one had tricked me into pressing print.
I had wanted to mark the rhythm on paper before an early call, a convenience I later replaced with the clean room.
The technician showed the printer's retention setting as it existed that morning.
Completed-job metadata remained cached for twenty-four hours unless manually cleared.
The cache recorded a job, not a reader.
It could not show whether the sheet landed face up, stayed in the tray or was collected.
It could not identify eyes in a room, hands on a page or any decision made after collection.
My solicitor made me repeat that limit for the statement.
“The record proves my device printed the page,” I said.
“It does not prove who read the paper.”
The technician added that the household access cutoff occurred the next day at 18:00.
Oliver still had ordinary access when I created the risk.
Ordinary domestic access did not grant permission to reuse unpublished writing, but it made physical opportunity unsurprising rather than secret.
It did mean I could not pretend the page had been protected like my later clean-room files.
I signed the factual statement with the failure included.
My solicitor attached the earlier custody disclosure and barred any inference beyond this one job.
The technician then opened the router event summary after confirming that its collection authority excluded every unrelated category of household traffic.
Only traffic connected to the printer and its diagnostic service had been extracted.
Other browsing, messages and devices remained outside the scope.
At 07:18, my laptop had disconnected from the printer service.
At 07:19, the printer reported the job complete.
Nothing in those entries identified a person beside the tray.
I felt anger arrive, then turn towards the correct address: partly mine, because secure authorship included admitting when my own practice had failed.
The formal record would never let me tell the cleaner story.
That was the price of asking it to tell a reliable one.
The technician sealed the sending record, cache settings and limited router export under one hash schedule.
He retained the forensic image.
My solicitor and Oliver's solicitor would receive the same signed report.
I received a read-only copy and no unrelated household data.
The platform would receive only the conclusion needed for its preservation review, not a map of our former home's private digital life.
My solicitor asked whether I still wished to proceed after admitting the weak custody.
“Yes,” I said, “with the weakness attached.”
The report supported possible access, not copying.
The public comparison supported specific overlap, not the route by which it happened.
Those propositions remained separate on the summary page, with no arrow pretending that opportunity automatically completed the missing act.
At 09:38, the technician expanded the final authorised router entry.
A household account had contacted the printer service at 08:02 that same morning.
The account name was Oliver's.
Its logged action was precise but still limited.
At 08:02, Oliver's account downloaded the printer diagnostic package.