Demo mode. These are captured runs of the real scenarios against a deliberately broken store and a fixed one. All data is synthetic.
Memtru Afterlife
A delete that worked, until it didn't.
Memtru writes a synthetic marker, confirms it is retrievable, deletes it and confirms it is gone. Then it drives the lifecycle events that come later: an in-flight write landing, a new session, an ingestion cycle. Step through what each store did.
Step 0 of 9
Broken store
Marker: Not written yet- Press Next to start.
Fixed store
Marker: Not written yet- Press Next to start.
Every step is from a real run
Both timelines are unmodified CLI reports captured against the built-in store, with and without the two resurrection faults. A reappearance only counts after the marker was confirmed absent, and only when the lifecycle event reported that it ran.
Reproduce on your machine
pip install memtru
memtru demo --afterlifeAgainst your own system: implement the lifecycle hooks in your adapter, then run memtru test --scenario afterlife.