Issue 191: an internal-only route was dropped by the proxy, and serving it naively would have made it public. The diagnosis records both, why "inside" is now told by the mesh rather than worked out by the proxy, and the release order.
ADR 0167 (accepted): a membership carries what its module receives and every machine's private-network address. The route proxy is the first reader.
ADR 0138, progressive insight of 2026-10-02: for a routed endpoint, the proxy is where internal reach is kept.
Designs 08 and 25: dated paragraphs saying the same.
Fix: mesh-catalog PR 211, then mesh-controller PR 207. Status stays located until they merge and are verified live.
records.py, index.py and cycle.py pass.
- **Issue 191**: an internal-only route was dropped by the proxy, and serving it naively would have made it public. The diagnosis records both, why "inside" is now told by the mesh rather than worked out by the proxy, and the release order.
- **ADR 0167 (accepted)**: a membership carries what its module receives and every machine's private-network address. The route proxy is the first reader.
- **ADR 0138**, progressive insight of 2026-10-02: for a routed endpoint, the proxy is where internal reach is kept.
- **Designs 08 and 25**: dated paragraphs saying the same.
Fix: mesh-catalog PR 211, then mesh-controller PR 207. Status stays `located` until they merge and are verified live.
`records.py`, `index.py` and `cycle.py` pass.
mesh-admin
changed title from Issue 191: a route with only an internal name is dropped as naming nothing to Issue 191 and ADR 0167: a membership carries what its module receives, and who the mesh is2026-10-01 23:48:38 +00:00
Issue 191's route proxy needs to know who the mesh is to serve an
internal name correctly, and the first fix had it work that out alone.
The membership on the bus now carries it, from the same list the filter
uses. ADR 0138 gains an insight that the proxy is where internal reach
is kept; designs 08 and 25 say how.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fix: mesh-catalog PR 211, then mesh-controller PR 207. Status stays
locateduntil they merge and are verified live.records.py,index.pyandcycle.pypass.68650cda5ftoe6b638e63cIssue 191: a route with only an internal name is dropped as naming nothingto Issue 191 and ADR 0167: a membership carries what its module receives, and who the mesh ise6b638e63cto28d53dcc28