Resolve the target BEFORE the first domain-modeling action — question, fact-lookup, or write; not merely before the first doc write.

Target = the current repo, unless an explicit signal names another repo. Signals (detecting them requires no registry read):

The user names a repo by slug or path.
The primary artifact under work — the issue, PR, plan doc, or wayfinder map being grilled — belongs to a visible owner/repo that is not the current repo. A repo merely mentioned in conversation is NOT a signal. If several artifacts are in play, the one the user's latest instruction acts on is primary.
A wayfinder map's ## Notes names a target repo.

Only after a signal fires, resolve the local clone: the AFK registry (.agents/afk-pipeline/REGISTRY.md) if present, else known checkout roots (~/dev/code/<repo>), else ask. Never silently fall back to the current repo when a signal named a repo you can't resolve.

Safe default in orchestration dirs: if the session sits in a profile/orchestration workspace rather than the artifact's own repo and no signal has fired, ask for the target instead of assuming the current repo — a profile dir is almost never where domain docs belong. Exception: when the domain doc under work is the profile's own glossary, the profile IS the target.

Announce the resolution before the first question ("Maintaining the domain model for <repo> at <path>" / "…for the current repo") and treat it as a confirmation point — proceed only if the human doesn't contradict it.

When the target is NOT the current repo, this resolution re-orients the whole session: