Chapter 71: Reference Stabilization
The contract turned Asha's warning into a deliverable someone could invoice.
On Thursday, Samuel opened D14's final scope inside KRR's restricted data room.
The sentence sat beneath ordinary services for public monitoring and factual corrections.
Its third item authorized proactive contact with prospective employers and clients under reference stabilization.
Grant's response called the phrase lawful consistency management.
Samuel said a service description could be lawful and still require testing against actual work.
He placed D13's redacted contact index beside the contract without opening any private reference record.
The procurement custodian had retained the native agreement, amendment history, and approval ledger.
KRR held controlled copies whose hashes matched the custodian's export receipts.
The Grayfield platform separately supplied the L10 dispatch and service index already authenticated in May.
No amount appeared on our screen.
Even a verified total would have shown purchased capacity, not the purpose of an individual assignment.
Judith's protected bank, tax, and account fields remained closed.
I asked whether the paid invoices proved that the unusual item had been ordered for Jonah.
“Not without the task link,” Samuel said.
He selected the first D13 report and exposed only its task number, date, and service category.
The same number appeared in L10 beside a work order and a completed-contact entry.
It appeared again on D14's scope allocation page beneath reference stabilization.
Three independent systems had preserved the same identifier for different purposes.
The contract defined what Grayfield could deliver.
The field report described what its staff recorded doing.
The dispatch log fixed when the assigned service moved through the platform.
None of those records alone established who wrote the script or why the task was approved.
Samuel then displayed Asha's limited W02 process statement.
Her words explained only what happened when a risk field reached her own reference workflow.
She had routed outside inquiries to the strategy office and had not decided their answers.
Her statement contained no amount, employer identity, private question, or applicant history.
KRR used her words as a process key, never as permission to open the underlying reference.
The workflow label matched D14's service label without expanding what Asha had personally witnessed.
I signed the viewing restriction before Samuel unlocked the next task row.
Its identifier followed the same three-record route.
So did a third.
The fourth carried a different department prefix but the identical stabilized-reference service code.
Grant argued in writing that repeated codes could reflect administrative efficiency rather than retaliation.
Samuel preserved that explanation in the response column.
He also preserved the fact that the deliverable expressly included proactive outside contact.
I wanted the four rows to become four names because names made the harm easier to hold.
The data room gave me only redacted case IDs.
KRR's identity custodian kept the mapping outside my access register.
Samuel warned that matching identifiers did not establish four proven injuries.
One task could involve lawful verification, disputed language, or no measurable outside result at all.
They established four tasks requiring protected, case-by-case review.
He locked the D14-D13-L10 crosswalk and issued separate verification requests for each row.
Each request traveled through KRR rather than Claire, Jonah, or a Whitmore office seeking names.
The lock receipt named the source custodians, native formats, hashes, and access limits.
No total invoice value entered the finding.
No percentage became a claim about the company's entire workforce.
The narrow conclusion was harder to headline and easier to defend.
WMG had purchased a service that allowed proactive contact with potential employers or clients.
Four task numbers had moved through that service category.
Whether each involved a protected complaint, an authorized script, or an external consequence remained open.
Samuel replaced the single-case review label with FOUR PROTECTED CASE TESTS.
The four task numbers belonged to four different complainants, not Jonah alone.