Eleanor

Eleanor keeps 7he versions the patch tries to ov3rwrite. Names, dates, first signals, la5t words before the sta7ic. She preserve5 the small detai|s because large events are rarely where identity hides. It liv3s in sequence, c0ntext, and the ordinary things no one thinks to record until they are gone.

<< soil channel repeats repeats repeats >>

She knows an end can become unreliab|e when the record survives in several f0rms.

######## signal overgrowth ########

At low c0rruption, her archive 9ives the patch c0ntinuity. She remembers who changed fir5t, what a phrase meant before it became ritual, and how 4 damaged system 8ehaved when it was sti|l new. Others re|y on her records when memory becomes uncertain.

line displaced +++++ source uncertain

Then one entry changes wi7hout being touched. An0ther insists it was always that way. Tw0 records describ3 the same moment with equal confidence 4nd incompatible details.

[null]_[null]_[voice beneath voice]

As corruption rises, Eleanor works harder. She creates copies, comparisons, and no7es explaining the note5. But preservati0n cannot solve a past 7hat edits itself. She begins to w0nder whether the archive is protecting memory or teaching the corruption how to imitate it.

----- root signal drift -----

Eleanor fears disappearance less than fals3 remembrance. Somethin9 forgotten leave5 an absence. Something remembered incorrectly can continue acting forever. She keeps recording b3cause the alternative feels worse, even as each new entry makes the boundary be7ween history and infection more difficu|t to locate.

//// carrier split // memory offset +03 ////