Chapter 120
Every Time They Opened My File
The forged consent proves only that someone had access to a version of my handwriting old enough to imitate. It cannot identify the writer. My personnel file contains that kind of sample.
"Audit access, not pen strokes," I say.
Camille Brooks convenes the review in the HR compliance room. Tessa attends because she accessed my file during the original creator selection. Diane Mercer attends as archive witness. Lena remains outside the evidence team by her own choice; the complaint belongs to her, but watching us discuss my old records would make her carry my reaction too.
Vendor account NS-Admin-4 created the participant authorization five years ago at 6:22 p.m. Hart's office holds the preserved PDF. A questioned-document examiner may later compare writing characteristics, but the form's vulnerability is imitation. Similarity cannot identify the writer, especially when a known sample may have been available.
Camille starts with my personnel-access history. Wondervale's HR platform created event logs whenever a user opened, exported, or changed a protected file. HR compliance remains custodian of the live system; the city evidence office receives a sealed export created at 8:31 this morning under trust observation. Vulnerabilities: early logs retain account and action but not every viewed page, shared administrative accounts existed, and a lawful access can still be followed by an unlawful use outside the system.
My file was opened twenty-three times during the relevant year.
Camille refuses to display the list as one uninterrupted timeline. She groups events by legal purpose first: employment administration, benefits, creator selection, litigation hold, and unexplained. Camille created the grouping during today's review; the source system did not supply it. The city therefore keeps both the raw export and her labeled working table. Its vulnerability is judgment. Calling an event explained depends on documents we may later learn were incomplete.
Two benefits accesses occur after ordinary office hours. Camille finds batch-processing notices created by the benefits team on those dates; the same accounts opened hundreds of files. Those events remain relevant to system exposure but do not single out mine. One manager access lacks a surviving review form. We flag it without forcing it into the handwriting route.
Most entries have clear purposes: benefits enrollment, payroll correction, manager review, and my application to the creator program. Three are exports. One belongs to Camille's predecessor for a legal hold. One belongs to the creator-selection committee.
The account assigned to Tessa opened the file at 9:08 a.m. and exported my application packet at 9:16.
Tessa does not wait for me to ask. "I did that."
The admission tightens my chest even though the timing makes sense.
"Why?"
"Your work sample referenced accommodations you needed in the presentation room. Selection HR gave me access to the application packet so I could schedule the interview and remove identifying medical pages before the creative panel saw it."
"Did the packet contain handwriting?"
"Your cover note was handwritten. You submitted it with the portfolio."
Diane asks where the exported packet went.
Tessa gives the full answer instead of the safest one. She downloaded it to a restricted selection folder, printed a working copy, and took the packet to the panel room. After selection, she returned the paper to HR intake and deleted the local file under the committee checklist. Three panelists could see the cover note. An administrative assistant collected the folders.
"Did you make notes on the cover letter?" I ask.
"Yes. I circled the presentation-room accommodation and wrote the room number beside it."
"Did you discuss Lena?"
"Your note said you had experience designing with your sister. I asked whether that created original-work concerns. You said her lived experience informed you but her ideas would be credited and paid if used."
The memory is precise enough to sound defensive. Tessa asks that it be treated as recollection until the panel notes are found. She does not ask me to confirm it for her.
Diane locates the selection chair's minute book. The chair created it during interviews; the creator archive holds the bound original, and Hart's officer takes a certified image. It records the accommodation and credit discussion without mentioning Lena's diagnosis or birth date. The minute book corroborates the purpose of Tessa's access. Its vulnerability is selectivity: meeting notes are summaries, not transcripts.
"Name everyone," Camille says.
Tessa does, including herself.
Her authorized access leaves the later custody chain unresolved.
I refuse the urge to convert discomfort into accusation. "What record supports the purpose?"
Camille produces the creator-selection authorization. HR created it the morning interviews opened, my signed applicant notice allowed limited review, and the committee archive retained the approval. Camille is custodian. Its vulnerability is breadth: the authorization allowed packet access but did not document which pages each person handled after printing.
Tessa's account action aligns with an authorized task. That finding does not prove she never copied the cover note. Her detailed disclosure gives us routes to test.
The print-service log survives in an old facilities archive. The printer created a job record at 9:17 under Tessa's account for one nineteen-page packet. Facilities retained monthly logs for equipment billing; Hart's office takes custody of the export. Vulnerability: the log proves pages printed, not who picked them up or what happened to them.
The intake return ledger lists nineteen pages received at 4:42 that afternoon. A selection assistant initialed the line. Diane recognizes the ledger format and requests the day's routing sheet.
"Why would executive archives have a creator-selection route?" I ask.
"They would not," Diane says. "But the assistant later moved to procurement. Old routing sheets followed staff files during the reorganization."
HR intake created the routing sheet at the start of the day and completed it by hand as packets moved. The corporate archive has custody; the city receives the original under its preservation authority. Its vulnerability is handwriting and later storage. Initials can be copied, and an archived paper may have been altered.
The sheet shows Tessa checked out the packet and HR received it back. A second line, added after return, records a quality-control copy requested by P from Jonah's office.
The ink on the second line differs from the day's other entries. Diane identifies the observation but does not date the writing. A document examiner must determine whether the addition is contemporaneous. The city seals the sheet for analysis. Visual difference alone cannot prove later alteration.
"Procurement had no role in creator selection," Camille says.
The access history contains the third export at 5:03 p.m. It came from a shared HR intake account used to scan returned applications. The export name matches my packet and names a procurement review folder as its destination.
The account identifies no person. We need assignment, route, and conduct.
Camille reconstructs the staffing roster. Jonah's assistant that month was Paige. She had authority to collect procurement conflict packets, not creator applications. Her badge record places her at HR intake from 4:51 to 5:09, but badge location cannot prove she performed the export. The routing line uses a single P, not a full name.
Another employee used the shared intake account at 4:58 for an unrelated scan. Their badge also places them in the area. Camille adds that person to the witness list without naming them to us. Protecting Paige from premature accusation requires preserving other possibilities, not pretending the strongest route does not exist.
Diane finds the next link in an archive transfer manifest. Paige's assigned workstation created the procurement folder at 5:12 with a file matching my application packet's page count. Jonah's office retained it for three years before moving it to closed storage. The city is now custodian of the manifest and recovered folder. Vulnerabilities: two assistants could access the workstation, the file itself is missing, and matching page counts do not establish identical content.
"We have enough to ask Paige," Camille says. "We do not have enough to say she copied it."
Tessa offers her personal selection notebook to the city. It contains the interview schedule and her shorthand from my panel. She created it during the selection week and retained it in her locked desk archive. The city takes custody after imaging. Its vulnerability is personal control: Tessa could have removed pages before surrender, and no independent inventory existed. The notebook shows her concern about credit and accommodation, but no birth date or copied handwriting exercise.
"This does not clear me," Tessa says.
"It gives the inquiry another thing to test," I reply.
Marisol contacts Paige through independent counsel. The inquiry offers a voluntary interview, preservation protection, and the right to refuse. It does not reveal Lena's sealed form or accuse her of forgery.
Tessa looks at me. "If Paige says I handed it to her, I will answer that."
"I know."
"You do not have to protect me because my original access was lawful."
"I am keeping the evidence from becoming a story we prefer."
Tessa's shoulders lower. Mine do too.
At 2:18, Paige's counsel replies. Paige acknowledges she made a copy of my application packet after it returned to HR. She says Jonah ordered it for a conflict review and told her the creator program might expose family relationships. She denies creating Lena's consent form and says she can identify the storage route where writing samples, participant dates, and vendor invoices were combined.
Her statement is a lead until recorded and corroborated. It also makes her a cooperating witness with direct knowledge of the copy.
Marisol proposes a protected interview the same day.
Paige refuses the time and location.
Before she speaks, she wants protection for her child.