Stale-location incident

Run a deterministic memory failure from capture through diagnosis, replay, and regression.

The repository includes a credential-free reference incident that stores an old city, records a correction, and deliberately retrieves the stale record.

Run the complete example

git clone https://github.com/Meyk0/engram-viz.git
cd engram-viz
npm install
npm run engram -- demo stale-location

That one command initializes local capture, starts Studio, records the three turns, and opens the Incidents workspace. It uses no live model or provider.

To exercise the instrumented Mem0-shaped fixture manually, start Studio and run the fixture in another terminal:

npm run engram -- dev
npm run engram -- run -- node examples/mem0-stale-correction/demo.mjs

Diagnose the answer

1. Open http://localhost:3100/?mode=incidents.
2. Select the recorded What city do I live in now? turn.
3. Enter Oakland as expected answer evidence.
4. Review why the stale San Francisco memory was selected.
5. Apply the proposed branch repair.
6. Replay the frozen turn.
7. Export the passing regression artifact.

Run the checked-in regression

npm run engram -- test \
  regressions/current-city.engram-test.json \
  --executor examples/mem0-stale-correction/regression-executor.mjs \
  --format github \
  --output engram-regression-report.json

The example is intentionally deterministic. It tests Engram’s incident workflow without claiming equivalence to a live memory provider or model.