- Status
- NEW RESEARCHED DESIGN; not deployed
- Reviewed
- 2026-09-12
- Nature
- library engineering view
- Priority
- P1_IF_APPLICABLE
- Accountability
- R08, R01, R25, R26
Question
What happens to each old URL, and is the migration reversible?
Nodes
Old URL; Hop; Destination; Release; Rollback mapping
Relationship sketch
- old URL → redirect hop
- final URL → intended replacement
- mapping → release version
Evidence inputs
Authorized redirect map, actual HTTP observations, content equivalence decisions, backup mapping.
Implementation
Check loops, long chains, deleted destinations, and mismatched content. Treat redirect changes as authorized production changes with rollback; do not silently replace all missing pages with the homepage.
Acceptance checks
- No loop in approved redirect paths
- Every moved important URL has a reviewed outcome
- Rollback restores the previous mapping
Do not infer
An HTTP redirect does not prove the destination inherited a particular ranking.
Publication boundary
Redirect behavior public; migration control records private.
Source basis
S17, S41. See Research/sources.json. Sources support the primitives or named technology. The organization, labels, actions, and acceptance contracts in this catalog are this library's design, not claimed provider requirements.
