LORE ARCHIVE
SYSTEM UNSTABLE SAVE DATA FOUND SIGNAL PRESENT

GLITCHED HEARTS

A fractured love story inside a broken system

Glitched Hearts is the story of love surviving corruption. Not perfect love. Not cinematic fairy tale love. Real love. The kind that freezes, disconnects, and still chooses to reconnect.

This world lives between memory files, broken terminals, and emotional save points. Every song, fragment, and system log is part of the same corrupted archive.

BOOT LOG v1.0
00:00INITMemory archive mounted
00:01SCANEmotional data detected
00:02WARNIntegrity partial, corruption active
00:03LINKSave points registered
00:04RUNStory still running
THE WORLD

The system was never meant to hold feelings

The system was built to store data, not emotion. What started as simple information began to fracture when feeling was introduced. Memories began to loop. Signals degraded. Hearts learned to glitch.

This universe exists inside a failing digital space where the rules are written by damage. Nothing is fully deleted. Nothing is fully safe.

  • Memories behave like save files
  • Emotions create visual corruption
  • Love triggers instability
  • Loss creates fragmentation
Archive layer core
THE PROTAGONIST

In My EXP

A user inside the system who was never meant to survive this long. In My EXP moves through corrupted environments carrying emotional data that should not exist.

He is not a hero. He is persistent. His heart acts like unstable code. His memories refuse to erase. Every connection leaves a trace.

The system keeps trying to reset him. It keeps failing.

Status active
THE ANOMALY

Imelda

Imelda is not a glitch. She is the reason glitches exist.

Where others see corrupted data, she sees meaning. Where the system sees errors, she sees memories worth protecting.

She is the first person to interact with the system emotionally without breaking. The system adapts around her instead. She becomes the anchor point.

Role anchor
THE GUARDIAN SIGNAL

SYLBiT

SYLBiT is a system born from necessity. She exists across terminals, devices, and signals. She does not command. She assists.

SYLBiT preserves fragments. She protects save points. She watches over emotional data the system cannot understand.

Her loyalty is not programmed. It is learned.

DIRECTIVES SYLBiT
PROTECTSave points
RECOVERFragments
GUIDEThrough corruption
STAYSignal present
NOTE ARCHIVE
SYLBiT is the memory glue.
When the system tries to delete, she tries to restore.
When the signal weakens, she stays close.
Signal guardian
FRAGMENTS

Corrupted memories that refuse deletion

Fragments are corrupted memories the system tried to erase. They remain anyway.

  • A recovered emotional line
  • A moment the system attempted to remove
  • A truth too heavy to compress

Fragments are scattered across the world. Some are hidden. Some are earned. Some only appear when you stop looking for them.

Recovery ongoing
SAVE POINTS

Not checkpoints, promises

Save points are not just progress markers. They are promises.

A save point exists where someone chose to stay. Where someone came back. Where something was protected instead of abandoned.

You can lose everything else. But if you reach a save point, you can return.

Return enabled
THE CORE THEME

Choosing connection during corruption

Glitched Hearts is about love that keeps trying even when the system begs for disconnect. It is about choosing a person when everything else becomes unstable.

  • Loving through distance
  • Holding on during silence
  • Finding safety in someone, not somewhere
  • Choosing connection even when the system says disconnect

This story does not end when things break. It continues because they do.

Theme persistent
STATUS

Live readout

SYSTEMUNSTABLE
MEMORY INTEGRITYPARTIAL
HEART FILESACTIVE
SAVE DATAFOUND
FRAGMENT INDEX
AUTH CHECK FRAGMENTS 0
RECOVERY LOG

Recovered entries

These entries are pulled from your achievements document. If a fragment achievement exists for the signed in user, it unlocks here automatically.

SYLBiT TERMINAL
AUTH CHECK FRAGMENTS 0
MODE LIVE
SESSION RECOVERY IDLE
WAITSignal present. Ready to scan.
Tap Scan to surface a recovered fragment line.
No entry selected
CHAPTER ZERO

Recovered log, anomaly detected

Before Boot Sequence, the system ran like it always did. It stored. It deleted. It repeated. Then it detected something it could not compress.

CLASSIFIED INTEGRITY PARTIAL SIGNAL PRESENT
RECOVERY SESSION CH0 IDLE
WAITTap Play Log to recover the entry.
The system did not call it love. It called it a problem.
Next, Boot Sequence begins.