novox/hq
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request 'Issue 122: count it properly — 30 of 71 definitions name this installation' (#128) from issue/122-the-census into main

Browse Source
This commit was merged in pull request #128.
This commit is contained in:
jschoubben
2026-09-26 15:09:17 +00:00
parent 5db79cd168 d5a4cb0d4f
commit 1012fff607
1 changed files with 22 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
04-ISSUES/122-a-module-cannot-ask-for-its-own-public-name/00-report.md
+22
View File
@@ -30,6 +30,28 @@ automation module, whose environment file states its host, its protocol and a fu
URL as literals; two more — the proxy and the builder — carry a complete clone URL for a repository URL as literals; two more — the proxy and the builder — carry a complete clone URL for a repository
on this mesh's own forge, scheme, host and port included. on this mesh's own forge, scheme, host and port included.
**Counted properly, 2026-09-26.** The five were what a first look found. A sweep of all 71
definitions, for values that could only be true of one installation:
| What is named | Occurrences | Modules |
|---|---|---|
| A public domain, or a name under one | 49 | 26 |
| The node's own name | 58 | 19 |
| A routable IP address | 12 | 1 |
| An absolute path on the machine | 798 | 70 |
| An email address | 0 | 0 |
The path row is [issue 119](../119-a-module-definition-decides-where-its-files-live/00-report.md),
counted again and grown. The rest is this issue. **Thirty of the seventy-one definitions name this
installation** in one of the first three ways, and the worst single case is not a domain at all: a
mail module states the node's own public IPv4 as the address it trusts a real-IP header from, so a
node that moves, or gains a second address, silently stops attributing mail to the right sender. A
private subnet, the mail domain, the site name and the administrator's domain sit in the same block
of values.
Two upstream resolvers are excluded from the count deliberately: naming a public DNS service is a
policy default, true of any mesh that wants it, not a fact about this one.
So the three under review are the visible edge of a pattern the catalogue already follows, which So the three under review are the visible edge of a pattern the catalogue already follows, which
changes what this issue is for. It is not a matter of refusing three changes; there is no version of changes what this issue is for. It is not a matter of refusing three changes; there is no version of
this catalogue today that does not name the mesh it was written in, and a mechanism is the only this catalogue today that does not name the mesh it was written in, and a mechanism is the only