The People Who Never Billed

"The live system is isolated anyway," I reply. "Use city-preserved exports. State what each one can prove."

The first export came from Wondervale's vendor directory at 6:20 on the night networks were isolated. Camille Brooks's records team created it under city observation. Hart's office is custodian of the sealed file; Nico has a read-only copy under his written mandate. Its vulnerability is historical depth. The export shows current and retained vendor profiles, but a deleted record may survive only in backups.

Nico also has a personnel crosswalk created by the city from vendor tax records and access rosters. The city created it at 7:11 this morning and retains custody; vendor names are visible while personal tax numbers remain masked. Its vulnerability is employment status. A person may appear because a vendor proposed, onboarded, or paid them, and the crosswalk does not prove they performed Wondervale work.

We test Joseph Pike first. His name appears in an old contractor liaison roster created two years before his death, with a legitimate worker ID that begins MCTR, not CPRT. The roster makes it less likely the ghost code was his normal identifier. It cannot rule out a second category created in his name.

"Search for repeated dates after separation or death," Nico says.

I stop him before he runs the query. "Define the purpose and fields. We are looking for identity reuse, not creating a list of dead or disabled people for another team to browse."

Lena sets the minimum comparison: participant code, claimed service date, vendor, invoice amount, and whether a verified record places the person in the program. Names stay with each source custodian unless a match requires counsel review.

The query finds CPRT attached to forty-seven people across six vendors as a classification rather than an employer.

Nico reads the label aloud. "Community participant, reimbursable testing."

Lena turns from the screen. "Those are not vendor personnel."

The distinction redirects our request to the independent design lab's community-payment index. Wondervale's participant files remain closed. Lena states her conflict before opening anything: her organizations may have referred testers, and her own community records are part of the comparison. She will describe the system but will not decide whether a match is genuine.

The lab board created its combined payment index when participating groups transferred governance outside Wondervale. Each group supplied a signed export and retained its source records. The city grant office holds the combined index; the groups remain custodians of originals. Vulnerabilities: the transfer covers groups that consented, older programs have gaps, and absence from the index cannot prove a person never participated privately.

None of the CPRT ledger numbers matches a paid participant in the combined index.

"Check format, not identity," Lena says. "Our current codes begin with the program and end with a random participant key. CPRT looks like an accounting category pretending to be a person."

Eli has been silent since we started. He asks Nico to show the vendor personnel rows surrounding one CPRT entry. On either side are staffing records from Meridian Talent Services, his former petitioner. He recognizes the field order.

"Meridian used this for ghost participants," he says.

The phrase is sharp enough to become an accusation, so I make him define it.

"During mentorship vendor demonstrations, the billing screen required a participant ID before a consulting invoice could close. If the community tester had not been entered, coordinators used a temporary participant category. The record was supposed to be corrected before payment."

"Who taught you that?"

"A project coordinator during onboarding. I entered two temporary codes myself."

"Do you have a record you lawfully hold?"

Eli searches the files transferred under his counsel-approved exit protocol. He finds a training guide attached to his Meridian onboarding packet. Meridian's learning team created it eleven months ago at 4:12 p.m.; Eli received it as an assigned employee and retained it in his protected transfer archive. The employee legal trust is custodian of the preserved copy. Its vulnerabilities are timing and scope: the guide postdates Pike's entries and describes Meridian's process, not every vendor's.

Page fourteen defines CPRT-TEMP as temporary community participant, replace before invoice approval.

The ledger drops the word TEMP. The numerical pattern remains.

"That establishes only a billing category," I say. "Whether these entries are false remains open."

Eli shows us how a legitimate correction should look. His training guide requires the temporary code to be linked to a participant record, replaced before approval, and preserved in an audit table. The city searches its retained vendor exports for that table. Meridian produced one in the mentorship system, but the five ledger codes never appear there.

"Could another vendor hold the correction?" Lena asks.

"Yes," Eli says. "Or someone could have approved the invoice without correcting it. The missing table tells us where to request. It does not choose between those possibilities."

Nico requests invoice headers associated with the ledger dates and amounts. The city procurement archive contains five. Wondervale Accounts Payable created each payment record when a vendor submitted an invoice. Hart's office took custody during the five-year procurement expansion. Vulnerabilities: the payment system preserves approving accounts and attached descriptions, while attachments may have been removed before preservation and accounts do not identify human operators.

All five invoices charge community accessibility consultation. Two name Joseph Pike as employee representative. Three list only J.P.. The vendor recipients are Northstar, Meridian, and a consulting company linked to Open Lantern.

The amounts total thirty-eight thousand dollars.

Nico follows the payment endpoints without opening unrelated vendor accounts. Accounts Payable created the transfer confirmations on each settlement date, and the city bank-subpoena team holds them. Four payments reach ordinary vendor operating accounts. Payment five moves from Northstar to an Open Lantern consulting account two days later. Suspicious timing cannot prove the funds are identical because the account held other money.

Its follow-on transfer uses memo code CPRT-14, matching the ledger entry tied to Pike after his death. That gives the inquiry a transaction route independent of initials.

Lena reads the service descriptions: small-group mobility review, sensory-access consultation, and family consent coordination. Her network either performs that work or pays disabled testers to perform it. None appears in community records.

"They invented people to bill for our labor," she says.

Lena turns her anger into a request. She asks the six community groups to search their source ledgers by date, amount, vendor, and service description, without disclosing participant names to Wondervale. Each group appoints its own reviewer. The city provides a neutral comparison table.

Three groups respond before noon. One had no program on the listed date. Another ran a sensory workshop but paid its participants directly and never used Northstar. The third recognizes language copied from an old grant proposal, including a typo in the phrase quiet queue transition.

A fourth group finds a legitimate consulting session on one invoice date. Its director refuses to clear the vendor invoice merely because the date aligns. Her organization paid six named participants from its own grant and billed Wondervale a different amount. She transfers the signed attendance and payment summary directly to Hart's comparison officer. The group remains custodian of names; the city receives totals and consent status. Vulnerability: attendance proves that session happened, while it cannot show whether Northstar provided a separate service the same day.

The distinction matters. A real workshop may have been used as cover for an additional invented one.

The community coalition created that proposal six years ago and submitted it to Wondervale for an unfunded pilot. Open Path Families now holds the transferred original; the city has a grant-archive copy. Its vulnerability is circulation. Wondervale received the proposal lawfully, and many employees could have reused its language without proving who created the invoice.

We have enough to expand the case without claiming we know the author. Dead-person identifiers, temporary-participant codes, invoices lacking community matches, and copied service language form a pattern across vendors.

Marisol files an amended complaint for false community-consulting invoices. She identifies the evidence, the gaps, and every group whose records must remain community-controlled. At 12:46, the employee trust and four participating organizations sign the filing and deposit it with Hart's office. Its vulnerability is incomplete membership: groups outside the coalition may still establish legitimate services.

Hart approves preservation notices for all CPRT-linked invoices and source attachments. The inquiry now protects community consultants as potential victims, not decorative witnesses to a company fraud.

Nico runs one final comparison against the participant index's non-identifying fields. We use dates, program codes, and uniqueness checks, not names. Most ghost rows carry plausible adult birth years and random days. One record repeats a date already stored in an old accessibility contact form.

Lena sees it before I do.

"That date is mine," she says.

The code does not contain her name. A birth date cannot establish identity by itself.

It matches Lena Damien's day, month, and year exactly.