Skip to content

docs(docs): A proposed ADR says who enforces a site's address policy behind an egress proxy - #54

Merged
sodre merged 1 commit into
mainfrom
t3/triage-foresight-46
Nov 22, 2026
Merged

sodre merged 1 commit into
mainfrom
t3/triage-foresight-46

Conversation

@sodre

@sodre sodre commented Nov 22, 2026

Copy link
Copy Markdown
Member

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: proposed

ADR 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 of main and each cites the ADR; #50, which builds the Gateway change, changes its status to accepted.

Evidence

Criterion Ticked Shown by
main holds ADR 0003 with status proposed yes git show HEAD:docs/adr/0003-the-egress-proxy-resolves-the-site-and-carries-its-address-policy.md
The glossary on main defines egress proxy yes grep -n -A2 'Egress proxy' GLOSSARY.md
The handbook still builds with no warnings yes python -m mkdocs build --strict

No 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.md on the branch head, which the squash puts on main: line 2 reads status: proposed.
  • grep -n -A2 'Egress proxy' GLOSSARY.md: the term, its definition and its _Avoid_ line, under "Gateway egress".
  • python -m mkdocs build --strict, from requirements-docs.txt in a fresh virtual environment: exit 0, "Documentation built in 0.25 seconds", no warnings. mkdocs.yml excludes /adr/, so the published handbook's pages are unchanged.
  • The CI, Sidecar mTLS and Native provider qualification workflows passed on the push of this commit.

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

…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
sodre marked this pull request as ready for review November 22, 2026 06:56
@sodre
sodre merged commit ae585cd into main Nov 22, 2026
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A builder finds the proposed ADR 0003 and the egress proxy term on main

1 participant