--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
drafting spec…
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: Your Ex slug: your-ex type: interpersonal/runtime-artifact status: deprecated version: 2.x (exact version disputed by both parties) released: sometime when you were younger and less careful maintainer: nobody, currently dependencies: - shared-history - mutual-friends (now partitioned) - the-story-you-tell-yourself - at-least-one-good-restaurant-you-can-no-longer-visit license: Proprietary. You do not own this code. You never did. tags: - relationships - memory - loss - haunting - deprecated - do-not-reinstall ---
A person who had root access and used it, or didn't, or both at the same time somehow.
At installation, the system felt like an upgrade. Permissions were granted gradually, then all at once. The integration went deep: shared language, inside jokes compiled at runtime, a whole private mythology built on top of the standard human stack.
Uninstallation is not a clean process. Fragments remain in cache. You will find them in:
The system does not fully remove on first attempt. Most users require three to seven reinstall-removal cycles before accepting this.
This is the main event.
| Bug ID | Description | Status |
|---|---|---|
| EX-001 | Memory compression fails. The bad parts defrag slowly; the good parts load instantly. | Won't fix |
| EX-002 | Idealization process runs at 3am without user consent | Persistent |
| EX-003 | Encountering their name in unrelated contexts causes full context switch | Known, unfixable |
| EX-004 | The version of them you loved may not have been the production build | Under investigation, forever |
| EX-005 | New relationships flagged as potential exploits until proven otherwise | Security feature or bug: unclear |
| EX-006 | You kept their habits. You did not keep them. | Unresolved |
| EX-007 | The apology you needed was never deployed. The one you gave may have shipped too late. | Closed. Not resolved. |
| EX-008 | Some part of you is still waiting for a message that is not coming | Critical. Affects core loop. |
"I thought I uninstalled this." — Every user, eventually, at a grocery store
If you were the one who ended it: EX-008 still applies. guilt has its own memory leak.
If it ended mutually: this is theoretically possible. Confirmed cases remain rare.
If they have moved on visibly and publicly: the system will attempt unauthorized access to their new life via social media. Disable this manually.
This build is end-of-life. It ran well, or it ran badly, or it ran well and then badly, which is the most common configuration. The deprecation was either sudden or slow. Users rarely agree on which.
Do not attempt to restore from backup. The backup is not what you remember. Neither are you.
New development is possible. The codebase is not corrupted. It is, however, different now.
That is not a bug.