The Applicants Who Never Worked

The benefits administrator created the recovered premium tables during each monthly billing cycle and exported them through the employee portal this week. Counsel holds the worker-authorized copies; the administrator retains source records under the court order. Their vulnerability is context. The tables show premiums posted to an employee category, but they do not establish who funded the payment, received the benefit, or controlled the account.

Nico lines the payment dates against vendor invoices. Both ghost IDs appear during months when consulting payments to Hollis and the creator platform increased. Timing gives us a question, not a route.

"Application archive," Paige says from the screen.

Her lawyer asks her to explain why.

"Jonah's office kept rejected applicants in a reserve staffing pool. Names, birth dates, contact details, prior employers. Some files included benefit eligibility questions."

June grips the back of the empty chair in front of her. "Applicants were told their records would be kept for future openings."

"That is what recruiting said."

"Who could access the pool?"

Paige names procurement workforce planning, recruiting operations, and Jonah's executive support team during seasonal hiring. She says she used the pool to build staffing projections. Her testimony can identify practices she saw. It cannot prove who opened a specific application or created a ghost benefits record.

Camille authorizes a limited comparison through the independent privacy examiner. Wondervale does not receive the rejected applicants' identities. The examiner will compare hashed identifiers derived from name, birth date, and application number, then return potential matches to victim counsel.

The examiner creates the comparison protocol at 7:41. Marisol's privacy counsel reviews it at 7:56, and the court monitor approves it at 8:09. The examiner keeps the application archive in its existing sealed environment and holds the match key. We receive coded results only. Its vulnerability is false matching. Shared names, data-entry errors, and changed identifiers can connect the wrong person unless counsel verifies against original records.

At 8:32, the first two coded results appear.

Both ghost IDs match rejected applications.

One applicant sought a costume-shop job and withdrew after accepting work elsewhere. The other applied for maintenance and failed a required certification screen. Recruiting records show neither person became an employee.

June asks whether either applicant consented to benefits enrollment.

The archive contains ordinary application consent for recruiting and retention. It contains no benefits authorization. Missing consent in this archive does not prove none exists elsewhere, so counsel requests the source enrollment forms from the benefits administrator.

At 9:14, the administrator produces two forms. Both carry typed names, electronic acknowledgments, and Wondervale department codes. Their creation logs show enrollment through a batch interface, not the public employee portal. The administrator holds the source forms and access logs; the court receives certified copies. The forms' vulnerability is identity. A typed name and checked acknowledgment do not establish that the applicant completed the enrollment.

The batch interface used a vendor credential assigned to workforce planning.

"Jonah," June says.

"His office," I correct. "The credential was shared across an approved service team."

Disgust moves across her face without weakening her attention. "Then every person with access belongs on the preservation list."

Paige asks to see the credential label through her lawyer. When it appears, she closes her eyes for a second.

"Reserve staffing," she says. "That was the account name Jonah used."

"Did you use it?" her lawyer asks.

"For staffing forecasts and vendor head-count files. I never enrolled anyone in benefits."

"Could someone else use the same credential?"

"Yes. Three assistants had the password at different times. Procurement technology also serviced it."

Her answer increases the number of possible actors instead of giving the room one person to blame.

Nico studies the payment schedule. "If an account creates a fake active employee, the administrator bills a premium. Where does the payment go?"

Wondervale pays the administrator from the protected benefits reserve. The administrator sends carrier amounts onward and pays contracted service fees. The ghost entries include an additional reconciliation fee routed to a workforce-continuity vendor.

That vendor shares a payment address with one of the consulting entities already connected to J.P. invoices.

Nico traces the bank and contract records already in public or city custody. The address link supports common administration. It does not prove common ownership, much less identify who received the final funds.

"The ghost IDs may create billable head count," he says. "Premiums and reconciliation charges could move money through ordinary benefits payments. We need bank destinations and carrier confirmations before we call it a cash channel."

Every step resembles a normal expense, which is what makes the method ugly.

The examiner expands the comparison to all ghost IDs found in the consented files. Counsel contacts workers before using additional exports. By noon, there are fourteen ghost entries. Nine produce likely matches to rejected applicants. Two match former contractors whose assignments ended before the premium dates. Three remain unmatched.

We notify potential victims before any public filing.

Marisol's office creates the notice at 11:28 with plain descriptions of the match, the records reviewed, the uncertainty, and available rights. Independent counsel sends each notice through contact information verified outside the compromised application system. The legal panel holds delivery records; Wondervale receives aggregate counts only. A delivery receipt cannot prove the right person opened the notice, so counsel confirms identity before discussing details.

The employee trust funds separate lawyers, credit monitoring, identity-document replacement, and benefit-record correction. Assistance does not require cooperation with investigators or permission to use a person's story.

One applicant hangs up after hearing Wondervale's name. Another asks whether a four-year-old rejection can affect her current insurance. A third wants every copy of his disability disclosure destroyed before he will speak to anyone.

Counsel gives each person a choice about notice to current insurers, law enforcement contact, and use of the application in the case. Two request correction without an interview. One wants a prosecutor present before anyone opens his original file. The panel records those limits in separate client files that Wondervale cannot access. A lawyer's confirmation tells us representation exists; it reveals nothing about whether the client will cooperate.

June asks recruiting to suspend automated rejection messages while the archive is examined. Applicants currently seeking work should not receive unexplained delays or a false promise that the investigation cannot affect them. Camille approves a plain notice stating that hiring may take longer because old data access is under review. It names no victim and makes no claim that the current hiring system was compromised.

June leaves the evidence room to call recruiting staff. She returns with a proposal that freezes all nonessential access to rejected applications, preserves the archive with an outside custodian, and gives applicants a direct deletion or limitation request subject to legal holds.

"Recruiting will say they need a future-candidate pool," Paige says.

"They can ask people again," June replies. "A possible future job is not permanent permission."

Camille and the caretaker council adopt the freeze at 1:22. Active hiring continues through a clean system with new consent. The old pool remains sealed for victim notice and the criminal inquiry. The order may slow seasonal recruitment, a cost the council records instead of hiding.

At 2:10, the court monitor authorizes a larger comparison using payroll IDs, vendor billing dates, and the sealed application archive. The examiner creates a match report with coded rows and confidence levels. Prosecutors, victim counsel, and the court receive separate versions based on their authority. The report can identify overlapping records. It cannot establish who copied the data or why the benefits administrator opened each account.

Nico and I work through the coded rows. Rejected applicants cluster around months when the reserve-staffing account submitted batch enrollments. Former contractors cluster around contract-renewal weeks. The unmatched IDs carry older hire dates and Vale executive cost centers.

"Could those be family coverage accounts?" June asks.

"Possibly. Or historical test records that were never removed."

We request the source enrollment file for the first unmatched ID.

The administrator sends the redacted header. The employee category says executive. Premiums continued for thirty-one months after the listed status changed to inactive. The identity field is sealed until victim counsel confirms whether the person is living and can be notified.

At 3:04, estate counsel joins the protected line.

The examiner releases the name under the court protocol.

The ghost ID belongs to Owen Vale.