Chapter 81: Calls After the Pause
Andrew stopped the work cameras could see and left the calls no one could photograph.
On Thursday, Samuel placed the authenticated D15 note at the center of KRR's timeline screen.
The board custodian's native file matched Grant's submitted copy in text, date, and version history.
Its routing field still defined the exception as media outreach.
L10 then showed what happened after the approval time.
Public monitoring summaries and press-response tasks moved into paused status before the next business cycle, with cancellation events preserved in the vendor log.
WMG was entitled to have that correction recorded accurately.
Grant's response said Andrew had recognized an external-activity risk and stopped the disputed program.
Samuel divided that sentence into categories instead of accepting or rejecting it whole.
Media outreach had stopped.
Public-facing fact correction had stopped pending review.
The reference-contact queue had not been named in D15.
Its work orders did not move to paused status.
They changed from media-response support to relationship stabilization service under D14's final scope.
The first replacement task entered the vendor platform six hours after the note, carrying the same regional queue but a newly selected service label.
The second followed the next morning with the same protected case identifier.
L10 fixed those times and categories without explaining anyone's motive.
I asked whether changing a code proved an attempt to hide the calls.
“No,” Samuel said. “It proves the operational route changed.”
Intent required other records and witnesses.
Judith's W07 statement explained the ordinary approval mechanics for a changed service category.
She had not written the scope or approved the field language.
Her evidence established that the altered category could not activate without both required role approvals.
D14 supplied the corresponding scope term and purchase-order rule.
The field report supplied the recorded contact activity, including completion time and the limited outcome code entered by the caller.
The dispatch log supplied the service time.
No fee amount appeared on the matrix, and KRR did not infer a financial motive from the existence of a paid vendor relationship.
The existence of payment supported company resources, not the private purpose of each approver.
Samuel marked PARTIAL PAUSE in the D15 column.
He refused Grant's proposed wording that Andrew had ended the entire protocol.
He also refused my earlier fear that the note had stopped nothing.
The stopped media tasks remained green in the correction column.
The continuing reference tasks remained red only as issues requiring responsibility analysis.
Color did not turn either category into a complete verdict.
KRR locked the D15-D14-L10-W07 timeline and issued the same limited finding to all responding attorneys.
The source custodians retained the native note, contract, and platform records, while KRR's controlled copies carried separate intake hashes and access histories.
I received a participant summary with task IDs, categories, and proof limits.
Jonah received nothing outside his own attorney channel.
The narrower result cost me the brief belief that Andrew had tried to stop everything.
It also prevented the report from erasing what he had actually stopped.
Samuel added that the continued calls still required proof of authorization at the relevant levels and could not be attributed from a category name alone.
The first post-note task displayed an approval event from the strategy office role queue.
The second field displayed an approval event from the chair office role queue.
Neither role event alone identified the human user without the source access record.
Neither proved that the approver understood every later script.
Together they satisfied D14's activation condition for that task.
The work could not proceed on a single approval.
Samuel enlarged the two native fields without exposing invoice values or account details.
One belonged to the strategy office.
The other belonged to the chair office.