# Phase 10 eligibility handoff

**NO-GO for broad cleanup or deletion. Phase 10 was not started.** All 33 routes and 57 preservation contracts remain in scope; 56 PARTIAL and C11 DEFERRED are qualification states, not permission to remove functionality.

| Candidate | Eligibility / required proof | Preserve |
|---|---|---|
| Duplicate initial reminder read (P9-PERF-01) | Candidate for a separately scoped shared-owner change after measuring benefit and independently exercising shell/Dashboard loading, failure, refresh and account disposal | Notification counts, reminder rules, Dashboard widgets and failure recovery |
| Legacy `/kanban`, `/applications/:id`, `/correspondence/review` | Keep aliases. No deletion eligibility without reader/bookmark/extension migration evidence and agreed compatibility policy | Query/hash, target section and identity/ownership boundaries |
| Legacy Job/Application schema (RD26) | Ineligible until expand/verify/contract and intended-provider migration, all readers/writers, rollback/restore are proven | IDs, relations, submissions, binaries, historical records |
| Dashboard/report calculation or Board optimization | Candidate only after an agreed measured budget identifies a bottleneck; retain complete membership and accessible alternatives | All filters, sorts, statuses, report definitions, nine-widget catalogue and owner/revision settings |
| Shared UI consolidation | No demonstrated need for a new framework. Any extraction requires caller census and error/loading/dirty/focus/localisation preservation | MUI/theme/router/current state/rendering and fixed CV geometry |
| Old tests or evidence | No deletion based on passing new tests. Keep original failures, fixture semantics and historical acceptance | Original PDF oracle, limits, auth guards, no retries/skips replacing failures |
| C11 / P5-13 / new integrations | Ineligible for cleanup activation. Separate model/provider/product qualification remains required | Withheld endpoints, review-before-apply and canonical/variant boundaries |

RD21 needs a separate data-integrity work item before unqualified acceptance: [concurrent-save contract issue](../p9-04/RD21_CONCURRENCY_ISSUE.md). It spans server contracts, callers, transactions and recoverable conflicts; a last-minute client-only guard cannot provide atomic safety. Creation-intent idempotency and canonical-write/later-Identity partial commits must be assessed explicitly.

Before any future cleanup: establish a clean directly verified remote baseline, agree exact candidate scope, link affected preservation IDs and callers, reproduce the problem, retain a rollback path and run the relevant tests plus full regression. Actual human/provider/document/infrastructure gates in [RISKS](../RISKS.md) remain independent of cleanup eligibility. No production operation is authorised by this handoff.