Rendered from docs/obligations/0062-a-relation-may-admit-a-document-and-an-anchor-and-no-rule.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

A relation may admit a document and an anchor, and no rule orders the two

Context

The base package declares traces_to with both governed_document and code_path at the target end. One target string can reach the identifier index and an anchor resolver, and nothing says which answer wins. Q4 rules that a target is an identifier and leaves the anchor case unordered.

Obligation

The corpus owes a stated order, so that a target which both resolvers claim has one reading.

Discharge

The engine reads the index first, then each anchor kind in declaration order. Where two anchor kinds claim one string, it reports a tie and binds neither. Spec 2 sets that precedent for two shelves of equal specificity. The index matches an identifier and never a path. A path to a typed document with an identifier binds to nothing, and the engine names the identifier to write (#1410). A path that reaches such a document through a symbolic link binds to nothing as well, and the engine names the same remedy (#1417).