archive

# archive — Retire Completed Plans Move completed cycle plans out of the active set. **Never delete** — archive. ## Doc Paths | Doc | Path | | ------------ | --------------------------------- | | Active plans | `docs/plans/` | | Gap-report | `docs/plans/<plan>.gap-report.md` | | Archived | `docs/plans/archived/` | --- ## Pipeline ### 1. Resolve which plan(s) - If a plan file is named in `$ARGUMENTS`, archive that one. - Otherwise list the plans in `docs/plans/` (excluding `archived/`) and ask the user which to archive. ### 2. Completion check Before moving, verify each plan is actually complete. **Warn and ask to proceed** (don't hard-halt) when any of these are unfinished: - the plan doc's "Gaps surfaced during execution" section has **unresolved entries**; - a companion `docs/plans/<plan>.gap-report.md` exists with **open** rows (a legacy autopilot gap-report, un-reconciled); - an **execute run journal** (mempalace room `runs`, drawer `<plan>`) is not marked complete; - an **active plan** under `docs/plans/` (excluding `archived/`) lists this plan in its `requires:` frontmatter — archiving it out from under a dependent plan; - a blueprint doc named in this plan's `covers:` frontmatter is **not** `implementation: complete` — the plan is being retired before what it covers is fully built. Surface what's outstanding and let the user decide whether to archive anyway. Skip the run...