Chapter 115: Asha Uses Her Name
Asha put her name on the statement and kept the rest of her life out of it.
On Wednesday, KRR convened a protection meeting with her attorney at the table.
I attended as an affected participant without a vote or private consultation role.
The protection coordinator began by asking whether anyone had requested public identification from Asha.
Her attorney said no.
Samuel confirmed that KRR did not require a name to retain the statement's evidentiary value.
The existing protected version could remain protected without weakening its place in the review. Its identifier, authentication, and corroborating documents would remain unchanged.
Asha said she still wanted her name used.
She wanted readers to know that a former HR business partner had described the routing process.
Her decision did not authorize her home address, family information, or current employer. It also withheld schedules that could reveal her work or travel.
It did not authorize private legal advice or every detail of her interview.
The coordinator displayed a field-by-field public authorization.
`Asha Bell` appeared in the name field.
`Former HR business partner` appeared as the relevant role.
The process facts she had already verified appeared in the statement body.
Her street, personal phone, family names, and current workplace remained protected.
The same restrictions applied to document metadata and download properties. The filename would use the statement identifier, not her upload name.
Asha reviewed each public field with her attorney. The coordinator required an answer for every field instead of treating one signature as unlimited consent.
She corrected one old title that implied she had supervised the entire department.
Her actual role remained narrower and more accurate.
Samuel asked whether she understood that news outlets could repeat the public name and role.
She said yes.
The attorney described the existing contact route for press requests and online harassment reports. Requests would reach counsel, not Asha's personal email or phone.
Asha could decline every interview.
Using her name did not create a duty to answer strangers.
Her independent legal support remained active. KRR documented it, and the record showed no payment or promise tied to naming herself.
Her career protection did not depend on Claire, Jonah, WMG, WCT, or public praise.
I was asked only whether the proposed public wording misstated an event I had personally attended.
It did not.
I gave that limited answer and stopped.
I did not tell Asha that naming herself would help the package.
I did not warn her away because Vivian might attack.
Either response could have made my needs part of her choice.
The coordinator tested the public copy against the authorization fields. Another staff member repeated it from a clean account.
No protected field appeared in the page, index, file name, or properties panel.
The underlying signed statement remained under KRR custody with its original restrictions.
The public version received a separate hash and release boundary. Its index identified it as a redacted derivative, not the source.
At 2:52, Asha signed the authorization in her attorney's presence.
KRR countersigned the protection confirmation without changing the source record.
Her name increased her personal exposure, not the scope of what her testimony proved. The methods note would call identification voluntary, not a credibility score.
The supporting documents and logs remained necessary.
One witness choosing visibility did not establish a standard for another. The written ruling barred reviewers from turning Asha's choice into pressure.
I accepted that the public package could contain different levels of identification without ranking anyone's courage.
The protection coordinator locked Asha's choice and its review date.
Her attorney retained the complete authorization and KRR retained the protected original.
I received only the public-field confirmation.
Before the meeting ended, a separate preference arrived through another attorney channel.
Lila authorized her initials and supporting documents, but no full name, current employer, or media contact.
Her choice would be different from Asha's and governed by the same privacy rule.