Chapter 86
The Code I Left Behind
Cal Price asks for immunity before he says which Vale director Jonah served.
The request lands in the interview room at 8:07 a.m., twelve hours after six supervisors lost system access and company devices. Cal sits with his lawyer on one side of the table. Rina and an independent investigator sit opposite him. Adrian stands near the wall instead of taking the empty chair beside me.
That distance is intentional. Today I am not his father or the former chairman who once settled uncertainty with a look. I am a director whose old approvals may be evidence.
Marisol negotiated the conditions for this first meeting. It is a proffer, not immunity. Cal may describe what he knows without the company using his statements as the sole basis for discipline, but outside authorities retain their own power. The investigator records the session on two encrypted devices. One creates the primary file; the second creates a simultaneous backup. At the end, counsel will hash both recordings, seal the primary, and place the backup in the municipal evidence vault.
The vulnerability is stated aloud: Cal has had fourteen hours since his access was suspended to speak with other supervisors. His memory may be influenced, and his lawyer has not disclosed those contacts. Corroboration must come from records created before yesterday.
"Full immunity," Cal says again. "Then I give you the director."
Adrian answers before the investigator can. "You do not get a pardon in exchange for an accusation."
Cal's lawyer turns toward him. "Mr. Vale is here as what, exactly?"
"Finance committee representative."
"The same committee that approved procurement funding?"
Rina closes her notebook. "This is why roles were listed in the notice. Adrian may ask questions after the proffer begins. He does not decide criminal immunity, employment discipline, or witness protection."
My son dislikes the correction. He accepts it.
The investigator offers Cal a narrower written term: if his evidence is materially corroborated, outside counsel will recommend continued paid leave rather than termination while authorities review his conduct. No promise binds the city or prosecutors. Any lie voids the protection. Cal reads it twice and signs at 8:19. His lawyer signs as witness. The investigator uploads the executed page to the case portal at 8:22 and records its checksum in the room log.
"Jonah did not make final decisions," Cal says. "He reported to a director."
"Name the director," the investigator says.
"I never saw a name. I saw an authorization code."
Adrian's impatience sharpens the air. "Codes can be copied."
"This one opened exceptions. Supplier substitutions, sole-source approvals, archive releases. The requests would come back with MV-04. Once that code appeared, procurement treated the exception as board-authorized."
My initials seem to rise from the table.
The investigator looks at me. "Do you recognize that code?"
"Yes. It was assigned to me during Owen Vale's hospitalization."
Cal leans back after placing his weapon where everyone can see it.
I make myself continue. "It was a temporary board-continuity credential. Owen was incapacitated. Several directors traveled between the hospital, headquarters, and Wondervale. The code allowed urgent approvals to move without his physical signature."
"Who had access?" Rina asks.
The shame is practical before it is emotional. It has dates, people, and a policy I helped weaken.
"I did. Diane Mercer administered the board portal. Jonah received procurement packets carrying the code after approval. During the first three weeks, my two sons and the general counsel also received printed continuity binders. I do not know whether the code itself appeared in every binder."
Adrian turns from the wall. "You told us those were reference copies."
"They were supposed to be. We were moving decisions while Owen was in intensive care. I allowed urgency to replace access control."
"How long was the code active?"
"It should have expired when the board restored normal delegation. I cannot testify that it did."
The investigator requests the continuity policy, access-revocation record, and original code registry through outside counsel. I do not call Diane or search my old files. That would turn a witness into an investigator inside his own history.
Cal describes the workflow. A procurement manager entered an exception. Jonah reviewed it. A director-level code appeared in the approval field, sometimes minutes later, sometimes the next day. Cal claims he never saw Jonah type the code. He says the code was treated as authority because audits tested whether the field was populated, not who controlled the credential at the moment of use.
Rina asks him to reconstruct one request without looking at his papers. Cal names the BrightSpan substitution that later reached Harbor Flight. He remembers creating the request on a Tuesday after a supplier delay, Jonah returning it Thursday, and the approval arriving before Friday's operations call. The preserved calendar places the call on Friday, but the exception log dates approval Wednesday. Either Cal's memory is wrong or the record moved through a path he did not see. The discrepancy is entered beside his statement. A useful witness is not made credible by erasing the parts he remembers badly.
"Who received notice when the code approved an exception?" Rina asks.
"Procurement, finance, and the requesting supervisor. Directors received a weekly digest."
Outside counsel requests those digests too. If they survive, they may show whether warnings reached the board. If they do not, the retention failure becomes another institutional cost rather than an excuse to trust Cal.
"Did you approve exceptions under MV-04?" Adrian asks.
"I processed them."
"That was not the question."
Cal's lawyer objects, but Cal answers. "I approved three supplier substitutions after the system showed board authority. I did not inspect the board minutes."
The admission gives his story a cost. It does not make it true.
At 9:03, outside counsel delivers the original registry. Diane created it seven years ago and signed each issue line in ink. The scanned record entered the preserved archive eighteen months later. Its paper original remains in a numbered corporate-records box now held by counsel. The registry lists MV-04 as mine and gives an expiration date thirty days after Owen returned home.
The revocation log is missing.
Rina notes the weakness. A registry proves a code existed and should have expired. It does not prove the credential remained active, nor does an approval bearing the code prove I used it.
Then the portal team produces a preexisting system export created during a 2023 access audit. Its creator was an outside cybersecurity vendor, its timestamp was certified at the time, and the vendor retained the source image under its normal seven-year policy. The export shows MV-04 accepted fourteen months after its scheduled expiration.
No user or device identifier appears beside the event. The old system logged authority, not identity.
"That is a governance failure," I say. "It is not evidence of who entered the code."
Adrian studies me. I expect anger. What I see is colder and more disciplined.
"Did you ever ask whether it was revoked?"
"No."
"Did you review the 2023 audit?"
"I received its executive summary. I did not request the exception log."
"Then the board failed twice. First when it shared authority. Again when it accepted a summary that hid continued use."
He does not call me Dad. The missing word lands hard, and I accept why he withholds it.
Cal offers a folder of printed approval notices. His lawyer says he kept them at home because he feared Jonah would erase the system. That private custody is a serious weakness. The pages have no verified origin, and Cal had the opportunity to alter or select them. The investigator scans them as leads, marks them uncorroborated, and seals the originals in Cal's presence. They will not support a finding unless matched to independent logs.
One page carries MV-04 beside the supplier that sold the relabeled accessibility restraints. The transaction date is four years after the credential should have died.
I ask the investigator to place my board privileges on screen.
Adrian finally looks directly at me. "What are you doing?"
"Removing the argument that I can influence the records we now need."
I surrender access to the board portal, committee workspaces, director messaging archive, and nonpublic procurement reports for the duration of the inquiry. Only legal notices required for my fiduciary duties may reach me through independent counsel. My recusal also covers every vote concerning witness discipline, code review, or Jonah's reporting line.
The act is not absolution. It makes my ignorance more expensive. I cannot shape the company's response, read every allegation, or call allies before a hearing. The board will appoint a temporary director to my committee seats by evening.
My surrender also triggers a bylaw rule requiring an independent director to review any urgent vote I would otherwise receive. Decisions may take longer during the subsidy deadline. The company will bear that delay because speed purchased through a compromised witness would cost more.
At 9:41, I sign the surrender instrument. Outside counsel countersigns and disables my access while the recording runs. Rina verifies the change through a separate read-only status report. The investigator enters the report, signature, and disablement time into the evidence index.
Cal watches the power leave my hands. "Does that help my deal?"
"It helps the inquiry," Rina says. "Your deal depends on truth we can confirm."
The investigator asks whether he ever saw another director code on Jonah's exception notices.
Cal hesitates. His eyes move to Adrian.
"Once," he says. "During the refinancing search. Different code, same override level."
Adrian's face empties.
Cal gives the code slowly enough for the recorder to catch every character.
AV-17.
This time, the initials belong to my son.

