Chapter 24: The Protocol
The protocol never used the word retaliation; it used the word stability eleven times.
On Thursday morning, a WMG policy custodian opened D05 inside a read-only data room while Priya observed from the authorized seat beside mine.
Daphne's company authorization controlled the view. Priya was present for WCT's fund-risk inquiry, not as commander of WMG records.
Grant sat across the table with Dana.
The screen disabled download, print, copy, and capture.
Every page turn entered the custodian's access log.
A moving watermark carried my name, the session number, and the time, making any unauthorized image traceable without giving me a copy.
Issue Management Protocol, Version Four, sounded responsible in its opening purpose.
It coordinated workplace safety, legal response, communications, and stakeholder continuity during events that could disrupt employees or public operations.
Most of its examples were ordinary.
A threat at a worksite required safety escalation.
False public information could require a documented correction.
An employee facing media harassment could need privacy and security support.
Legitimate examples mattered because a rule could protect people in one case and become a shield for pressure in another. The text alone could not tell us which.
“Those functions are legitimate,” Grant said.
“On the page, yes,” I replied.
The sentence denied me an easy villain and denied him an automatic defense.
We reached the intake section.
Managers could open a protocol file for safety risks, litigation threats, external complaints, media attention, or operational instability.
The categories overlapped without explaining when a person asking an internal question became an external risk.
The intake section required coordination but gave the visible reader no answer about who challenged an external-stability label or separated a complainant from a threat actor.
Nothing in the text instructed anyone to punish a complainant.
Nothing proved the process had been used against Jonah.
I asked the custodian to display the version footer and approval path.
Version Four had a policy-repository identifier, an effective date, and a multidepartment approval block.
Andrew's name did not appear on the visible policy approval page.
That absence neither cleared nor implicated him.
“What are you asking to obtain?” Grant said.
“Not this file for myself.”
Dana placed our proposed scope request on the table, outside the data-room system.
It asked that a future independent review receive all native protocol versions, deployment history, approval trail, and a protected sample of uses from the relevant period.
The request did not assume the samples would show abuse.
It asked for the records needed to test whether written safeguards matched actual use.
Any use sample would need redaction, lawful company approval, and direct delivery to the reviewer. I would not receive employee narratives while waiting for that process.
Grant objected that no independent reviewer had been selected or authorized.
“Then the request belongs in the pending scope record, not in Claire's possession,” Priya said.
She did not order the custodian to export anything.
Dana submitted the scope request to Daphne's WMG board channel and separately recorded WCT's nonprofit interest in the fund language.
Two entities received two notices.
Neither notice created review access.
The custodian gave Dana a page-number index showing what we had viewed and the applicable repository identifiers.
No native file, attachment, or employee-level sample left the room.
The protocol remained D05 in WMG custody, first seen but not independently acquired or validated.
That limit changed the investigation anyway.
Grant could still argue that Jonah's dispute was personal.
He could no longer deny that WMG maintained a formal process capable of joining internal events, legal response, communications decisions, and public stability under one administrative label.
Whether it had done so lawfully required versions, deployment records, and use samples we did not yet have.
The slower conclusion was the honest one.
At the final appendix, the custodian enlarged a trigger category omitted from the purpose page.
The words sat inside a box labeled EXTERNAL STABILITY REVIEW.
Internal challenge likely to reach external stakeholders.