Chapter 68: Opened, Not Understood
Six minutes glowed beside Andrew's user ID; Samuel labeled the field opportunity to review and left intent blank.
The portal custodian projected the native access export inside KRR's demonstration room.
Every row came from the board system rather than a screenshot or reconstructed spreadsheet. The export retained native event identifiers.
The vendor preserved server time, file version, user ID, action type, and session duration.
KRR verified the export hash against the board portal's retained source record before Samuel interpreted any event field.
The first row showed Vivian uploading the employability memo under her authenticated account.
That event supported submission, not proof that she personally typed every sentence.
The distribution event placed the file in the listed recipients' board workspaces.
Andrew's account opened the document the following morning.
The system recorded six minutes between opening and closing the file pane. It did not record scrolling, eye movement, notes, or attention.
It could not show whether he read every page.
It could not show whether another person used the authenticated session.
It could not show understanding, agreement, objection, or later instruction.
Samuel fixed the field label before anyone argued about meaning.
OPPORTUNITY TO REVIEW appeared beside Andrew, Vivian, and each recorded board recipient.
No row received KNOWLEDGE, APPROVAL, or INTENT.
Grant argued that a file-open event was worthless without proof of comprehension.
Samuel answered that it was limited rather than worthless.
The log could defeat a claim that the memo never reached the account. It also fixed the version available during that session.
It could not establish what the account holder concluded after it arrived.
I asked whether six minutes made Andrew more likely to have read it.
Dana stopped the question before Samuel had to speculate.
Duration described a session, not attention. A document could remain open while its user handled another task.
KRR preserved my question as an example of the inference the method prohibited.
The other directors' rows varied from seconds to several minutes.
Those differences created no hierarchy of guilt. Samuel prohibited ranking recipients by minutes or clicks in any responsibility summary.
Samuel requested the meeting agenda, annotated action list, subsequent revisions, and nonprivileged distribution materials.
He also requested interviews with the author, recipients, and anyone assigned implementation work.
The logs would provide dates against which those independent sources could be tested.
They would not substitute for those sources.
The custodian then opened the revision directory without displaying protected document content.
Two later versions carried the same external employability heading.
Their existence proved revision activity, not approval or deployment. The directory did not reveal who requested each change.
KRR sealed the directory and routed the documents for ordinary privilege and privacy screening.
I signed the limited demonstration summary with the word understood deliberately absent.
Andrew's account had received an opportunity to review Vivian's proposal.
That was more than the family story had admitted and less than motive.
The restraint felt familiar now, which did not make it easy.
I had once turned an incomplete brief into a clean public certainty.
KRR would not let me repeat that habit with an access log.
At 3:36, Samuel received a protected-contact update tied to the revision directory.
The name belonged to a former regional supervisor listed in an implementation routing field already within the approved review scope.
Devon Chase had been located through his public attorney channel.
He had supervised regions where protocol tasks were assigned and reviewed.
KRR sent him a neutral protected-process explanation without describing expected testimony.
His attorney returned a conditional acceptance before the demonstration ended.
Devon would attend a protection meeting the next morning if one employer document arrived first.
He required written assurance that his current employer would not retaliate for truthful participation.
Until that protection existed, he would say nothing about what followed the memo.