ADR-0022: Ask which knowledge notes to keep before archiving a project
Accepted
Status: accepted · 2026-10-25
Context
coach archive moved a project folder whole into 4.Archive. A concept note or a note with sparring history inside it would then leave 3.Resources and stop being sparrable (ADR-0018). kb-template's archive_project now lists suggestions in its preview: notes that look worth keeping (a concept note, sparring history, a note citing raw material, or one linked from outside the project), each with a target folder under 3.Resources and the reasons, and it takes keep to move those notes there first.
Decision
- Before the archive preview,
coach archivelists the suggested notes, each with the folder it would go to and why. - The learner chooses which to keep: numbers, Enter for all of them, or
none. The chosen notes go to their suggested folders. - The preview then shows the full plan, the kept notes moving into Resources and the rest of the project into the archive, and nothing moves until the learner confirms (ADR-0009).
- The filing port carries the suggestions and the
keeplist; the MCP adapter passeskeeptoarchive_project.
Alternatives
- Archive the project whole, as before. Simplest, but concept notes and sparred notes leave
3.Resourcesand can no longer be sparred. - Keep every suggestion automatically with
keep_suggested: true. No extra question, but kb-template's guesses decide what stays. - Show the suggestions and ask, chosen by the owner on 2026-10-25: one extra question, and the learner decides, as everywhere else in the CLI.
Consequences
- Archiving a finished project no longer buries the concepts and sparred notes made during it.
- Choosing a different target folder than the suggested one still needs Obsidian or
coach fileafterwards.