She had memorized all the rules of the system.
Not the stated ones — those were obvious, printed in the documentation, repeated in the onboarding. She meant the real rules: the ones that lived in the behavior of the logs, in the patterns of what got flagged and what didn't, in the silence where documentation should have been.
Aiko had been a systems analyst for eleven years. She knew that every information system was, in fact, two systems: the one that was designed, and the one that had grown.
The designed one: clean, logical, documented.
The grown one: a palimpsest of patches, workarounds, legacy dependencies, and decisions made by people who no longer worked there, for reasons no one fully remembered.
Her job, this week, was to map the second one.
She opened a terminal window. Her fingers moved without thought.
grep -r "deprecated" ./src | wc -l
4,847.
She made a note.
By Thursday, she had a picture.
Not a complete one — she suspected it would never be complete, not this kind of system. But enough. A topology of the real.
She found the node everyone had forgotten: a service spawned in 2019 for a client that no longer existed, still running, still writing to a database that three other systems read from without knowing its origin.
A ghost in the machine. A foundation no one had intended to build on.
She sat back.
In informatics, there was a name for this: technical debt. But that implied it could be paid off.
Sometimes it couldn't. Sometimes the ghost was the foundation.
She began writing her report.