EVERYDAY MEMORY
Keep it accurate
Correct, replace, forget, and answer conflicts. A memory you cannot correct is a liability.
flow correct <id> <text>- Save a corrected version and retire the old one in the same step. The old memory leaves recall, the history keeps both, and the old record says what replaced it.
flow supersede <old> <new>- Say that one memory replaces another, when both already exist. For the pair you spot while reading — where the correction was written last week and nobody ever connected them.
flow forget <id>- Remove a memory from recall, along with the facts drawn from it.
flow review- Memories a later note may have made out of date. Guesses, not decisions.
flow review keep <id> · retire <id>- Answer one: keep it as it stands, or retire it. Only a person can retire a memory.
Which one to use
| Situation | Use |
|---|---|
| A memory is wrong and you have the right version | flow correct <id> <text> — saves the new one and retires the old in one step. |
| Both versions already exist | flow supersede <old> <new> |
| It should not be in memory at all | flow forget <id> |
| Flow suspects two memories conflict | flow review, then keep or retire |
Retiring never deletes. The old memory leaves search, the history keeps both, and the old one says what replaced it. Facts drawn from it leave the knowledge graph too.
Who may change shared memory
- In a company workspace: the author of the memory, or an owner/admin.
- In a communal workspace: moderators. Members can challenge instead, and may always forget their own contributions.
- Only a person can retire a memory. Conflict detection only suggests.
flow forget removes a memory from recall; it is not legal erasure. For GDPR erasure of a whole scope, see Your data.