Chapter 42: Deployed at 4:12
At 4:12 p.m., the matrix stopped being a draft and began deciding where complaints went.
On Monday, April 21, Marcus projected the HRIS deployment log inside KRR's restricted demonstration room after the custodian verified his export receipt.
His attorney sat beside him, and his anti-retaliation protection remained attached to the session record.
Samuel controlled the keyboard while Marcus described only what the system had recorded.
The first screen displayed the D06 version hash already preserved by the HR custodian.
The second displayed L05, the policy-version and deployment log generated automatically by the HRIS platform during ordinary system administration.
Its hash entry matched the matrix KRR had reviewed on Friday.
Marcus explained that a match connected the deployed package to that file version.
It did not identify the person who wrote each field or approved its business purpose.
Grant repeated that distinction before Samuel could ask his next question about the named account.
"An author account may be an administrative uploader," he said.
Samuel entered the limitation directly into the evidence matrix.
The account label naming Andrew's strategy office did not prove Andrew personally drafted D06.
The upload event did not prove he reviewed, understood, or approved the matrix.
Marcus agreed without offering an opinion about Andrew.
He advanced to the production-history panel.
An earlier version had remained in staging throughout the morning of the recorded Issue 17 closure date.
At 3:58, the platform recorded a final package validation.
At 4:07, a deployment job entered the approved production queue.
At 4:12, that job completed across the linked HR and communications workflow environments.
The timestamp came from the server clock and its retained audit record.
Marcus showed the clock-synchronization certificate and the export method used for L05.
KRR's custodian recorded the source, query, operator, time range, and resulting hash.
No one in the room could edit the production history through the read-only interface.
The Issue 17 record showed administrative closure earlier that same day.
L05 therefore established a deployment sequence that the earlier D05 text alone had not supplied.
It still did not explain why Issue 17 closed or whether the deployment targeted Jonah.
Samuel linked D06 and L05 in the evidence matrix under system timing.
He left motive, authorization, implementation, and individual consequence as separate open questions.
I watched four conclusions remain blank where a press statement would have filled them instantly.
Grant asked whether the timing could reflect a routine quarterly release.
Marcus said the log contained no field for routine, urgent, retaliatory, or benign.
It recorded package state, job state, environment, account, and time.
Samuel requested the formal approval workflow rather than treating absence of a motive field as evidence.
The request sought authorization records from the proper communications and HR custodians.
It did not ask Marcus to reconstruct conversations he had not witnessed.
His role ended with system provenance and deployment mechanics.
He signed a narrow technical declaration describing those boundaries.
KRR's custodian sealed the native L05 export, working copy, and demonstration recording together.
I received no copy and no right to revise Marcus's wording.
Samuel then opened the deployment-target list, with employee identities and unrelated accounts redacted.
Each retained row showed an environment, access group, and service-account destination.
The list confirmed that D06 reached both HR review and communications review functions.
That was institutional plumbing, not proof that every routed complaint produced an adverse act.
The witness needed to explain reference practice had not yet entered the process.
Samuel marked that future proof requirement beside W02 and kept the identity restricted.
At 11:38, the technical session ended and Marcus left with his attorney.
One external destination remained visible because it belonged to the preserved Northline project scope.
The account name was Elena Ruiz.