Chapter 74: Four Green Arrows
The deck reduced four careers to a green arrow labeled contained.
On Tuesday, Samuel opened the board-portal return beside Devon's D10 work copy.
The native files carried the same deck identifier, version number, and visible content.
Their hashes matched after KRR normalized only the portal's export wrapper.
The vendor custodian documented that technical step and preserved both originals.
Devon's copy had passed its source check.
Each of the four rows showed a redacted risk ID, department, quarter, and containment percentage. The percentage measured internal closure against the deck's own definition, not employment loss, client decisions, or human recovery.
No row named a person on my screen.
No row described a reference call, client warning, script, or outside decision. Nothing in the deck allowed me to translate a green arrow into a particular act without another source.
Green arrows said the protocol had reached an internal status.
They did not say how that status had been produced.
Grant's response emphasized the absence of contact methods.
Samuel agreed that D10 could not directly prove one.
He moved the method column out of the deck and into the case crosswalk.
The first ID matched Jonah's tested record through its custodian-controlled mapping.
The second matched the procurement case without showing me its private file.
The third matched operations and Devon's two task sheets.
The fourth remained a protected project-management record awaiting witness consent.
KRR did not convert four IDs into a total workforce count. Four rows were four reviewed rows, not proof that only four people existed or that hundreds had been harmed.
It used them to ask whether the same four cases had been summarized upward.
The portal export included distribution fields and version history.
The custodian's declaration explained how revisions were stored, how account events were generated, and which fields administrators could alter.
Andrew's account and several board accounts had received the original deck.
L07 showed opportunity to review, not comprehension, agreement, or instruction.
Samuel repeated that label beside every open event.
Vivian's account opened D10 on the evening it was distributed.
Sixteen minutes later, her account downloaded the source deck.
At 8:47, the same account uploaded a new annotated version.
The annotation field beside the four arrows read expand external controls.
The log established account activity and sequence.
It did not establish who physically used the account without further verification.
It did not prove what Vivian understood about any unnamed individual.
Her attorney requested that the annotation be treated as risk-management vocabulary.
Samuel preserved the interpretation as a contested explanation.
He also preserved the native wording and its timestamp.
D09 had proposed external employability risk at the policy level.
D10 had summarized four IDs as contained without naming the method.
L07 now connected Vivian's account to an instruction to expand external controls.
KRR still needed Devon's supported statement and recipient responses to test implementation responsibility.
Samuel authorized notices to the identified recipients through their attorneys.
Each notice separated receipt, understanding, approval, and implementation so a single open event could not answer all four.
The notices quoted no protected name and disclosed no private reference record.
They asked who prepared, reviewed, or acted on the annotated version.
I signed the observation log without calling the arrows proof of four ruined careers.
One external consequence remained unverified even in the strongest tested case.
The deck showed how management measured success, not everything success had cost.
Its language made containment visible while keeping the underlying people and methods outside the board slide.
KRR locked the D10-D09-L07 crosswalk with Devon's statement marked corroboration pending recipient response.
The final history panel displayed the original upload, Vivian's open event, and the annotated upload.
No entry recorded her private motive.
No percentage supplied the missing method.
The last event still carried her account name.
That same night, Vivian's account had uploaded the version marked expand external controls; who used the account and what Vivian understood still required verification.