Use a uniquely prefixed key
The production test used course_5_output_style and removed only that exact key. Unrelated internal memory remained unchanged.
Separate two memory systems
| System | Use |
|---|---|
| KV memory | Exact facts a human sets and controls. |
| Graph memory | Knowledge accumulated through the runtime engine. |
Store one exact preference
armaraos memory set <AGENT> course_5_output_style "three short bullets"
Read and list the intended key
armaraos memory get <AGENT> course_5_output_style --json
armaraos memory list <AGENT> --json
The full list also exposes unrelated internal keys and local paths. Select and redact rather than publishing the complete store.
Use KV for controlled facts
Timezones, output formats, and project labels fit KV memory because the intended value is exact.
Delete only the exact key
armaraos memory delete <AGENT> course_5_output_style
Verify absence
armaraos memory get <AGENT> course_5_output_style --json
Key not found is the expected final state.
Keep a second copy of important facts
KV has no export command. Record important values elsewhere before deleting them.
Check it / complete another disposable round trip
End with key not found.
Use another uniquely prefixed key and leave all unrelated entries untouched.
KV deletion is immediate and permanent. Full list output can expose internal state and paths, so select and redact before sharing it.
Troubleshooting for this sitting
| What you see | Likely cause | What to do |
|---|---|---|
| Key not found before set | The key does not exist. | Set the prefixed key first. |
| Unrelated keys appear | The store includes internal entries. | Filter output and do not delete them. |
| Delete cannot be undone | That is the contract. | Keep a second copy. |
| Name works here | KV supports name or ID. | Do not generalize to other families. |