Repository navigation
docs(docs): A proposed ADR says who enforces a site's address policy behind an egress proxy - #54
Merged
Merged
Conversation
…hind an egress proxy Adds ADR 0003 as proposed and the glossary term "egress proxy". On a route through the operator's egress proxy the Gateway sends the site's name and resolves nothing, so name resolution and address policy move to the proxy. The decisions come from the triage of #46 and bind the spec in #49, whose first pull request accepts the ADR. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
sodre
marked this pull request as ready for review
November 22, 2026 06:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #53
Summary
Nothing changes for anyone using the product. The repository gains a proposed decision record on how the Gateway will reach a protected site through an operator's egress proxy, and the glossary term for it.
GLOSSARY.md # + "Gateway egress" section: Egress proxy docs/adr/ +└── 0003-the-egress-proxy-resolves-the-site-and-carries-its-address-policy.md # status: proposedADR 0003 holds the decisions the owner made while triaging #46: on a route through the egress proxy the Gateway sends the site's name and resolves nothing, so name resolution and address policy move to the proxy, and the Gateway never falls back to a direct connection. It is
proposed, so it binds nothing yet. The tickets of spec #49 are built from fresh checkouts ofmainand each cites the ADR; #50, which builds the Gateway change, changes its status toaccepted.Evidence
mainholds ADR 0003 with statusproposedgit show HEAD:docs/adr/0003-the-egress-proxy-resolves-the-site-and-carries-its-address-policy.mdmaindefines egress proxygrep -n -A2 'Egress proxy' GLOSSARY.mdpython -m mkdocs build --strictNo new test or guard: the change is two documentation files.
git show HEAD:docs/adr/0003-the-egress-proxy-resolves-the-site-and-carries-its-address-policy.mdon the branch head, which the squash puts onmain: line 2 readsstatus: proposed.grep -n -A2 'Egress proxy' GLOSSARY.md: the term, its definition and its_Avoid_line, under "Gateway egress".python -m mkdocs build --strict, fromrequirements-docs.txtin a fresh virtual environment: exit 0, "Documentation built in 0.25 seconds", no warnings.mkdocs.ymlexcludes/adr/, so the published handbook's pages are unchanged.Not run: nothing
Merge Danger
Door: two-way. A revert removes the ADR and the glossary section; nothing depends on them until #50 is built.
Blast Radius: documentation only.
The merge changes no source, image or configuration. It touches
docs/, so the handbook workflow rebuilds the handbook, with the same pages as before.Reviews
No review ran: 0 findings
The owner asked for this pull request to be opened and merged. The ADR is
proposed, and the pull request of #50, which accepts it, gets the full review.Tracking
Epic: E2 Reach protected sites through an operator's egress proxy
Spec: #49 Reach protected sites through an operator's egress proxy
Ticket: #53 A builder finds the proposed ADR 0003 and the egress proxy term on main
Flag: none
🤖 Generated with Claude Code