The Account With My Name

My name earns me the same scrutiny Simon received.

At 9:19, I sign a voluntary device-surrender receipt. The independent examiner takes custody of my company laptop, phone, hardware key, and office tablet. The receipt records serial numbers, condition, time, and each person present. My personal phone stays outside the initial scope until counsel defines what work data, if any, can be collected without exposing unrelated private communications.

"Suspend every active session," I tell Nico.

He looks to committee counsel rather than obeying me. My emergency authority does not make me the forensic custodian of my own account.

Counsel approves. Vale technology terminates the sessions at 9:24 and preserves the authentication logs before disabling access. The system creates the revocation record. The independent committee receives a copy. Its vulnerability is coverage: a session on an unknown device or a copied file outside Vale systems may not appear.

I draft the employee notice from a clean terminal with counsel watching. It states that an executive credential associated with me uploaded a forecast containing protected workforce data. The notice identifies the user as unknown and lists the immediate actions: my devices surrendered, sessions suspended, affected employees receiving separate protected notice, and independent forensics underway.

I include that I will have no system access while the review proceeds.

Camille removes one sentence before release. I wrote that no employee data would be used against anyone. She changes it to a specific instruction: attendance, badge, mentorship, and forecast data from the package may not be used in employment decisions, and attempted use must be reported to her protected channel.

"A promise is not a control," she says.

Camille's correction gives employees an enforceable instruction.

Committee counsel creates the final file at 9:37. The staff communication archive is custodian, and the employee trust receives it simultaneously. The notice cannot prove my innocence or predict the review result. It proves what management disclosed and prohibited before the investigation concluded.

At 9:40, it reaches every employee account and the posted break-room system.

Only then do we examine where I was.

The upload occurred during the weekend Mira and I spent at her family home. We arrived Friday evening and did not return to the park until Sunday afternoon. I remember the Saturday hour because Lena had gone to bed, Mira was revising a community-studio access plan, and I was losing an argument with a dishwasher that considered every plate a structural threat.

Memory is not a custody log.

Mira can confirm I was with her. Her testimony would establish what she observed, not what my account or any unattended device did elsewhere. Using our private weekend as my first defense would also turn her into an alibi before the system evidence has been tested.

"I believe you did not send it," she says.

She continues, and the words strike harder.

"I also want the complete review. Every device, recovery path, delegation, and exception. My belief cannot close an evidence question."

"It won't."

"And we disclose that I was with you only through counsel, with the narrowest time and no private messages unless an independent reviewer finds them necessary."

"Agreed."

She trusts me and still requires an independent review. Three months ago, I might have heard that demand as a failure of love. Today I understand that the review keeps love from becoming concealment.

Nico starts with my hardware key. The examiner's log shows its serial number was paired to my laptop during the relevant period. Device telemetry places that laptop offline from Friday evening until Monday morning. The source is Vale's management server, which records the last corporate connection. It cannot prove the laptop stayed unused while offline or that the key was never copied.

My phone connected to the cellular network near Mira's neighborhood. The carrier retains connection records, not a continuous map or proof of possession. Counsel preserves the narrow location window without opening personal content.

The uploaded package does not appear on either device's current file index. Deletion remains possible. So does a remote session.

"The room log shows password authentication followed by an administrative recovery approval," Nico says.

"My hardware key was not used?"

"The recovery approval bypassed it."

He displays the raw authentication event. My username entered at 11:41, and the password challenge passed. Seven seconds later, an administrative token approved recovery from a device registered as a board-services terminal. The session uploaded the package at 11:48 and ended at 11:51.

The historical terminal label belongs to a physical device retired two years ago, and its name may have been reassigned or copied into a virtual session. A token approved the bypass, according to the event record. It does not identify the operator or the machine's actual location.

"Which token?" Camille asks.

Nico reads the identifier. Camille leaves the room without answering.

She returns with the access recertification archive she assembled during Malcolm's signature review. The archive contains board-administration accounts, retirement notices, exception approvals, and migration logs. Independent technology counsel collected it under seal. Camille has review access because recovery credentials intersect with personnel separations.

The token identifier belongs to Diane Mercer's old administrative recovery account.

Diane retired from daily executive administration but continued serving on the committee and helping with historical records. Her ordinary staff account was reduced. The recovery token should have expired during the board-system migration.

The credential survived.

Camille traces the exception. Technology created a migration list eighteen months ago. A board-services manager marked Diane's recovery credential retain for legacy archive continuity. The system preserved the token without a new expiration date. The manager's account approved the exception; the record does not show who requested it or whether Diane knew it remained active.

"Was it used in Malcolm's disputed signature?" I ask.

Nico compares identifiers. The old event recorded approval through Diane's account but did not preserve the token suffix. The systems are consistent with the same recovery path, but the missing identifier prevents a match.

Camille records that as unresolved.

The current event is stronger. The token suffix matches Diane's retained credential. Its use created a recovery session under my account. Neither fact makes Diane the operator.

We call her through committee counsel. Before Diane joins, Camille states the limits: we will ask about the token's creation, custody, and known access. We will not tell her whose accounts appear elsewhere until the examiner determines what disclosure is necessary. Her answers will be preserved, and she may have counsel present.

Diane asks for counsel.

That choice delays the interview and protects the record from becoming an ambush.

At 10:46, the committee issues a formal suspension of my remaining system access. I retain no email, portal, shared-drive, approval, or emergency console login. Dev keeps delegated safety authority. Camille keeps protected personnel authority. The employee trust and city observer receive the access order.

The order is irreversible until an independent forensic finding permits restoration. My contract authority was already frozen. Now even the duties I retain must travel through the written delegates instead of my screen.

Mira reads the order beside me. She does not tell me the loss is temporary.

"Who do you lead without an account?" she asks.

"The people who are free to refuse me."

"Then start there."

We keep board communication public and refrain from blaming Diane. Nico preserves the token logs. Camille begins an inventory of every legacy credential. I leave my office badge with the examiner and wait in the committee room for Diane's interview.

She arrives at 11:22 with counsel, studies the token identifier, and confirms she created the recovery credential during Owen Vale's last year of active leadership. She believed it had expired after the migration. The written record supports the intended expiration and contradicts the actual system state.

Counsel asks who knew the token existed.

Diane looks at me across the table.

"Only one other person knew," she says.