docs(evidence): reorganize Evidence Gateway guidance - #651
Conversation
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 79b9857e1f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2a415ced1a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Evidence Gateway does not consume this Relay-protected API. It uses its own configured authoritative | ||
| HTTP source and does not inherit Relay's authorization or policy model. |
There was a problem hiding this comment.
Preserve Relay as a fixed source option
For deployments that intentionally configure a Relay-protected read API as the fixed HTTP source, this now tells Relay tutorial readers that Evidence Gateway cannot consume the API they just built. The product boundary is that Relay authorization is not inherited, not that Relay is unsupported as a source; fresh evidence here is this page's new sentence denying consumption outside the already-commented architecture page.
AGENTS.md reference: AGENTS.md:L43-L45
Useful? React with 👍 / 👎.
What changed
evidence,evidencectl, andregistry-evidenceWhy
The public documentation mixed the old product name with a retired Relay-based topology. That made the navigation repetitive and described an architecture the current Evidence Gateway no longer uses.
Impact
This is a documentation-site change only. Runtime names, wire identifiers, schemas, CLI commands, and archived release history remain unchanged.
Validation
npm test(316 passed)npm run checkgit diff --check