The compliance request form has seventeen fields, six of which are required. Lydia fills in all seventeen.
Business justification allows two hundred words. She uses forty-eight. Quality assurance review of property risk assessments in Phoenix metro region. Reviewing recent D-42 (property risk) denial codes for pattern consistency with stated criteria. Requesting access to decision parameter documentation for UnderwRite Pro 4.0's property risk module, specifically variables contributing to property risk scores in Maricopa County assessments, Q4 2027 through Q1 2028. Professional, contained, the kind of language that lives in a compliance queue without alarming anyone — a processor doing due diligence, nothing unusual. She spends fifteen minutes on the wording. Too technical and it looks like model auditing. Too vague and they'll ask for clarification. She submits it on a Tuesday morning between applications twenty-eight and twenty-nine, the processing center's air conditioning set at its usual sixty-eight degrees, her cardigan on the seatback where it's been since March.
Three days later, the automated acknowledgment: her request has been received and forwarded to the vendor for technical documentation, per standard operating procedure under the Technology Transparency Policy adopted January 2028. Response timeline: sixty to ninety business days. Additional delays may apply based on vendor capacity.
She does the math. Sixty business days is twelve weeks. Ninety is eighteen. The most optimistic scenario puts documentation in mid-July; the realistic one runs into August. It is mid-April. She reads the email a second time looking for an expedite option, a direct contact, anything outside the automated process. There isn't one. The system has a channel for questions like hers, and the channel has a calendar that doesn't answer to her. She closes the email and opens her queue. Twenty-eight applications pending.
Ray appears at her desk at 2:17 on a Friday, but not the way he usually does. She's seen him check in on processors a hundred times — standing at the cubicle wall, tablet in one hand, scanning output before the conversation starts, already positioned to leave. Today he pulls the chair from the adjacent hotdesk and sits down. Sets his tablet face-down on the desk edge.
"Compliance called me," he says. Not the automated notification — a person called. About the documentation request. "They want context before they route it. Is there a specific case with an issue?"
She's had the answer ready since Thursday. "I noticed some inconsistencies in D-42 coding. A few denials in the Maricopa queue where the property risk flag didn't match documented risk indicators. Clean LTV, clean title, comparables that support the listed value. Nothing flagging on the property side."
"Did you run QA on them?"
"QA flags came back clear."
"Then the system weighed inputs we don't have documentation for." He says it without impatience — it's operational logic, not a rebuke. "That's what UnderwRite does. We process the file. The system scores. Our access layer doesn't cover every variable."
"I know that. I wanted to understand which variables were producing the flag."
Ray taps the desk edge once. "That's what compliance flagged. You didn't submit a QA inquiry. You requested training data access and decision parameter documentation." He looks at her steadily. "That's a model audit request. Different process." He pauses. "If a specific case needs review, document it through the override request form. Compliance's job is the system. Your job is the queue."
"I understand the distinction." "I know you do." He reaches for the tablet, already rising. "Thirty-seven percent throughput so far this month. You were at forty-two same point last quarter." Not a warning — a figure, delivered in the same register as all his figures. "The request is logged. Compliance will be in touch. Let them do their job." He's back at his desk in twelve steps, and he doesn't look back.
The stegosaurus is on the kitchen table when Lydia sits down after dinner. Amara left it there at breakfast — orange plastic, tilted slightly to the right between the fruit bowl and David's coffee mug. Lydia moves it to the windowsill and opens her laptop. David comes in drying his hands on a dish towel; he looks at the screen, then at her.
"Walk me through it," he says. He sits down across from her. "The whole thing."
She's told him pieces over six weeks — the Hernandez denial, the accumulating cases, the school district pattern — each time in fragments before picking up Amara or before his calls. Now she lays out the full shape: twenty-three denials, eight clustered along school district boundary lines, applicants with children in enrollment-age ranges, properties clean on every factor she can document. The pattern holding across four analyses.
David listens the way he listens to job site problems — following causality, not expression. When she finishes, he turns his coffee mug once.
"You need the decision parameters or you need outcome data," he says. "You can't get the parameters for another three months." "At minimum," she says. "So outcomes." He sets the mug flat. "What would outcome data actually tell you?"
"Whether the property risk materialized. Whether these homes declined in value, had title problems, flooding, something that justified the code after the fact. If the outcomes don't match the risk category, the code wasn't about property risk."
"And you'd get that from the families." "That's the only source I have," she says. He's quiet for a moment. "Going through an archived spreadsheet is one kind of work," he says. "Contacting applicants outside any official process is another kind. You'd be doing that as yourself. Not as HomeFirst, not in any capacity that protects you if someone asks questions."
"I know what it is," she says. "I know you know." He looks at her across the kitchen table, the stegosaurus gone from between them. "I'm not saying stop. I'm saying be clear about what you're doing before you do it."
The house settles after eleven. David is asleep — she'd stood in the bedroom doorway until she heard his breathing even out. Amara's monitor shows steady green. The A/C runs its cycle and clicks off. She opens the laptop at the desk in the corner and pulls up the spreadsheet.
Twenty-three rows. The last two added last week, going back through archived files in sessions the access logs would record as extended after-hours activity. She's thought about those logs. She's gone back anyway.
She could stop here. The argument for stopping has accumulated along with the rows: compliance has her request, Ray is watching her throughput, and nothing she's doing falls inside her job description. She processes applications. The AI issues verdicts. When the verdict produces a question, the question routes through a process with a sixty-to-ninety-business-day calendar. Individual processors don't evaluate model-level decisions. She knows this — has known it for two years, has defended the logic to herself in the months when the AI's decisions felt arbitrary and she processed them anyway because the framework existed for reasons and the people who built it had methodology she doesn't have.
She's run these twenty-three rows four ways. The school district cluster holds across all four. Eight cases out of twenty-three — a small sample, and she's been careful not to overclaim it. She's checked base rates, controlled for neighborhood median income, looked for simpler explanations. The pattern doesn't dissolve. Eight denials, same boundary zone, applicants with children in relevant age ranges, properties clean on every factor she can document.
The pattern is real. She didn't imagine it.
In these twenty-three rows are families who received a letter and adjusted accordingly. Different neighborhoods. Different schools. The decision came through and their lives followed — without drama, practically, the shape of what was possible contracting quietly around a door that hadn't opened. Most of them probably didn't appeal. The research says most people don't. They apply elsewhere, or they stay where they are, or they wait, and the distance between what they'd planned and where they ended up doesn't belong to anyone's case file.
She searches public records: Arizona professional licensing database, Maricopa County address registry. Eleven Elena Hernandezes in the county. She cross-references the listed employer on the application's income documentation — hospital administration, credentials renewed January 2028 — against the licensing database and gets one match. South Phoenix address, consistent with the zip code on the original application.
She opens a draft email. Three sentences: her name, the company, the application date, a request for a few minutes of Elena Hernandez's time. She reads it twice. An email from a mortgage processor asking questions about a denial letter is either alarming or forgettable, and forgettable means ignored — and she doesn't want to be ignored.
She closes the draft and saves the address to her phone under a note she labels Sat AM. Tomorrow is Saturday. She hasn't worked out what she'll say when she gets there — how to explain that she's not acting in any official capacity, that she found this address through public records on her own time, that she has a spreadsheet with twenty-three rows and one of them is the Hernandez family and she can't make the cluster disappear. She'll work that out on the drive.
She closes the spreadsheet, and the screen goes to the HomeFirst portal — queue counter at zero, all applications current, status bar reading clean across every column. Work finished, everything processed, the dashboard reflecting nothing unusual. She closes the laptop. The stegosaurus is still on the windowsill. She leaves it there and goes to bed.