update-memory

• SKILL.mdcore · 8,860 bytes

# Update memory

## Goal

Memory stays consistent with the owner's latest words, so a request never applies two entries that disagree. Every change leaves a trail: the old entry, the new entry and the link between them, because the owner may ask why a rule changed, and because a superseded entry is the evidence that the old behavior was once wanted. Nothing is deleted, renumbered or reordered, since ids are cited in tests, dispositions and reports, and a deleted id breaks every citation. Operations are small and named, supersede, retire, confirm, narrow or leave, so a reader can see what happened from the metadata line alone. A confirmation is recorded too, because an entry confirmed by a correction twice is an entry that is not taking effect, and that signal is what triggers a new check. The non-fact memory types, failures, decisions, open questions, scope, glossary, pointers and workflows, are appended here in their own formats so that the next request can load them by type. The measure of this skill is that memory never holds two active answers to the same question.

## Objective

Find every existing entry the new information touches, by searching the fact files and the memory files for the subject, the artifact kind and the ids the feedback names. Decide one operation per entry from the five below, with leave as the default when nothing changes. Apply the operation by editing only the metadata line of the old entry and, when a replacement is needed, appending a new entry at the end of the file. Append any failure, decision, open question, scope line, glossary term, pointer or workflow the new information implies, in its type's format from the memory map. Inside feedback handling, apply operations only within the feedback-update subagent's own files and report the rest for the orchestrator. Report every id touched with its operation and reason, so the request report and the disposition can cite them.

## Tasks

1. Find the entries the new information touches. Grep `facts/` and `memory/` for the subject, its synonyms, the artifact kind and every id the feedback names, and list each candidate with its file and current status. Skip entries that are already superseded or retired; they are history.
2. Pick one operation per candidate: supersede, retire, confirm, narrow or leave, by the definitions below. Write the reason in a few words while deciding; the reason goes on the metadata line or in the report.