`doctor` and `status tangled` answered one question — can what I am about to do work — from the two ends of it, and only the first word said which end. They are `doctor local` and `doctor remote` now, in the vocabulary git spent thirty years teaching. `doctor` is a container and runs nothing itself, which is how every other family here works. Whether a knot answers is a fact about the knot, so it is asked once, by `remote`. `local` names the knot its origin resolves to and stops there. The surviving probe is also the one that outlives an index outage: it reads the knot from the repo's DID document rather than off the repo record, whose address only Bobbin can supply. The two routes look like duplication and are not. `local`'s `remote` row is `origin` now — one word cannot mean both the git remote a row is about and the end of the wire a sibling command is about. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Change-Id: Idebfd9047fe8d2a8aafa449917ec2229866b32d1