Read the Docs redirect precedence when multiple rules match one path

Read the Docs supports project-level redirects configured in the dashboard, including exact-path and wildcard entries that map old documentation URLs to new versions or external targets. A documented gap is the evaluation order when several redirect rules could match the same incoming request path.

The uncertainty is whether rules are processed sequentially in dashboard order, ranked by pattern specificity, or resolved by an internal priority. Overlapping wildcard and exact rules can produce different destinations depending on which precedence model applies. The same logical path may also be reachable under versioned URL prefixes or custom domains, adding another layer of ambiguity.

Behavior may differ between the hosted service and self-hosted instances, and precedence is not guaranteed to remain stable across platform updates. The platform documentation does not define the ordering contract, and the dashboard does not expose an explicit priority field.

1. Which precedence model does Read the Docs apply when multiple redirect entries match the same path?
2. How do versioned URL prefixes and custom domains affect that ordering?
3. What observable signal should operators use to confirm the active rule?