The site publishes the repository's markdown

Placing the site's content root at docs/ made every file in that directory a published page, chosen by an autogenerated sidebar rather than by anyone. The boundary arrived as a side effect of a generator's configuration. Developer documentation also sits outside that directory — package READMEs, the contributing and security guidance, and the rules an agent works from are all written for the same reader as the design record.

So the published surface is the repository's markdown. Splitting it at one directory sorts a reader's material by where a file happens to sit rather than by what it says, and it lets a claim hold one home in the repository while having none on the site.

Rejected: an allowlist naming the published documents. It is a second list beside the corpus it describes, and the copy is the one nobody updates — the same shape six scanners were converted away from when they stopped keeping their own extension lists and started asking git. Rejected also: publishing docs/ alone, which is the boundary that arrived by accident.

The duplication gate follows this surface rather than lagging it, since one claim having one home is a property of what is published.

What a sidebar offers is a separate question from what exists at a URL, and it is answered by The site navigates less than it publishes.