When an assertion is retracted (e.g. via CR-2026-144's move feature, or any other retraction path), the backend correctly records the retraction event with a rationale — confirmed directly against the database. But the Memory room's frontend only renders held and settled sections. There is no surface showing a retracted assertion or why it was retracted. An Operator cannot see that a note was moved, or the reason, without a direct database or API query.
The seed commits to "corrections preserved, not smoothed" — superseded assertions remain in memory as corrections, trajectory preserved alongside destination. The backend honors this. The frontend does not expose it. The correction exists but is invisible to the person it should inform.
Recorded. Not scheduled. Should be considered before further work that relies on retraction being a visible, trustable action to the Operator.