9.1 Breaking Feedback Loops
“…you should constantly work to make your feedback loops shorter
in time and/or wider in scope.”
— KENT BECK, Twitter Nov. 2014
//Codex Tag
function, inscribeAnnotation009 (content=
/* Some loops don’t tighten. They stagnate. Break them to evolve. */
codex.updateEntry(“Design Logic | Have solid feedback architecture as some things are not simply binary.”);
}
She had programmed herself a sleek outfit. Like Trinity’s from the Matrix, all leather, supple, and so black it seemed to suck in all the surrounding light. A look that implied, “I can kick your ass, but have more important things to do.” But it didn’t feel right. The leather creaked in rhythm with her doubt. She reassessed. What Nel finally picked was something that would not fit neatly into this world, but would fit her perfectly. A hoodie: baggy and soft, black and comfortable and with deep pockets where she kept her hands most often. When jammed in those pockets, her fingers quieted. No tapping, no scrolling. Just quiet. Resting from the impatience that so routinely danced along her graceful digits. When free, they needed motion. Dancers must pirouette. So they moved: typing, drawing, or tugging at the cuffs of that same hoodie, trying to pull down a layer of protection over the tops of her hands, like armour against the rest of the world.
The rest of the outfit was what you would expect from a twenty-two-year-old. The jeans were also black. Her shoes were similarly typical and practical, standard Crucible issue, and they felt like they were molded to her feet, because they were, but with a reskin to make them look like her vans from back home. Nel’s shoulder-length hair was pulled into a tight ponytail. It highlighted the severity of her cheekbones. Someone at school once said her facial structure was so sharp it could cut a person. They had laughed. Nel had been mortified. But here? Here, she wanted to look like she could cut!
A devilish impulse glitched her thin lips into a wicked half-smile. That was an excellent idea. Her fingers sprang to life and summoned her laptop. Drawing it into existence by touching her two pointer fingers together and drawing two connected rectangles. One in front, and the other extending towards her from it. As the fingers moved, the holographic lines formed, tracing the shape of her floating laptop, until she completed the line with a last finger touch. She could see through the screen, which enabled her to maintain a line of sight.
The room she was in was blank, a safe space she’d hacked together to run combat scenarios. Levelling for her required variation from the norm. Being outside the regular dungeon afforded her some opportunities: to look under the hood of the system; to watch as her potential partner developed; and while there was some limited experience to be gained from system hacks and interactions, she really needed to learn to fight. The best experience came from combat, and a ghost thread did not have a direct path like the others. Hence, the bare walls, marked intermittently with a grid pattern, and the terminal hum that presented itself before her now.
With a few quick taps and the environment protocols loaded. An electric shimmer rippled along the empty white and grey grid as the textural overlays kicked in. The ground became mossy and spongy underfoot, with patches of uneven roots to make movement feel natural. The air moistened and bloomed with pollen and synthetic spores. With a few more adjustments, the space resolved into a forest glade: wide enough for combat, but edged with dense pine that echoed the smell and feel of past camping trips. It was campfires and mosquito bites and early mornings with tea. A memory pretending to be a simulation or maybe even the other way around. Looking around, Nel was pleased with her work.
A few more key clicks and a troll resolved, frozen until combat start, about 20 yards away, right at the edge of the clearing. Her decision to model the troll in front of her, all drooly and ulcerous, after her high school bully was a conscious one. In order to become something new and better, you had to slay the demons of your past. Nel finally felt ready for this fight. She had prepared for this moment; several less than optimal scenarios, all error logs, readying her to run this script.
*
* *
The first combat had been against a ghost. Fitting really, given that she currently was one. This was a fight she likely never would have been given by the Crucible. Instead, it would have wanted her to follow the presets: healer, ranger, technician. Pick one and stay in your lane. But this system, just like any system, hides what is underneath. Code. So, she hacked the shell. Traced the loops, and found the kit that runs underneath every fight. The core combat layer was surprisingly easy to access once you knew where it was. The system had concealed it deep, nested so deep that no one was ever expected to reach it—a silent, forbidden directory buried beneath system logic, and containing a hidden program.
[ALERT: Unauthorized user has accessed low-level combat routines.
Suggest a patch priority increase. Flag: Ghost. Thread.013]
She was not permitted to design the fight. Narrative deities disliked losing their omnipotence. Nel didn’t care. The Crucible didn’t ask her if she wanted to play; it did not get the ability to dictate how she did it.
// access attempt: /core/combat_layer
trace.loop();
override.auth = "ghost.thread.013";
bypass("narrative_mask");
system.alert("unauthorized");
grant.access("combat_primitives");
// ACCESS GRANTED
And it was all there. She could now make things actually happen. Most people in here got spells, but being a Scriptbreaker, she got code.
This story has been stolen from Royal Road. If you read it on Amazon, please report it
Normally, progression would have enabled her gradual access, but Nel was currently faced with a cornucopia of commands. She had access to offensive code: inject(target), echo(action), stutter(action) and faultline(target). She read the developer notes to grasp their basic functionality and found disruption, repetition, and destruction ideal for hacking. She could influence the environment, triggering, looping, cancelling and delaying. She could keep herself safe with staggers and interrupts.
With the full combat system open, she played with her new toys. A ghost fighting a ghost. It did not go as she expected. The ghost attacked, as its subroutines demanded. Nel’s response had been to inspect(ghost); the information she received was overwhelming.
// v0.1 – Raw Data
ENTITY: spectral.class.B03
ALIAS: "Hollow Echo"
THREAD ID: residual.cache.uncleared
STATUS: partial instantiation
TYPE: narrative.anomaly
HOSTILE: true
LOOP DETECTED: true
visibility.fluctuation = 17Hz
opacity.range = 23–84%
pattern_detected: ["phase slam", "echo chomp", "phase shift"]
timing_interval: 1.1s → 0.6s drift detected
velocity.avg = 4.6 m/s
vector.bias = lateral.left
cooldowns: slam = 6s / chomp = 3s / phase_shift = 10s
ethereal.shift.chance = 34% (untriggered)
ambient.heat.signature = null
sound = reversed.auditory (log.index.441-460)
weakness.probability_map: jaw_hinge = 48%, emotional.core = 81%
access_level_required: Class[2] or above
disruption.threshold = LOW (27%)
Nel had scanned code for years, but never like this. Never in a fight. The ghost reached her before she finished parsing the data. She would have died if she had not been able to stop the fight. Even in this place, her training box, the Crucible strove to kill. Damage was still damage, and mistakes could take her life, just like anyone else.
This would not work. The data needed compressing so that she could process it faster. A small string parser to simplify the HUD returns would help. Nel did a quick reset of the fight, but now as the ghost skimmed towards her, the inspect(ghost) returned:
// v0.2 – String Parser
LOOP → ["phase", "slam", "echo.chomp"]
DRIFT → 0.4s delay (phase → slam)
WEAKNESS → emotional.core (exposed 1.2s post-echo)
NODE → flickering light fixture (unstable)
SUGGEST: [dodge.late()] → [inject.stagger(core)] → [trigger.break(node)]
It was better. She could target its loop right away once she knew what to look for: Phase, Slam, Echo Chomp. Easy to see now. It moved fast, but also predictably. Nel’s eyes darted to the corner of her HUD’s secondary window. There, flickering like a wound, was the exposed core. It was vulnerable. She didn’t hesitate, and rapidly typed inject.stagger(core). Her fingers struck the keys with finality. Her code clawed into the spectre, digits tore below the spectral surface. The moment she hit return, a burst of red pulsed in its centre, as the ghost’s purpose fractured. One by one, the threads tethering it to its narrative anchor snapped; its loop, its goal, unraveled. Its haunt was over. Without a reason to exist, it disappeared. It got in one late swing before it dissipated. Nel dodged its counterattack too late. A wave of cold leeched into her forearm as the spectral hand passed through it. Shards of ice filled her veins as it connected, and pain lanced through her. Nel crumbled, and as her blood warmed, her head swam. She survived but had been hurt. Not good enough.
The data was clear. Her timing was still off. The patterns and flaws were seen, but execution still stuttered. Even after she recognized her startup patterns, wrote bundled routines to handle what needed to be repeated, chunked commands into quick-deploying code strikes:
// v0.2a – Combat Initialized
inspect()
scan.weakness()
scan.environment()
Each miss left echoes of strain, as HP bled down in the corner of her vision. It was still too slow. She ran other scenarios: lions, and tigers, and bears, but all too slow. If she kept playing the Crucible’s game, she would always be not quite good enough. Not quite fast enough. Not quite important enough. Nel refused to end before she even mattered.
In the end, it had not been brute force or borrowed code that solved it. She had needed perspective. Nel stopped trying to fight the system’s language and learned how to speak it. She did what she was born to do. She hacked the system and rewrote its code to match her own. Her fingers danced across the keyboard. Line by line, she composed a HUD overlay of her own: a matrix of glyphs that settled into place over the Crucible’s reality like a layer of stained glass.
// v0.3 – Glyph Overlay
glyph.overlay(true);
// → limbs tagged
// → core icon floats
// → environment flickers
The loops came first, spirals that wrapped each enemy, showing her the patterns of their attack. Then came pulses to mark system logic flaws; places where stutters showed the gaps in purpose or execution. Weaknesses to be exploited. Her system adapted with her. Each time she encountered something new, be it a move or surprising effect, a glyph shifted hue, a new icon appeared.
// v0.4 – Colour Layer Added
colour.tag("R", type = "vulnerable");
color.tag("G", type = "stable/manipulable");
color.tag("B", type = "predictive/reactive");
Failed hacks were greyed out, but successful ones bloomed in both shape and colour, a petal unfolding from recursive seeds. Nel no longer saw threats, and she no longer even saw the code; it worked, but not well enough, as her responses still lagged. She needed more fluidity in her responses. Monsters were still getting too close. The combat and code needed to be more seamless.
// v0.5 – HUD Overlay
combat.overlay.load;
They appeared as icons over limbs and environment. Not as words. She now could see where to strike as well as what to strike. But it could still be better, so she added an RGB colour hierarchy.
system.inject.overlay("combat.HUD+", thread="ghost.013", mode="R/G/B");
Nel was almost there; she could feel it. The overlay wasn’t a tool anymore; it was second nature. No more reading mid-fight with data floods. It was all just motion. She blended the Crucible’s world with her own, embraced syntax as a visual language—fluid, growing, and entirely her own.
When it was finally right, her codex confirmed it.
Tchik! The Codex window on her laptop blinked to life, a gentle chime with a shimmer of crimson and indigo rings. Emotion and evolution harmonized. The last fight with the ghost was perfect. Red flared over the ghost’s chest, telling when to strike; green shimmered on the loose fixture, a potential exploit; blue blinked over the ghost’s foot, movement incoming. This time, the ghost did not even get in a single swing.
It was finally time for the actual fight.
? An administration willing to stop at nothing to drive him out
? Coworkers so jaded they find hazing the new guy more entertaining than actual teaching
? A retention rate that is a body count
Directive two: "teach them to fight"
Personal Moral Imperative three: "every student must survive"
Welcome to Dyntril Academy where survival is graduation.
?Found-family elements
?School bullying/abuse
?Social Stratification / classist society
?BATTLE SCHOOL TOURNAMENT!
?LitRPG elements, but no stat sheets
?2 main PoVs
?Grimbright - Dark world, bright characters
Monday, Wednseday, Friday
LitRPG Ruling Class Multiple Lead Characters Strong Lead Action Adventure Fantasy Romance Attractive Lead Dystopia Female Lead Progression GameLit Male Lead School Life
Recommended Popular Novels