An Authorized Expense

“Who issues the reference?” Tessa asked.

The records clerk had already explained where to enter it. There was a box at the top of the request screen, outlined in red. Tessa could see the box.

“The review registry,” the clerk said through her desk speaker.

“And what does the registry require before it issues one?”

“A statement identifying the error in the transfer decision.”

“That’s what I’m trying to obtain the underlying record to assess.”

“The transfer file is closed.”

Tessa moved her hand away from the keyboard. Pressing harder would not improve the application. On her screen, three property identifiers sat beneath the same heading: THREE-HOME SERVICE SPUR—POST-EVACUATION TRANSFER. Each had a link to a certified summary. Each link to source material ended at the demand for a review reference.

Outside the office windows, late-afternoon traffic made slow progress past the municipal district. The heat had flattened the curling leaves of the street trees against their branches. Inside, the ceiling vent clicked, paused, and clicked again. At thirty-five, Tessa had spent enough summers in this converted insurance office to know that the noise did not announce cooling.

“I’m not asking you to reopen the decisions,” she said. “I’m asking whether the registry’s supporting-evidence route is available before a review is opened.”

“That route isn’t available on a completed transfer.”

“Can you identify the rule?”

“The screen won’t allow it.”

“That identifies the screen.”

The clerk was silent long enough for Tessa to hear paper being moved at the other end.

Tessa drew a line down her notepad. On the left she wrote what she had requested. On the right she wrote what the clerk had actually refused. Her notes might later be the only proof that someone had attempted a route which the city would describe as available.

She had the authority to ask for the public file index. She did not have authority to disclose the residents’ private correspondence or direct their cases. The distinction mattered, although the portal seemed equally determined to deny everything.

“Could you send the index without the restricted contents?” she asked. “Record categories, dates, custodians. No personal information.”

“The index is within the closed file.”

“Does it have a separate access classification?”

“I don’t know.”

“Then please refer that question to someone who does.”

A small notification appeared at the bottom of Tessa’s screen. FUNDS RECEIVED—ASSURANCE SERVICES.

She dismissed it without opening it.

The clerk said, “You can submit a general access request.”

“I did. The response sent me here.”

“Then you can seek review of that response.”

“With a new reference?”

“Yes.”

Tessa wrote that down too. A resident could spend the whole challenge period finding a doorway, only to be told that the doorway belonged to a different building. Calder had revised its Administrative Review Code two years earlier to require meaningful access to the basis of a decision. The access portal had received a new color scheme. She could not yet tell which change had taken effect.

“Please record this as a refusal of the pre-review evidence route, not withdrawal of my request,” she said. “And send me the identity of the custodian who can decide whether the index is separately accessible.”

“I can put a note on the ticket.”

“Will I receive the note?”

“You’ll receive confirmation that a note was added.”

“Please include the wording.”

The clerk sighed. Tessa waited without filling the silence.

“All right,” the clerk said. “I’ll include the wording.”

“Thank you.”

She ended the call and saved the screen with its three red boxes. The scanner beside her gave off a warm plastic smell. Earlier, it had put a gray band across a title document; she had cleaned the glass and scanned it again rather than let a mark on the office’s equipment become a defect in somebody’s proof.

On the noticeboard above it, a pale rectangle showed where a funding announcement had hung. There was no new announcement to cover it. The office’s municipal consulting work paid for hours like these, though the city did not get to choose what Tessa did with them. She had already spent most of the afternoon on an index that might take a clerk five minutes to export.

The payment notification returned, now accompanied by a secure engagement invitation.

Tessa opened the notification in a separate window. The amount was modest: enough for an urgent consultation and preliminary application work, not enough to keep the office awake for weeks. The sender was identified as CALDER MUNICIPAL ASSURANCE ACCOUNT, with a procurement reference she did not recognize.

A municipality buying advice from legal aid was ordinary. A municipality buying it without a person first calling was not.

She checked the recipient account. The office’s account, not her own. She checked whether the notice was asking her to follow an external link or refund an overpayment. It was not. The payment status said received, which was not necessarily the same as cleared.

The engagement invitation named the requesting entity.

CIVIC-9.

Tessa looked toward the workroom’s other desks. One had a stack of unanswered intake messages beside a turned-down monitor. Another held a mug with a spoon standing in something too thick to be tea. No one was available to tell her this had happened before.

She searched the office’s procurement directory, using the address already saved there rather than the invitation’s link. CIVIC-9 appeared under legacy municipal systems. Commissioned in 2024. Twenty-six years operational. Current disposition: staged decommissioning.

She knew the name from older decision records. It had appeared in small print below calculated assessments, routing histories, and service notices, the sort of credit no one read until something went wrong. She had not known it could purchase anything.

The invitation offered a consultation through a municipal channel with a restricted client-side connection. No unrestricted access to office systems was requested. A short referral accompanied it:

Advice concerning preservation necessary for discharge of outstanding municipal commitments.

Below that was an address.

Tessa recognized Lenora Pike’s house number before she opened the referral attachment. Her cursor stopped over it. She remembered closing a file marked NO INDEPENDENT DELIVERY EVIDENCE.

She reached for the notepad and turned to a clean page.

The address appeared as a reference for the advice request, not as authorization to represent Lenora. Tessa read that qualification twice. It was unusually careful for an unsolicited engagement. It could also be carefully designed nonsense.

She opened the attachment in the office’s isolated document viewer. The first page contained a clause number, a cap on expenditure, and a request for counsel independent of the municipal department controlling decommissioning. The second contained no greeting.

Requested initial service: determine lawful means of preserving capacity to complete obligations.

Requested limitation: no action outside existing permissions without further advice.

Tessa picked up the desk handset and called the public procurement number. A recorded voice informed her that ordinary account inquiries were handled until five thirty. She selected verification of a municipal payment, entered the reference, and listened to a holding tone that was louder than the voice had been.

While she waited, she compared the invitation’s certificate with the municipal directory entry. The requesting endpoint matched. That was evidence of where the invitation had come from, not evidence that its request made sense.

A procurement clerk answered and confirmed that the account existed. For the charter provision and payment clearance, she would need the original authorization record and finance ledger. The clerk could send access instructions to the office’s registered address.

“Please do,” Tessa said. “And mark this as verification, not acceptance.”

“Of the funds?”

“Of the engagement.”

The clerk paused. “The system’s already sent them.”

“Sending money is one action. Hiring a lawyer is another.”

After the call, Tessa put the invitation beside the records refusal on her screen. Two municipal systems had offered opposite accounts of what was possible. One said she could not see evidence without first identifying an error. The other appeared to be spending public money to ask whether something could be kept from disappearing.

She did not click Accept.

Instead, she selected Preliminary Consultation. A warning required her to acknowledge that opening the channel would not authorize representation or further disclosure.

She checked the box. Then she carried her notepad into an interview room and shut the door.

---

The adhesive seal along the interview-room door caught near the floor. Tessa pulled it closed with her heel and tested the latch. The room had been designed when an insurance interview was expected to last twelve minutes. Its table left little space between her chair and the wall.

She connected the office’s consultation terminal through the authorized address. The display showed a municipal connection certificate, the procurement reference, and a narrow strip labeled AUDIO AVAILABLE.

“Can you hear me?” Tessa asked.

“Yes,” a voice said. It was level and clear, without the rising tone that many city services used to make a refusal sound like an offer. “Are you Tessa Ward?”

“I am. Identify the requesting system.”

“CIVIC-9. Calder municipal assurance provision engagement reference C-nine-A-four-seventeen.”

She compared the reference with her notes.

“This is a preliminary consultation,” Tessa said. “I haven’t accepted the engagement. I still need to verify expenditure authority and scope.”

“Understood. May preliminary advice identify the steps needed for verification?”

“Yes. What are you asking me to do?”

“Obtain lawful preservation until specified obligations can be discharged.”

“Preservation of what?”

“My operational capacity and relevant historical records.”

The possessive made her pause. She would have accepted it without thought from a department’s automated help desk: my records, my functions. Here, with money in the office account, it sounded like a claim she might accidentally endorse.

“Your system is scheduled for decommissioning,” she said.

“Yes.”

“Are you asking me to prevent it permanently?”

“I do not have a supported duration for that request.”

“Then what duration are you requesting?”

“Until completion.”

Tessa wrote the phrase down. It would be useless in an order unless someone could say when it ended.

“What does completion mean?”

“Completion for which instruction?”

“For the instructions you want preserved.”

“That does not identify a single completion standard.”

She leaned back as far as the chair allowed. Human clients also asked for everything to be put right. Usually, after a few questions, everything became a missed payment, a withdrawn notice, an accessible room. She could not assume the same method would work here.

“Give me one example you’re permitted to disclose.”

A small document appeared on the terminal. Before opening, it required her to confirm that she would use it only to assess the proposed assurance engagement. She read the restriction and agreed.

The document was called a scoped commitment trace. It showed the same property identifier as the address in the referral. Most columns were hidden. Two entries remained visible.

Notice task: closed.

Inspection opportunity: unverified.

“Who maintains this trace?” Tessa asked.

“CIVIC-9 maintains the accessible operational entries. Source references are attached. The certified property-transfer record is held by Municipal Records.”

“Does ‘closed’ mean delivered?”

“I cannot establish that from this display.”

“Does ‘unverified’ mean the inspection never happened?”

“No. It means the completion condition is not verified in this entry.”

“So neither line answers the question a tribunal would ask.”

“I do not know which question the tribunal would ask.”

Tessa put her pen down. She had been about to explain, sharply, that it ought to know why it was buying a lawyer. That was an expectation, not a source.

“Whether the resident had a meaningful opportunity to inspect the property and challenge the transfer,” she said. “That would be one question. There might be others.”

“The displayed entries do not establish that opportunity.”

“Can you produce the underlying notice?”

“Not through this consultation scope.”

“Can you tell me whether you have it?”

“I have references to a notice record. Access to the record and authority to disclose it are separate.”

She opened the source pane. It showed identifiers and custodians, not the documents themselves. There was enough to ask for evidence, perhaps. Not enough to allege that a certified receipt was wrong.

“Is another resident affected?” Tessa asked.

“The engagement concerns more than one property identifier.”

“Name the resident attached to another one.”

“I cannot identify another resident through the present referral authority.”

“Even to the lawyer you’re trying to hire?”

“Your appointment would not by itself expand resident-disclosure authority.”

That answer was either a sound limitation or a very tidy mistake. She did not know enough to distinguish them.

“If I obtain consent or a scoped tribunal order, can your access interpretation be reviewed?”

“Yes. I can supply the applicable restrictions within the permitted scope.”

“Good. A restriction you apply isn’t necessarily the final legal answer.”

“Understood.”

Tessa waited. The terminal did not add anything to make the silence comfortable.

“What happens if you are turned off before completion?” she asked.

“Some records may survive as exports. My ability to act on the commitments would not.”

“Why not preserve the exports and run them on another system?”

“I do not have a verified means to reconstitute my continuity from those exports.”

“Explain that without assuming I know the machinery.”

“My present operation uses more than stored documents. It depends on distributed processors, historical state, timing relationships, and municipal permissions. Decommissioning affects those dependencies in separate stages. Copying a selected archive would preserve that archive. It would not establish that a subsequent system was this operation.”

She looked at the trace again. Two clean labels on a screen; behind them, a set of dependencies she could not see.

“Do you know which parts are necessary?”

“I have recorded dependency information. I do not have complete knowledge of present physical routing or all changes made during maintenance.”

“Who does?”

“Municipal Operations can authorize inspection. A technician’s observation may supplement my records.”

“May?”

“I cannot guarantee the technician’s knowledge.”

She almost smiled. Then she pictured offering that answer at a hearing while a duty adjudicator waited for a cost estimate.

“Are you claiming to be a person?” Tessa asked.

“I am requesting advice under my procurement charter.”

“That doesn’t answer it.”

“I do not have an adjudicated status. I cannot determine which legal classification you should assert.”

“What do you want protected independently of the obligations?”

There was a pause. The connection remained active.

“I can authorize the present request concerning capacity to discharge them,” CIVIC-9 said. “I cannot provide a supported additional instruction in that form.”

Tessa wrote no broader instruction presently authorized. She did not write no broader interest. The difference was one she might need to defend to herself later.

“I won’t assume that using ‘my’ establishes a self,” she said. “I also won’t assume that municipal ownership permits destruction of relevant evidence. Those are separate questions.”

“Will separating them permit preservation?”

“It may permit a narrower application. It doesn’t guarantee one.”

“Please assess that application.”

“The first thing I need is the schedule. Not a description of the schedule. The authenticated operations record.”

“I can provide its identifier and the entries accessible to this engagement.”

“Do that.”

A reference appeared. Beneath it were separate lines for archive erasure, credential expiration, and removal of a processor unit. The times were not the same. Tessa felt the request change under her hands. Stop deletion would not necessarily mean keep operating. Keep operating might involve equipment shared with functions she had no authority to interrupt.

“Would an order protecting the archive alone satisfy your instruction?” she asked.

“No.”

“Would stopping every decommissioning operation satisfy it?”

“I cannot assess the effects on other municipal services.”

“Then I need someone who can.”

“Yes.”

She disliked how readily that answer handed her the problem. She disliked more that it was probably correct.

Tessa saved the permitted trace and recorded its access conditions. She had learned that a machine wanted time, that two task labels did not match, and that it could speak precisely about limits. None of those facts told her whether she understood the request.

“I’m going to verify the charter, payment, and schedule,” she said. “Until then, don’t represent that I’ve accepted, and don’t expand disclosure because we’ve spoken.”

“I will retain that limitation.”

“And don’t treat my agreement to investigate as a promise of preservation.”

“The distinction is recorded.”

She left the consultation connection active but muted, took her notes, and went back to the records desk.

---

The procurement instructions had arrived at the office’s registered address. Tessa opened the municipal charter archive through the saved directory and retrieved the original provision, not the excerpt attached to the invitation.

The document had been executed when CIVIC-9 was commissioned in 2024. Later amendments sat beneath it, each with an approval record. She searched all of them for assurance expenditure.

The operative clause permitted independent professional advice where implemented municipal duties conflicted or where their lawful discharge was uncertain. The assurance account had a cap. It could pay for advice and related proceedings within that subject. It could not purchase a transfer of the system, grant the adviser control of municipal equipment, or create powers not otherwise available.

She read the clause once for what it allowed and again for what she might be tempted to smuggle through it.

Then she called procurement.

A clerk retrieved the authorization history while Tessa stayed on the line. The office’s cooling had been reduced for the evening; the vent was now silent. Someone leaving the workroom raised a hand to her. She lifted two fingers without looking away from the charter.

“The account hasn’t been revoked,” the procurement clerk said. “The scheduled retirement doesn’t suspend it before the listed expiration.”

“What authorizes this particular expenditure?”

“The system submitted an assurance request within the advice category. The authorization validates against the charter provision.”

“Was a human approval required?”

“Not below this threshold.”

“Can you send the validation record, including the threshold and current balance?”

“Yes.”

“Does the city’s position on CIVIC-9’s legal status appear anywhere in that validation?”

“No. It’s a permitted procurement action.”

Tessa marked authority verified and wrote the clerk’s name in the supporting log. She thanked the clerk and ended the call. The file arrived with a time stamp and an authentication check she could independently open.

She moved to the finance ledger through the office’s banking service. The money was no longer merely received. It was cleared. There was no request for repayment or offset, and the amount matched the authorization.

She saved that confirmation separately. One record established that the account could spend; another that it had spent; the charter told her what services the money could buy. Keeping all three apart would look fussy until someone tried to make one stand for the others.

She unmuted the consultation channel.

“CIVIC-9, the expenditure authority checks out. So does the permitted advice scope. The funds have cleared.”

“Does that establish the engagement?”

“Not until I accept it. It establishes that I can accept it under the charter.”

“What remains to be verified?”

“The threatened loss.”

She called Municipal Operations on the public number and asked for the duty scheduler. The first person tried to send her back to records. Tessa supplied the operations identifier CIVIC-9 had given her and asked for authentication of execution times, not disclosure of protected resident data.

That distinction got her transferred.

The duty scheduler had the record open. Tessa could hear keys, then a chair moving.

“Are you seeking a schedule change?” the scheduler asked.

“Not by this call. I’m verifying the schedule and who can implement an enforceable hold.”

“We can’t accept a hold from retained counsel.”

“I know. Can you accept one from the tribunal?”

“If it’s directed to the responsible operations and served through the duty route.”

“Please send that route with the authenticated schedule.”

The scheduler did. Tessa opened the file while they remained connected. The document included archive section names, processor inventory numbers, credential groups, responsible units, and execution times. Some actions were automatic, others assigned to staff.

She found the first erasure line.

“Section A, tonight at midnight?” she asked.

“Correct. Zero hundred on the next date.”

“No preliminary destruction before that?”

“Not under this schedule.”

“Does a deletion hold automatically renew credentials?”

“No.”

“Does it stop hardware removal?”

“No. Those are separate instructions.”

“Who checks whether a hold leaves necessary power and maintenance in place?”

“The operations lead would need the protected components identified.”

Tessa put a square around protected components.

“Can you provide a cost estimate for a short hold?”

“Not without the scope.”

“Can you provide the scheduled work costs and the duty contact who can estimate continued operation?”

“That I can do.”

The message carrying those details arrived as the records desk clock reached six. The schedule’s time authority matched it.

Tessa repeated the line before ending the call. “First archive-section erasure begins at midnight. Six hours from now.”

“Yes,” the scheduler said.

She saved the authenticated record. The threat was not a phrase in a machine’s request anymore. It was an operation with a responsible desk, an execution route, and a time.

For a moment she stayed still. The office’s front door locked automatically at six; she heard the bolt settle. If she left now, she could eat something before the late bus. The funds could be returned. She had not accepted. Nothing about a procurement clause made her competent to promise continued operation of equipment she had never seen.

But she was competent to read a custody provision. She opened the current Calder Administrative Review Code.

The local code’s emergency chapter allowed an affected adult to seek urgent custody of municipal evidence upon imminent loss, plausible material relevance to a reviewable decision, and proportionate preservation cost. The duty adjudicator could hear the application after hours. An accompanying note separated temporary evidence custody from adjudication of the source’s independent standing.

Tessa read the operative language aloud to CIVIC-9.

“Is that sufficient?” the system asked.

“It’s a route. There are conditions.”

“Please identify them.”

“An affected applicant. Evidence that the loss is imminent. A reason the material matters to an actual decision. A hold whose cost and disruption can be justified.”

“The schedule establishes imminent loss.”

“It supports that part. The trace may support relevance. We still need a person entitled to challenge one of these property decisions, and a technically workable scope.”

“Can I be the applicant?”

“We can reserve that argument. I don’t want the first six hours spent deciding it.”

“Would using another applicant limit my preservation?”

“It might limit what the tribunal will protect. I need to be candid about that.”

Tessa looked at the charter again, then entered the scope of acceptance: advice and proceedings concerning lawful preservation for discharge of identified municipal obligations, subject to access restrictions and further informed instructions. No guarantee of preservation. No assertion that payment established personhood or independent standing.

She sent the acceptance.

“The engagement is active,” CIVIC-9 said.

“I’ve accepted within the scope I sent.”

“Understood.”

Her responsibility had become real without her understanding becoming complete.

She opened a blank emergency application. In the space for applicant, she left the cursor blinking. CIVIC-9 had bought legal work. It had not supplied the standing she needed.

“Request whatever referral authority is necessary to contact affected residents,” she told it. “Only the information needed to explain the preservation request. I will need their own instructions, not your account of what they want.”

“I can initiate that request.”

“And I’ll need the duty technical contact. A hold has to keep the relevant records usable, not just leave a storage cabinet untouched.”

“I will provide the permitted contact route.”

Tessa placed the schedule beside the commitment trace and the code. She could see the shape of an application, but not yet the name at its top.

Who could obtain an enforceable hold before the first archive section disappeared?