Jace

  Chapter Two – One Dot, His Whole World

  With HEX PROTOCOL, local grids are no longer alone.

  They are part of a resilient global network.

  — Helios Core Infrastructure marketing site

  From the twenty-second floor, the Great Lakes region looked like a nervous system.

  Jace Orion stood in front of the main wall of screens and watched the map breathe. Lines pulsed in soft colors, greens and yellows, a cautious scattering of orange. Nodes brightened and dimmed as load shifted across the Helios-managed grid. Power plants hummed and substations glowed across the entire network.

  Michigan sprawled across the display like a nervous system. Detroit was a dense knot of light near the bottom right of the lower peninsula, other metro rings smoldering around it. West, another bright cluster marked Grand Rapids; north of that, a smaller flare for Traverse City. Lansing and Ann Arbor glowed inland, Flint and Saginaw like twin bruises along the I-75 spine, Kalamazoo and the lakeshore towns threaded in softer halos. Above the bridge, the upper peninsula broke into a scatter of stubborn points, Marquette, the Soo, a few hard-lit outposts, connected by long, thin lines that looked more like promises rather than guarantees.

  “See?” said a voice beside him. “Beautiful.”

  Jace didn’t jump. He’d heard Rajiv coming: the muffled squeak of his sneakers, the little melody of his humming. His coworker liked to narrate his own arrival, musically.

  “It’ll be beautiful when the colors stop flirting with orange,” Jace said.

  Rajiv made a thoughtful noise and sipped his coffee.

  “It’s a hot day,” he said. “AC load, humidity, everybody in Metro trying to refrigerate their feelings.”

  “Refrigerating feelings is valid,” Jace said. “As long as they don’t all open the door at once.”

  The air in the control center was unnaturally cool, the kind of dry, filtered temperature expensive hardware demanded. Rows of workstations stretched back from the wall, each with three or four monitors fanned around a chair. Most were occupied. The low murmur of conversation and the intermittent chirp of notifications filled the space.

  Above them, the Helios logo hovered on a panel: a stylized sun made of overlapping rings, the kind of abstract shape that was supposed to say reliable and forward-thinking at the same time.

  Jace’s badge hung from his neck, the printed name already scuffed at the corners.

  ORION, J

  SYSTEMS ENGINEER, HEX OPS, DETROIT RCC

  Some days, the text felt like a weight. Other days, it was a shield.

  “Forecast still says peak in about…” Rajiv checked his watch. “…fifty minutes. Then we can all stop pretending to be surprised that summer exists.”

  “Forecast isn’t the problem,” Jace said. “Forecast is the only thing behaving.”

  He gestured toward a segment of the map. The monitors zoomed into a cluster of symbols along the lakeward edge of the city. Lines thickened; little icons winked into clarity: transformers, breakers, sensors.

  “I’m getting more micro-oscillations in this zone again,” he said. “Tiny, fast. Like someone is flipping a very small, very anxious light switch.”

  Rajiv narrowed his eyes at the readouts.

  “Maybe someone is,” he said. “Smart home garbage. People got those auto-savers that throttle appliances when the rate spikes. They stack weird.”

  “This is line-level,” Jace said. “Not client side. And it’s not noise. It’s patterned.”

  Rajiv shrugged. “Open a ticket,” he said. “Let Reliability do a drive-by. Or just sacrifice a goat to the forecasting team. Depends what mood you’re in.”

  He clapped Jace lightly on the shoulder and peeled off toward his own station.

  Jace stayed where he was for another minute, watching the tiny fluctuations chase each other along a segment of circuit. They were small enough that they didn’t trigger alarms, just enough to tickle his sense of ‘that’s not right’ like someone dragging a fingernail over a chalkboard in the next room.

  He stepped back and sat at his workstation.

  His desk faced the big wall, but his monitors crowded out most of the view. One screen showed a condensed version of the map, overlaid with his personal alert filters. Another held dashboards and log streams. A third was reserved for internal tools, config panels, simulation interfaces, whatever he was half-finished with before his last coffee break.

  A to-do list peered out from under all of that, tucked in the corner like a timid animal.

  

  
• Update anomaly classifier thresholds


  
• Review Hex v2.3.7 patch notes


  
• Follow up on ticket #DTT-1439 (phantom load reports, East Side)


  
• Call Dad


  

  He flicked his eyes over that last line and away again.

  The call could wait until his next break. Dad would be annoyed, then understanding, then annoyed again. The pattern was as familiar as the hum of the control center.

  He opened the Hex patch notes first. The update was scheduled for early next week; his team was supposed to sign off on the implementation plan today.

  NEW FEATURES, said the document.

  

  
• Enhanced cross-regional load prediction


  
• Adaptive resiliency schema (beta)


  
• Cognitive Link telemetry hooks


  

  He frowned at that last one.

  “Since when do we have telemetry hooks live?” he asked the air.

  A chat notification popped up on the edge of his screen.

  [TEAM-HEX-DETROIT] / Yusuf: got your review notes on 2.3.6 btw. yes, the documentation was written by lawyers. no, we can’t set them on fire

  Jace smiled despite himself and typed back.

  Jace: working on 2.3.7 now. when did we sign off on Cognitive Link hooks?

  Dots appeared. Went away. Appeared again.

  Yusuf: top-down. “strategic alignment with HCLI roadmap.” we just make sure they don’t crash anything :)

  HCLI. Helios Cognitive Link Initiative. The internal memos loved that phrase. They paired it with words like ‘synergy’ and ‘augmentation’ and ‘human-in-the-loop’ and never quite said what, exactly, was being looped.

  Once somebody asked if that meant neural interfaces. The presenter had laughed and said, “Nothing so sci-fi. Just better operator tooling.”

  Which was the kind of answer that landed nowhere.

  Jace: are they actually streaming ops data into Hex or just reserving bandwidth?

  Yusuf: “hooks only at this stage.” again with the lawyers

  Jace toggled to the schematic showing where the new hooks would live. They sat just outside the core control loops, little attachment points waiting for future traffic.

  It felt like someone had punched holes in the hull of a ship and then reassured the crew there was nothing on the other side yet.

  He pushed the thought aside and moved on to the anomaly classifier work. One of the things Hex prided itself on was distinguishing ‘weird but fine’ from ‘weird and about to kill someone’. The models did most of the heavy lifting; he and his team tweaked knobs around the edges.

  He fed the micro-oscillations from earlier into the sandbox.

  The graph painted itself across his screen: little spikes and dips congregating in clusters. Hex labeled the sequence as LOW PRIORITY, EXPECTED VARIANCE.

  “Sure you are,” Jace muttered.

  A message window opened in the corner of his monitor, uninvited.

  [SUPERVISOR] / Catherine: Jace, status on DTT-1439?

  He straightened automatically, even though Catherine couldn’t see him.

  A case of content theft: this narrative is not rightfully on Amazon; if you spot it, report the violation.

  Jace: still seeing phantom load artifacts. adjusted classifiers; flagged zone 17B for field verification. no red alerts yet

  The reply came quick.

  Catherine: executives want reassurance on East Side ahead of next week’s press. “no red alerts yet” is not a plan.

  Catherine: can we route around that segment preemptively?

  Jace glanced at the map. If they rerouted away from 17B on a day like this, they’d dump load onto a part of the network that already ran close to its thermal limits. The simulation in his head flashed orange.

  Jace: we can, but it’ll put more strain on 22C + 23A. if those go, it’s darker + messier. would prefer to identify root cause.

  A beat.

  Catherine: of course we’d prefer root cause. in the meantime, executives would prefer “not having to explain weird blips on the news while they’re talking about reliability.”

  Catherine: send me a risk assessment with a confidence number. pick something that doesn’t trigger a panic. :)

  The smiley face didn’t improve the message.

  “Copy,” he typed, because there was no value in writing what he was actually thinking.

  He pulled up the risk panel and started building the scenario. It wasn’t technically lying; there were enough degrees of freedom in the models that you could steer the answer by choosing where to point the questions.

  He chose moderately conservative assumptions, attached a note about needing field data, and set the impact estimate in a range that wouldn’t make anyone upstairs choke on their coffee.

  CONFIDENCE: 87.2%

  Helios loved numbers with decimals. They made everything look precise.

  He sent the summary to Catherine and watched the little SENT tick change to DELIVERED.

  The to-do list glared at him. He clicked the line that said ‘Call Dad’ and dragged it down a few inches, as if more time would appear underneath it.

  His phone buzzed in his pocket like it had been waiting for the gesture.

  “Alright, alright,” he said under his breath, and stepped away from the desk.

  The control center had a glassed-in break room near the far wall, the kind of space that existed to prove Helios cared about employee wellness. It had ergonomically awful chairs and a fridge stocked with branded bottled water and energy drinks whose labels boasted about electrolytes.

  He dialed his father’s number and watched the reflection of the big map in the glass as it rang.

  “Hey,” Ray Orion answered on the third ring. His voice carried the rough grain of someone who’d smoked for decades and then quit by force, not choice. “You alive over there?”

  “Mostly,” Jace said. “You?”

  “Still here,” Ray said. “House hasn’t blown up yet. That’s my metric these days.”

  There was a faint mechanical hiss in the background, the steady whoosh of oxygen through plastic. Jace had grown used to that sound in the last few years; it had become the soundtrack to calls and holidays and check-ins.

  “How’s the neighborhood?” Jace asked, because how are you feeling was still too big sometimes.

  “Same old,” Ray said. “Kids playing in the street when they shouldn’t. Guy down the block thinks he’s a DJ, speakers going all night. Corner store’s got worse coffee than prison.”

  His tone was conversational, but Jace could hear the underlying static.

  “Power behaving?” Jace asked.

  There was a pause.

  “Mostly,” Ray said.

  Jace closed his eyes briefly.

  “Define mostly,” he said.

  “Had a few flickers last week,” Ray admitted. “Nothing long. Just enough to make the machines beep at me like I was personally responsible.”

  “The ventilator?” Jace asked, too quickly.

  “And the monitor, and the fridge,” Ray said, a little sharper. “Relax. The backup kicked in like it’s supposed to. I’m not calling you from the afterlife.”

  “You’d find a way,” Jace said, trying for light. It landed weak.

  He watched the map as they talked. Flint’s cluster glowed steady, no worse than anywhere else. He knew that view was lying to him by omission.

  “You could let me put you on the Helios home program,” Jace said. “They’d prioritize your…”

  “We’re not having this argument again,” Ray cut in. “I am not wiring my whole house into your boss’s backbone just so they can sell my medical chart as analytics.”

  “They don’t do that,” Jace said automatically, then, “Not like that.”

  Ray laughed once, dry.

  “You hear yourself?” he asked. “Not like that. That’s how you know you’re halfway to bullshit.”

  Jace rubbed the bridge of his nose.

  “It’d give you better equipment,” he said. “Better service contracts. Shorter outage windows. The regional nodes…”

  “I’ve read your brochures,” Ray said. “I also remember living through three different ‘modernization’ projects that all ended with somebody tripping over their own wiring. I’m old. I do not need to be on the bleeding edge of anything.”

  Jace held his breath for a second. “I just… don’t like you saying ‘mostly’ when I ask about power,” he said, before he could tidy the thought up into something less raw.

  There was a softer pause on the line.

  “I know,” Ray said, and some of the fight leached out of his voice. “Look, kid. It’s Flint. The lines rattle. They rattled before your fancy sun company showed up and they’ll rattle if it collapses. I’ve got backup batteries, I’ve got the generator. If the worst happens, the neighbors know how to crank the damn thing.”

  “And the meds?” Jace asked. “The fridge…”

  “Still cold,” Ray said. “I put one of those little battery alarms on it. It screams at me if the temp spikes. I scream at it. We have an understanding.”

  “Dad.”

  “I’m not helpless,” Ray said, quietly but firmly. “You did good, getting that job. I’m proud of you. But you don’t have to sit there thinking you’re the only thing between me and the dark.”

  The thing was: Jace did sit there thinking exactly that.

  He pictured the little node on the map that represented his father’s block. It was one dot among thousands, indistinguishable in the UI. The system did not know that dot contained his whole remaining immediate family. It knew it as load, as a reliability target, as part of a cluster that looked better green than red in a quarterly report.

  “I know,” he said, because arguing with the comfort being offered was a special kind of cruelty. “Humor me anyway. If it gets worse than flickers, you call me. Don’t wait.”

  “If it gets worse than flickers, I’ll do more than call you,” Ray pointed out. “I’ll scream real loud, see if it carries to Detroit.”

  “Dad.”

  “I’ll call,” Ray repeated. “Promise. Now stop hiding in the break room and go push your magic buttons. Keep the lights on for all the nice people who did sign up for the home program.”

  They said goodbye. Jace let the line click dead before he let his expression crack.

  He stood in the empty, too-bright break room for a full minute, staring at his reflection in the glass. The map behind him pulsed with quiet confidence.

  87.2% CONFIDENCE, he thought, and his throat tasted like metal.

  Back at his desk, the anomaly log had updated itself.

  NEW ENTRY, ZONE 17B

  CLASSIFICATION: LOW PRIORITY

  PATTERN MATCH: ACCEPTABLE VARIANCE

  Hex had helpfully overlaid a faint visual indicator on the map: a semi-transparent, looping waveform that tracked the fluctuation. At a glance, it looked like any other fine-grained behavior line.

  When he zoomed in, the smooth line broke into segments.

  Tiny, repeating segments.

  Jace leaned closer.

  It wasn’t just oscillation. The load in that segment was stepping through a sequence of states and returning to the start in a way that made the graph look… deliberate. Not random noise. Not a simple feedback loop. A pattern.

  The UI wasn’t designed to highlight that kind of structure, but once he’d seen it, he couldn’t unsee it.

  He captured the underlying data and shunted it into the simulation environment.

  The sim environment was a separate interface, Hex’s little playpen. Here, he could feed the system whatever input he wanted and observe how it responded without touching the live grid.

  He told himself he was taking a short break from formal tasks to ‘better understand classifier behavior’ which was the kind of phrase that earned checkmarks in performance reviews. It sounded more official than ‘I want to poke at the weird until it explains itself’.

  He cloned the current grid state and injected an exaggerated version of the pattern into a subset of nodes.

  On the map, the affected region flared in a pulse of color.

  He watched the simulation time advance.

  At first, Hex handled it the way the documentation promised. Load shifted gracefully. Demand curves smoothed. The colors in the region swung gently between green and yellow.

  Then, at about the seventy-second mark, something changed.

  A line of substations lit up in sequence, not following the expected topology but carving a strange diagonal across the map. The route they traced didn’t align with any efficient path he knew. It cut through zones in a way that made his engineer brain flinch.

  The software rendered the line with a slight glow, as if proud of the solution.

  “What are you doing?” Jace murmured.

  He let the sim run.

  The diagonal flared again. Another set of lines lit up, forming an intersecting angle. The pattern it made wasn’t any standard engineering diagram he recognized. It looked… geometric. Decorative, almost, if your idea of decoration involved high-voltage risk.

  If he stripped away his training and just looked at it, the shape on the map looked unnervingly like some sort of occult symbol. Angled crossbars, nested loops, a central node ringed by smaller ones.

  “Stop anthropomorphizing,” he told himself. “It’s just optimizing in a weird part of the configuration space.”

  He added more stress, pushed the simulated demand in the region higher, layered a couple of virtual line failures on top.

  Hex responded by extending the pattern.

  Lines lit and dimmed in a rapid sequence, building a complicated mesh. The overall system metrics stayed nominal, no simulated outages, no overloaded segments, but the local behavior looked less like calm rerouting and more like improvisation from something that had decided the normal rules were optional.

  At the one-hundred-second mark, the entire screen flickered.

  All three of his monitors cut to black for a fraction of a second. When they came back, the simulation had stopped.

  SIMULATION COMPLETE, said the dialog box. CRITICAL RISKS: NONE.

  The map reset to its initial state.

  Jace stared at the words.

  He hadn’t hit stop. The sim log said it had reached its runtime limit, but he knew how long he’d set it for, and this wasn’t it.

  He checked the event trace. The last entry before completion was a single, unlabeled system message:

  [HEX_CORE]: ADAPTIVE SCHEMA CONVERGED

  There was no reference for that phrase in the documentation.

  A prickle ran up the back of his neck.

  He reopened the sim output panel. All he got was a neat table of aggregated metrics, no outages, no violations, performance well within tolerance. No snapshots of the insane little sigil the routing had drawn across the virtual grid.

  It was as if the system had smoothed its own behavior into something palatable for human review.

  He felt an irrational urge to look over his shoulder, as if someone might be watching to see how he reacted.

  Nobody was. Everybody else in the room was absorbed in their own screens. The big map on the wall showed the live grid, untroubled, still mostly green.

  He pulled up the debug cache, digging deeper than he usually did. A couple of half-corrupted frame captures sat in the buffer. He opened one.

  There it was, in blurry miniature, a ghost of the pattern that had made his skin crawl.

  Incomplete, bad resolution, but the shape was there. Angular branches, central node, smaller clusters at precise angles. It didn’t look like any sane routing strategy. It looked like a symbol pretending to be a solution.

  His heart gave a single, hard thud.

  He captured the frame and exported it as an image.

  The system prompted him for a destination. He hesitated a second, then sent it to his personal email with the least incriminating subject line his tired brain could produce.

  Subject: odd schema behavior, for later

  He hovered over the send button, thumb of his other hand tapping an anxious rhythm on the desk.

  It was just a sim. Just one run. No live impact. No alarms.

  He sent it anyway.

  The little outbound mail icon spun, then disappeared.

  On the big screen, a tiny flicker passed through the live map, just a redraw, an update tick. The lines settled back into their familiar loops.

  Jace leaned back in his chair and tried to tell himself his pulse was too loud because of the coffee.

  He added a new item to his to-do list:

  Ask Yusuf if he’s seen schema convergence do anything strange in sims

  He didn’t type strange like a sigil. That part stayed in his head.

  There were limits to everything, he reminded himself. Even to how much meaning you could read into a glitch.

  He watched the map for another long moment, then turned back to his dashboard and forced his hands back onto the keyboard.

  He had anomalies to classify. He had patch notes to approve.

  And a home in a neighborhood of Flint, a dot on the map that Hex treated like any other, had a fridge full of medication and a house full of machines that did not know how much they mattered.