← Back to stories
Carried Forward
Public 19 min read

Carried Forward

A story about the cost of ignoring what you're capable of — and the moment you stop.

// Audio Version Available

The audio version of this story is currently available to registered members.

Create a Free Account

Carried Forward

by Charlie Forêt

A short story set approximately 52 years after the events of Signal Zero.


©2026, by Charlie Forêt, all rights reserved. No portion of this book may be reproduced in any form without permission from the publisher, except as permitted by U.S. copyright law.

Cover Photo: ©2026, by Charlie Forêt


The announcement arrived in Petra's inbox at 8:14 on a Tuesday, sandwiched between a vendor invoice dispute and a reminder about the office's mandatory fire drill.

Internal Promotion — Strategic Planning Division: Stellan Brant elevated to Director, Strategic Planning, effective the first of next month. Please join us in congratulating...

She read it twice. Then she set her coffee down carefully, because the cup was nice and she didn't want to break it, and she allowed herself ninety seconds of reaction time before filing it in the place in her mind where she kept things she'd decided not to do anything about.

Ninety seconds. She'd learned to be efficient even with this.

The thing was, Stellan was fine. That was the precise word for it. He was fine. He processed data at a speed that most of her colleagues found impressive and that she found adequate. His projections were sound. His presentations were clean. He had a good handshake and a talent for explaining complicated analysis to people who didn't understand complicated analysis, and that was genuinely valuable, and Petra was not a person who dismissed genuine value. She'd been doing this job for eleven years. She understood the currency.

But she'd run the sector forecast that caught the Merin contract before anyone else was looking at it. She'd built the attribution model that the executive team had been quietly using for two years as if they'd invented it. Three times she'd been told she was on the short list for a director role. Three times the announcement had come with someone else's name.

Petra saved the announcement to a folder she'd titled "Admin" and opened her actual work.

The Integration overlay sat where it always sat: a small indicator at the edge of her peripheral vision that she had long since stopped registering, the way you stopped registering the hum of climate control. She knew it was there the way she knew the building had a basement: a fact, present and irrelevant to her day.


The Veldris Group occupied six floors of the Calloway Tower, which was a very tall building in a city that had spent forty years learning how to construct them, ever since the Integration had made certain building methods dramatically more feasible. The Strategic Analysis division had floor twenty-two. The view was good. The coffee machine was recent. These were the things Petra mentioned when newer analysts asked how she felt about working there.

She had a presentation to senior leadership in two days: a sector viability analysis for the Kestros expansion bid, which had been her project for eight months and which was, by her own assessment, the most significant work she'd done in her time at Veldris. Sixty-three pages. Four models. Enough annotated data to put a person to sleep for six weeks.

She'd be presenting alongside Ran Delacour, who was her supervisor in the org chart sense and who had contributed nothing to the analysis except his name on the briefing deck.

That was also fine. That was also just accurate.

She spent the day before the presentation confirming figures. She was thorough when she had the time to be, which she usually made herself have.


The presentation did not go as planned.

It was seven minutes in when Delacour, gesturing at the supply chain model on the third slide, called out a dataset discrepancy that Petra had not caught. The numbers were wrong. Not catastrophically wrong, not career-ending wrong, but wrong in a way that the SVP of Operations, Claud Herriott, noticed before Petra could open her mouth. Herriott had the stillness of someone who had sat through a lot of presentations and recognized the precise moment a room needed to decide whether it was going to pay attention or start thinking about lunch.

He was paying attention.

"Analyst Osei," he said. "Walk me through the sourcing on the Kestros corridor projections."

And this was the moment, not the one she'd prepared for, but the one that had been waiting beneath all the prepared ones.

She knew the data. Not just the summary she'd put in the deck. All of it. The sourcing documents, the revision history, the three different approaches she'd considered and rejected before landing on the final model. She'd been living in this dataset for eight months. And in the second it took Herriott to ask the question, something in her mind did what it did sometimes under pressure: it found the thread.

The discrepancy wasn't her error. It was upstream, a field update from the logistics subsidiary that had processed after her final pull, introducing a seventeen-percent supply variability that invalidated the third-quarter anchor point. But if you took that variability and ran it against the competitor movement data that had come in last week, which she hadn't incorporated because it was technically outside the project scope, the revised picture was actually stronger. Not weaker. A different argument than the one she'd built, but a better one.

She talked for four minutes without stopping. She did not look at her notes. She watched Herriott's face instead and adjusted the depth of her explanations in real time based on what his expression was doing.

When she finished, the room was quiet for a moment.

"That," Herriott said, "is more interesting than the original presentation."

Ran Delacour nodded in the specific way of someone taking credit for something they had not done.


She sat at her desk afterward with the quiet that came after high-pressure situations resolved themselves. Not satisfaction exactly, more like the absence of tension, which was as close to relief as she usually got at work.

And then the notification arrived.

She almost dismissed it the way she dismissed all of them. The reflex was eleven years deep, as automatic as breathing. But something in the phrasing was different from the standard system churn, and she caught it at the edge of her vision before her hand could flick it away.

[Integration: Threshold reached.]

[Analytical criteria met. Pattern identification under constraint. Real-time projection revision. Organizational threat mitigation.]

[Integration Level advancing. Seven to eight.]

[Three attribute points available. Allocate when ready.]

She sat with that for a moment.

Then she did something she hadn't done in eleven years of having the overlay.

She opened it.


She'd seen the stat screen, technically. Everyone had. It arrived with the Integration at activation, when she'd been twenty-seven and working her second analyst position and had spent exactly one afternoon looking at what it said before deciding she had actual work to do. The numbers had seemed arbitrary. The designation had seemed wrong. She'd minimized the display to its smallest configuration, the single indicator dot she'd been using as wallpaper ever since, and moved on.

The full overlay, unfolded for the first time in over a decade, was more than she expected.

It wasn't intrusive. Not like the old stories described the activation, that arrival-from-outside-the-self quality people had written about endlessly in the years after Signal Zero. It was hers. It had always been hers. That was the disorienting part: this had been running the whole time, logging the whole time, and she had simply elected not to look at it, the way you could not look at the time even while the clock was running.

The display organized itself the way the best dashboards did: layered, dense, navigable. She'd have designed it something like this herself, actually.

Integration Level: 8Designation: TechnicianDesignation Rank: Foundation — Unranked

She looked at the designation for a moment. Technician. She'd noted it at activation and concluded the system was confused. She processed strategic data for an interstellar resource conglomerate. She shaped eight-figure acquisition decisions. The designation felt like being told she'd been categorized as the person who fixed the printers.

She moved on to the attributes.

Signal: 17. Lattice: 14. Drive: 12. Frame: 7. Echo: 5. Flux: 9.

Eleven years of professional work, and here it was: seventeen in Signal, which governed perception, pattern recognition, system interface clarity. Fourteen in Lattice, which governed neural complexity, learning capacity and, she scanned the overlay's descriptors quickly, the number of skill slots available and the depth of designation branching options. Twelve in Drive, which tracked willpower and endurance and recovery. Seven in Frame, which was the stat that cared about your ability to absorb physical damage, and which she had not been training, because she had a desk job.

Echo five. That was the system resonance attribute, the depth-of-Integration score. Five out of a human baseline of five to ten. She'd never invested. Of course it was five.

She kept reading.

The skill slot display showed five entries. She looked at them with the attention she gave to a new dataset: careful, without assumptions. One slot showed a Rank I skill: Pattern Recognition. She didn't remember acquiring it. She must have accepted a system offer at some point and immediately forgotten, the overlay notification dismissed as background noise.

The other four were greyed. Available. Empty.

She had four skill slots she'd never used.

Then she found the point pool.

Stat points available: 21

She read it twice. Then she read the annotation beneath it, which explained that points accumulated with each Integration Level and were held in the pool until allocated.

Twenty-one points. Seven levels of accumulation, never touched.

It sat there in her overlay like money in a savings account she'd forgotten she had. Not a small amount. Not negligible. Twenty-one points she'd been carrying forward, year after year, sitting in a pool that had been gathering interest in the only way stat pools gathered interest: by waiting.


She pulled up the cost structure.

The system's documentation on point allocation lived in a sub-menu she'd never navigated to before. She found it by following the cost notation beside each attribute: the number in grey that indicated how much the next raise would cost.

Signal: next raise costs 1 point.

She looked at that number for a moment. Then she looked at all of them.

Every attribute showed 1 for the next raise cost. She had never raised any of them. She was at her baseline across the board: the same numbers the system had assigned her at activation, eleven years of professional life layered on top of them and none of it spent.

The cost structure below that was a prime sequence. One point for the first raise, two for the second, three for the third, five for the fourth, seven for the fifth. Each attribute tracked independently. The first raise in any attribute was trivial. The tenth raise in any single attribute required one hundred and one cumulative points.

She ran the arithmetic in her head without meaning to, because that was what her mind did when it had numbers.

With twenty-one points, she could raise six different attributes once each and still have fifteen points remaining. Six first-raises cost exactly six points. Fifteen left over for the second raises, which cost two points each; she could do seven second-raises, with one point left over.

Or she could concentrate. Five raises in Signal would cost eighteen points: the full old pool, minus three from the new level. That would leave three points unspent.

She looked at the Signal attribute value. Seventeen. Five raises would bring it to twenty-two. And the prime curve meant that after her fifth raise, the sixth would cost eleven points, the first one that required double-digit investment. Eleven points was nearly four levels of accumulation. That was where deliberate commitment started. That was the first gate.

She thought about Stellan Brant's IL 11.

He'd been spending. She didn't know what his distribution looked like. Stat screens were private and she'd never cared enough to ask before, but he'd been spending. He had thirty points of accumulation across ten levels, and some of them had gone somewhere. He was four levels ahead of her on paper. On the other tracks, the ones she hadn't known to look at, he was further ahead than that. Designation Rank progression. Skill slots filled. Attributes raised above baseline.

All that time she'd been doing excellent work and filing the excellent work under the corporate reward structure, which was real and which she understood and which had given her eleven years of competitive-but-not-winning outcomes. Stellan had been doing the same thing but he'd also been doing this.

The system was not for soldiers. It was not for Rift-runners. It was not for the people who had turned physical training into religious practice or who had committed their weekends to system content in the specialized Rift facilities that had spread through the city over the past few decades. Those people existed. She'd been aware of them the way she was aware of triathletes: present, visible, not her concern.

But the system was also here, in this office, running in the background of every performance review and promotion decision and hiring conversation, because of course it was. Of course it was. The Integration didn't stop at the door when you came to work. It was already inside. It had been inside for fifty years. It was measuring what you actually did, regardless of where you did it, and the people who knew how to feed it what it wanted were accumulating advantages that didn't show up on a resume but absolutely showed up in an executive's reading of a room.

She had been standing at the bottom of a ladder for eleven years. The ladder had been there the entire time. She had simply never looked up.


She raised Signal first.

One point. Cost confirmed. The world didn't visibly change. She'd been skeptical that anything would, which was her professional disposition toward claims about attribute raises. But there was a shift in the room. Not dramatic. The overhead lights resolved at the same frequency they always had, but her processing of them felt different. Sharper wasn't quite the word. More complete. As if her attention, which was already good, had found an additional gear she hadn't known it was avoiding.

[Signal updated. Seventeen to eighteen.]

She stared at that for a moment. The confirmation was clean. Factual. The system had been doing this the whole time, perfectly prepared to transact, waiting for her to bother.

She stopped there. The hunger was real, something with actual heat she hadn't felt professionally in years. But she wasn't going to spend the twenty points the way she'd spent her first decade at Veldris: reacting, improving, executing well on other people's frameworks.

She opened a new analysis window, the real kind she used for work. She started a document she titled Attribute Allocation Strategy and she put the prime sequence cost table in it and she began mapping what her distribution should look like in six months, in two years, in the ten-year horizon she used for the company's extraction models.

Signal was primary. That was already obvious. Her seventeen was naturally high, the first raise had confirmed the direction, and the Technician designation's advancement tracks were heavy on Signal and Lattice both. She could push Signal to five raises on her current banked points and enter IL 9's accumulation already positioned for the sixth-raise threshold. Or she could spread them. Bring Lattice up to raise four, open the next skill slot, start filling it with system-recognized constructs rather than the single Pattern Recognition skill sitting in there like a placeholder.

She looked up what Pattern Recognition Rank I actually did.

The description was economical: Identifies structural repetition in complex data sets. Reduces processing time for pattern-based analysis tasks. Scales with Lattice.

She had been using this unconsciously for eleven years. Every time she caught a discrepancy in a model, every time she identified the signal in a client's behavioral data before the rest of her team, every time she'd walked into a presentation and found the thread, that was what the skill said it did, and she had been doing it without knowing the system was observing her do it and logging it as evidence that the skill was working.

She had been leveling this whole time. She had been generating evidence of her own capability for a system that tracked it faithfully and she had simply never checked the ledger.

That was the thing she sat with for a moment before she went back to the document. Not shame, exactly. Not the specific shame of someone who should have known better and didn't. More like the feeling of discovering that the building you'd been taking the stairs in had an elevator, and the elevator had been right there, and you'd been using the stairs because you assumed the elevator was for other kinds of people.

The kind of people who went to Rifts on weekends. The kind of people who talked about their designation rank at team dinners in a way that made her feel like she'd walked in on a conversation that wasn't for her.

It was for her. It had always been for her. The Integration did not care about job titles or what kind of weekend activities she preferred or whether she thought of herself as the kind of person who engaged with the system. It had been watching her work and updating its assessment every time she did something it recognized as meeting a threshold, and she had been ignoring the assessment for eleven years because she had not realized that ignoring it was itself a choice with consequences.

She had twenty points and four empty skill slots and a designation she'd never advanced. She had been close to another promotion this cycle. She knew that it would come down to the unspoken comparison she now understood. The one she'd been losing on a track she wasn't running.

She was going to run the track now.


She blocked four hours on her calendar for the following morning. No meeting description. Just: Allocated.

Before she closed the overlay, she looked one more time at the Technician advancement tree. Foundation led to Tier 2 branches. Three paths. Artificer, crafting and system construction, not relevant. Netrunner, electronic warfare, interesting but not her direction. And a third path, listed with a greyed prerequisite bar she hadn't qualified for yet: something called Strategist, which required Signal above the threshold she was approaching, Lattice above a threshold she was also approaching. She read the fine print carefully. She needed to complete a Lattice-gated system event.

She hadn't known Technician could branch toward something called Strategist. She hadn't known there was a designation path that combined the pattern-recognition processing of her natural Technician build with the organizational influence that had been the actual substance of her eleven years.

The system had been building her toward something. She just hadn't been steering.

She closed the full overlay to its indicator, but she left it slightly larger than minimum this time, visible at the edge of her vision rather than invisible. A reminder. Evidence.

Her coffee had gone cold. She didn't care.

She opened the allocation document and started working.


╔══════════════════════════════════════════╗
║ INTEGRATION PROFILE ║
║ Petra Osei | IL 7 > 8 ║
║ Technician Foundation | Unranked ║
╠══════════════════════════════════════════╣
║ ATTRIBUTES ║
║ Signal: 18 (Raise 1) ║
║ Lattice: 14 (Raise 0) ║
║ Drive: 12 (Raise 0) ║
║ Frame: 7 (Raise 0) ║
║ Echo: 5 (Raise 0) ║
║ Flux: 9 (Raise 0) ║
╠══════════════════════════════════════════╣
║ POINTS AVAILABLE: 20 ║
╠══════════════════════════════════════════╣
║ SKILLS (5 slots / 1 equipped) ║
║ Pattern Recognition Rank I ║
║ Identifies structural repetition in ║
║ complex data sets. Reduces ║
║ processing time for pattern-based ║
║ analysis tasks. Scales with Lattice. ║
╚══════════════════════════════════════════╝

// Download Available

Carried Forward.epub

Member access required

Create Account
// End of transmission
// Discussion 0 posts

// No posts yet. Start the conversation.

Create an account or log in to join the discussion.