Why public docs need owned raw routes

# Why public docs need owned raw routes

Public docs are not just pages for people to read in a browser.

They also become inputs for:

- copy-and-share flows
- grounded retrieval
- AI handoff actions
- export and archival workflows

That only works cleanly if the raw content lives behind routes we control.

## The problem with private-repo assumptions

If public pages depend on GitHub raw URLs from a private repository, the
experience breaks immediately for anyone outside the repo boundary.

Even when the page itself is public, the supposed "raw" source becomes a dead
end.

## The stronger posture

The stronger posture is simple:

- public page
- public raw route
- one owner-controlled origin

That keeps copy, export, and AI handoff behavior inside the real public
contract instead of leaking private authoring assumptions into the surface.

## Why this matters for AI too

Third-party AI tools do not all fetch public URLs the same way. Some are
blocked by crawler rules, some refuse raw-file fetches, and some truncate
context.

Owned raw routes do not solve every AI problem, but they give us a stable
public source that our own systems and users can rely on.