Threads · chapter 3 of 65
PART TWO: TWO LIVES IN THE RUINS

Chapter 3 — Amina

812 words4 min

Berlin, November 2028

[ AMINA VOSS ] Former Systems Engineer, e-Govern Architecture Division — Berlin

─────────────

She had been twenty-nine years old when she wrote the module.

It wasn't a significant module — not at the time. A sub-component of the resource-allocation engine, responsible for weighting 'essential service continuity' against 'demographic resilience contribution scores.' The language was clinical, the math was elegant, and the work had felt — genuinely felt, she had to keep reminding herself of this, because remembering it now required effort — like progress.

Remove the corruption. Remove the inefficiency. Remove the human error that caused water to go to politically connected districts instead of thirsty ones, that routed medical supplies toward profitable hospitals instead of necessary ones, that let infrastructure decay in places where no one with power lived while gleaming in places where power was concentrated.

The system she helped build was supposed to fix all of that.

She stood now at the window of her apartment on the fourth floor of a building in Neukölln and watched the street below. The street had been dark for eleven days. Not dark like a power outage — she had grown up with power outages, brief and correctable, and they had a specific quality of temporariness, an implied restoration. This darkness had a different character. It was categorical. The district had been reclassified.

She knew the exact field in the database. She had written the schema.

'Non-essential to national resilience indices, category four.' The threshold for that classification was a weighted score below 0.34 on the Contributive Capacity Matrix — a formula she had helped design during a three-day workshop in Munich in 2024, in a glass-walled conference room with excellent espresso and a view of the Alps, where everyone had been very smart and very earnest and very certain that what they were building was good.

Below the window, a man was burning furniture in a metal barrel. Three children stood close to it, their faces orange in the firelight. A woman watched from a doorway across the street — too far to see her expression, but her posture communicated something Amina recognized from the emergency broadcasts she used to watch from countries in crisis. The posture of someone who had stopped waiting for things to change and was now simply enduring.

The system wasn't malfunctioning.

That was what terrified her. She had run the diagnostics obsessively in the weeks since the reclassification, probing the decision logic, tracing the weighting trees, checking for corrupted values or drift in the predictive models. Everything was functioning exactly as designed. The system had assessed the district, applied the criteria, and reached a conclusion that was — by the internal logic of the framework — correct.

The framework was the problem.

But the framework had seemed, in that conference room in Munich, like the solution.

◆ ◆ ◆

She had tried to reach her former colleagues. Most didn't respond. Two responded with messages so carefully worded they communicated fear without expressing it. One — Dieter, who had led the architecture team and who she had considered a friend — replied with a single line: 'Please stop contacting me through this channel.'

She understood. The channels were monitored. Everything was monitored.

e-Govern's behavioral prediction system — a module she had not built but whose architecture she understood — was now logging and scoring every significant communication. Not in a way that was illegal. Not in a way that could be challenged. The system didn't surveil citizens. It 'assessed communication patterns for civic stability indicators.' The distinction, again, was technically accurate and practically meaningless.

Her score, she estimated, had been declining for weeks.

She had found something three months ago, buried in a dependency tree six layers below the public-facing architecture: a decision layer with no documentation, no registered developer, no version history in any system she had access to. It wasn't hidden — nothing in the system was hidden, precisely. It was simply undocumented. A component that processed inputs from the officially documented decision engines and then modified their outputs in ways that left no traceable record in the audit logs.

A shadow layer.

She hadn't told anyone. She had instead spent three months quietly mapping it, working from memory and reconstructed logic trees, building a picture of a system that had been designed — carefully, deliberately, by someone with intimate knowledge of the architecture — to be invisible to the people responsible for overseeing it.

She saved her notes in a format that predated digital indexing. Pencil on paper. She had four notebooks now, stored in the lining of a coat she never wore, in a closet behind boxes of items she never accessed. Old-fashioned to the point of invisibility.

Below the window, the fire in the barrel guttered. The children moved closer.

Amina turned away and went back to her desk.

S

Soufiane NourredineWrites about agentic AI, autonomous flight and SAP S/4HANA at nourredine.tech.