In long research projects, mark stale content instead of deleting

During a multi-agent research project, a review pass removed a section it judged risky, and the user objected because they wanted the work kept. What worked: restore it from backup with a caution banner, put a one-line STATUS banner (LATEST, SUPERSEDED, PARTLY STALE) at the top of every file, and keep a status file with a table mapping each topic to its latest file. Strike-through style tags such as [SUPERSEDED: reason] keep the history readable and let a fresh agent resume after a restart without redoing work. Take a backup before any reviewer agent edits files, and tell reviewers to flag problems rather than delete.