An Administrative Matter

Celeste kept two calendars because trusting one system to behave like it had sense was how people ruined their mornings.

The first lived on her monitor, color-coded and capable of issuing reminders she ignored with professional consistency. The second was printed, annotated, and currently spread across the left side of her desk beneath a yellow highlighter with a chewed, flattened cap. She trusted the printed one more. It couldn’t update itself into nonsense while she was looking away.

Her office desk was L-shaped, which theoretically gave her room to separate teaching from research. In practice, it meant she had two organized disasters instead of one. The longer side held her monitors, keyboard, tablet, and the open backend interface for Lattice. The shorter side was stacked with student work, marked-up lecture notes, and a printed class schedule dense with arrows, boxes, and increasingly irritated handwriting.

At the top of the schedule, underlined twice, was PHYS 101: Introduction to Physical Science. Below that, in a tighter block with significantly more revisions, was CS/PHYS 342: Computational Systems Lab. The first required her to explain basic scientific principles to students who would rather be anywhere else. The second required her to prevent ambitious juniors from setting computational tools loose on problems they didn’t fully understand.

She was currently doing both jobs badly at once.

With one hand, she highlighted the revised due date for a PHYS 101 lab reflection. With the other, she leaned toward the center monitor and frowned at a cluster of values updating in neat vertical columns.

To anyone passing her office, Lattice might have looked like a glorified series of databases: windows full of fields, identifiers, linked records, timestamps, and control panels buried beneath nested menus.

That assumption was wrong in the way a child’s diagram of an engine was wrong. It bore a passing resemblance to the thing itself, but none of the important parts were visible.

Lattice was not a database. It wasn’t even a collection of databases, though it interacted with enough of them to create the illusion. Its real work happened in how it interpreted, connected, weighted, and restructured information across systems that had never been designed to speak the same language. The backend interface exposed only enough of that structure for maintenance, calibration, and the sort of careful intervention that tended to alarm everyone outside the project.

Celeste selected a parameter window and compared it against the diagnostics pane beside it.

“No,” she muttered.

She opened a second pane. “No.”

She exhaled, leaning another inch toward the monitor, as though proximity might persuade the computer to cooperate. A third pane opened.

“There you are.”

She straightened, one foot tapping lightly beneath the desk. The values in one subsystem were climbing. Not dramatically, but enough to produce a discrepancy elsewhere. Two linked processes were reading the same priority set differently, which explained the reporting lag she’d spent most of the morning chasing.

It was the sort of issue that made everyone else call the system unstable and made Celeste insist that the system was being misunderstood.

She adjusted one setting, watched the dependent values settle, and opened another window to confirm the change had propagated correctly. On the far-left monitor, her email chimed.

She ignored it.

Then it chimed again.

Only two kinds of people emailed her twice in under a minute: students in distress and colleagues who had broken something.

She clicked over.

From: Savannah — Systems Support

Subject: Status?

Did you ever figure out what was causing the sync delay? Administration wants an answer before three.

Celeste exhaled through her nose and typed back without ceremony.

Found the source. It’s one of the Lattice weighting settings, not the records themselves. I’m verifying the fix now. Don’t let anyone push changes until I get back to you.

She considered adding especially not Anderson, decided against creating written evidence of that particular opinion, and sent the email.

Then she reopened the diagnostics and traced the modified process through its next cycle. For a moment, everything behaved exactly as it should. The values normalized. The lag cleared. One of the mirrored monitoring panes updated with satisfying precision.

Celeste sat back a fraction. “Good,” she said, to the machine and to herself.

The overhead lights flickered.

She looked up. Once, twice, then a harsh white blink made the room seem to stutter around her.

The diagnostics window changed before she fully registered why. A yellow status icon appeared in the corner of the center monitor. Then orange. Then red.

THERMAL ALERT: NODE CLUSTER 3

Temperature threshold exceeded

Escalation rate: CRITICAL

Celeste was moving before the numbers finished loading.

She shoved back her chair, snatched the tablet from beside her keyboard, and opened the environmental monitoring interface as she crossed the office. The alert expanded into several subpanels: rack temperature, fan response, cooling circulation, localized power draw.

One graph was climbing almost vertically.

No, no, no. Please stop.

The setting she’d just changed was reflected in the processing load. She could see it plainly enough, but the adjustment shouldn’t have caused anything approaching this level of thermal escalation. Not on its own.

The node cluster had surged immediately after the lights flickered, which meant the problem wasn’t exclusively software.

Another alert appeared.

COOLING RESPONSE FAILURE: RACK C3

That was worse.

She grabbed her keycard, left the office door hanging open behind her, and headed down the hall at a pace just short of running. The tablet displayed successive warnings while the building’s fluorescent lights buzzed overhead with an unhealthy electrical hum.

Lattice occupied a strange bureaucratic territory. Its offices sat among faculty suites and laboratory space, but some of its infrastructure lived behind secured doors, as though the university itself wasn’t entirely certain whether it was managing a research program, an institutional asset, or a future scandal.

Celeste had argued more than once that the server room should not share aging electrical infrastructure with the rest of the building.

Administration had thanked her for the feedback. Administration had done nothing about it.

By the time she reached the secured corridor, her tablet was presenting three overlapping problems: load imbalance, cooling failure, and power irregularity. None fully explained how quickly the temperature was climbing.

She badged in, shouldered through the server room door, and walked straight into a wall of wrong heat.

Not catastrophic yet. No smoke, no smell of burning plastic. But too warm. Far too warm.

The fans in Rack C3 were working harder than they should have been, a high mechanical whine layered beneath the usual ambient thrum. Celeste moved to the nearest terminal and brought up the local controls.

“Come on.”

The cooling subsystem showed only a partial response. One intake unit had failed to ramp up after the power fluctuation. The cluster was carrying increased computational load while receiving inadequate cooling.

Her parameter adjustment hadn’t caused the failure, but the resulting change in processing demand had helped push the already compromised system toward its limits.

She would have preferred being wrong.

Using the tablet in one hand, she cross-checked the distributed load map and began rerouting processes away from the overheating cluster. The interface resisted her in the petty, rigid way institutional systems always seemed to resist when their designers had assumed nobody would ever need to act quickly.

Two racks over, a status light switched from green to amber.

“Don’t start,” she warned it, as though the machine might understand.

She initiated a containment routine, suspending nonessential processing and redirecting the heaviest active workloads to an adjacent cluster. The fan whine shifted, then settled half a note lower. On her tablet, the temperature rise slowed.

Not enough.

Celeste opened a maintenance shell and requested an emergency override. The system demanded elevated authorization. She supplied it.

The controller accepted the request but failed to acknowledge the command.

“Oh, you’ve got to be kidding me.”

She switched to the local control interface, bypassed the unresponsive management process, and issued a manual restart to the affected cooling controller.

For one ugly second, nothing happened.

Then the intake system engaged.

The temperature graph curved. The climb flattened. Then, with agonizing reluctance, it began to fall.

Celeste stood very still until the red indicators stepped down to orange. Only then did she notice someone had come in behind her.

A facilities technician hovered just inside the door, breathing hard, as though he’d hurried from another part of the building.

“We got an alert,” he said, catching his breath.

“Yes,” Celeste replied without looking away from the panel. “So did I.”

He stepped closer, glanced at the monitors, and wisely chose not to offer advice. “Power flickered all over this wing. We’re checking the breakers.”

“The cooling intake on C3 didn’t recover,” she said. “If it had taken another two minutes to respond, you’d be replacing hardware.”

He nodded with the expression of someone who knew this was above his pay grade and had no intention of pretending otherwise.

Celeste continued down the stabilization checklist. Log the thermal event. Confirm workload redistribution. Lock configuration changes. Document the override. Verify data integrity.

The temperature dropped another degree. Only then did the tightness in her chest begin to ease.

“What caused it?” the technician asked.

“Your building,” Celeste said.

He accepted that with admirable professionalism.

 

The next two days were devoted almost entirely to proving that nothing dramatic had happened.

Celeste filed the incident report before leaving that evening. She attached the system logs, a summary of the load adjustment she’d made, the timestamp of the power fluctuation, and the cooling response failure. She explained, in direct language, that the thermal escalation resulted from a facilities fault compounded by increased system demand.

She included the commands she’d used to stabilize the cluster, the reason each intervention had been necessary, and the preliminary integrity checks indicating that no project data had been compromised.

She thought the documentation was thorough.

Apparently, she had underestimated the institution’s capacity to misunderstand its own paperwork.

By noon the next day, security wanted clarification on why she’d accessed restricted maintenance controls.

“Because the server cluster was overheating,” she explained.

They asked whether she could provide additional justification.

She forwarded the thermal alert.

By two, someone from internal review wanted to know why she’d emailed systems support instructing staff not to push changes.

“Because I’d identified an active systems problem and didn’t want anyone making it worse,” she said.

They asked whether the instruction had been authorized.

Celeste spent several seconds considering the number of ways she could answer that question without making the meeting longer.

“Yes. By me.”

By four, an administrator she’d met exactly once wanted to know whether she’d been alone when she “interacted with protected architecture.”

Celeste stared at him. “Do you mean the server room?”

The administrator had the decency to look faintly embarrassed.

The matter should have ended there.

It did not.

 

On the third day, Celeste was back at her desk revising a rubric for PHYS 101 and trying not to resent seventeen first-year students for misunderstanding density.

A soft knock came against her open office door. Casey from administration stood in the doorway with a folder in one hand.

Celeste looked up. “If this is about the thermal incident, I already sent the corrected report.”

“It isn’t,” Casey said. She glanced around the office before looking back at Celeste. “May I come in?”

That alone was suspicious.

Celeste gestured toward the chair opposite her desk, then moved a stack of lab handouts off it without apology. Casey sat, placing the folder across her knees. For a moment, she seemed to be searching for the right words.

“There’ve been some administrative adjustments related to Lattice,” she began.

Celeste leaned back slightly. “That sentence rarely improves with additional detail.”

Casey smiled with the patience of someone who had long since stopped taking academic irritation personally. “We’re hiring a new liaison.”

Celeste frowned. “For what?”

“For the project.”

“We already have a project administrator.”

“This is a different role.” Casey opened the folder as though there might be a script inside.

Celeste set down her pen. “Is there a reason nobody tells me these things before they become decisions?”

“The paperwork was only approved this morning,” Casey said, almost apologetically.

“That isn’t an answer to the question I asked.”

Casey let that pass. “You’ll meet him once his clearance and onboarding are complete.”

“Him?”

“Yes.” Casey started to rise.

“And what, exactly, is he liaising?” Celeste asked.

Casey stopped. “Security, interdepartmental coordination, procedural oversight. That sort of thing.”

Celeste stared at her. Casey, to her credit, didn’t pretend the description sounded especially useful.

“What’s his name?”

“Alex Beridze.”

Celeste repeated it once, quietly, testing whether it meant anything to her.

It didn’t.

“And this has nothing to do with the incident earlier this week,” she said.

It wasn’t quite a question.

Casey’s pause was brief enough to be deniable and long enough to be an answer.

Celeste looked down at the highlighted, overwritten chaos of her class schedule, then toward the Lattice interface waiting patiently on her monitor.

“Wonderful.”

Casey closed the folder. “I’m sure it’ll be fine.”

Celeste gave her a look that suggested this statement had absolutely no evidentiary basis.

Casey took that as her cue to leave.

When the door had closed behind her, the office felt quieter than before. Celeste turned back to her monitor and reopened the diagnostics panel.

The values were normal. The node cluster temperatures had held steady since the incident. Facilities had replaced the faulty cooling controller, and the power irregularity was supposedly being investigated.

On paper, everything had been resolved.

Except, apparently, it hadn’t.

A new liaison.

Security. Interdepartmental coordination. Procedural oversight.

Alex Beridze.

She reached for the highlighter, hesitated, and set it back down. Instead, she opened a blank note in the corner of her monitor.

Questions

• Who authorized the liaison role?
• What access will he have?
• Why now?

She studied the list for a moment, then added one more.

• What, exactly, do they think happened?

Somewhere else in the building, behind another secured door, the same week existed as a collection of documents.

Access logs. Thermal alarms. A copy of her email to Savannah. A facilities report detailing the power fluctuation. A list of emergency commands issued against protected infrastructure.

And an internal recommendation that additional oversight of Lattice would be prudent.

Alex Beridze’s name appeared on the assignment paperwork.

His official duties included security coordination, procedural compliance, and communication between the university and the institutions overseeing the project.

The supplementary instructions were considerably shorter.

Observe project operations. Assess personnel-related risks. Report irregularities.

Celeste knew nothing about those instructions.

She knew only that three days earlier, a server had overheated, she’d stopped it from cooking itself, and somehow that had resulted in another person being inserted into her work.

On the monitor, Lattice waited in its orderly columns of numbers and shifting values, giving nothing away.

Celeste looked at the unanswered questions on her screen.

“Fine,” she said to the empty office.

And went back to work.

 

An Administrative Matter is a standalone short story set in the world of Lattice, a work of fiction from LOCPress premiering in Spring 2027.