# Cursor Rules Deprecation Policy

**Last Updated:** 2026-04-03

This policy defines safe cleanup semantics for rule and guidance evolution.

## Status Labels

Use these labels in maintenance docs/changelogs:

- `active`: current source of truth
- `pointer`: thin routing file that points to canonical docs
- `archive`: historical context kept for auditability
- `deprecated`: should not be used for new work; scheduled for archive/removal

## Safe Deprecation Workflow

1. Identify replacement SSOT (rule/doc/skill).
2. Add migration note in active index docs.
3. Update skills and active routing docs first.
4. Run `make cursor-integrity`.
5. Mark old artifact `deprecated` and move to archive index.
6. Remove only after one wave passes with no regression in golden tasks.

## Guardrails

1. Never remove active guidance without a discoverable replacement path.
2. Never break `global.mdc` single always-apply contract.
3. Avoid big-bang removals; ship by waves.
4. Preserve historical traceability via archive index entries.