Never delete does not mean keep everything active
Leaving all memory in the active layer grows boot cost forever and mixes stale guidance into current judgment. Preservation and activation are separate axes.
Vestige treats promote, demote, and archive as first-class retier operations. Bytes remain while loader and index roles change. The ledger explains where the trace moved and why.
A raw move changes only half the meaning
Filesystem mv can leave owning index lines, frontmatter tier, and links behind. Source lives under archive while the index still calls it core.
Retier combines destination policy, frontmatter, move, deterministic index maintenance, and semantic commit. New summaries requiring judgment remain for a live session.
Archive is a library, not a tomb
Archived memory remains searchable and visible in Trail as decision provenance. It leaves default boot and active recommendation, changing role without erasing existence.
Age alone does not justify archive. Read whether the trace is stale operational guidance or heritage explaining present identity. Age may create a candidate, never disposition.
Ask again what delete means
A Delete request may mean remove from active load, hide an accidental duplicate, or combine records. Most memory intentions resolve through archive or merge with provenance.
True erasure for law or leaked secrets needs an explicit incident contract above never-delete. Sharing a casual UI path lets exception consume the default.