jochen
6e3373c879
0113 — the plaintext claim was false under its own mechanism: handing a provider's answer to the controller puts every secret on the broker and in the controller in the clear. The provider now seals each secret field itself, to the consumer node's public key the mesh hands it, and the controller carries sealed fields it cannot open. That is stricter than today, where the controller holds every minted credential in the clear. Option 3 (plaintext to the controller) is recorded and rejected. The foundation exception now covers root-secret rotation (0085) and forms like the broker admin's hash, so no phase claims to remove the broker's bootstrap step. To-be 24 and 13 are named among what it amends. 27 — resolution is consistent with 0110: co-location and the only provider apply only where no seat delivers the provision, so an unheld seat is refused even with one provider. The secret-field rule now matches 0086 exactly (a declared env-file, never a container environment value). The seat placeholder is the controller's, and the one module reading it moves to a host port. Contracts are held by the controller and written down in phase 1, so they can be checked; every rule has a check. An operator's secret is still the operator's, with the vault as custodian. Which seats a module holds is listed as not settled. 0110 — the unheld-seat-with-one-provider case and the one-answer-for-everyone rule have checks; the claim about moved manifests is corrected. 26 — the table governs and the code catches up, not the reverse; scope and capacity agree with the glossary; moving a seat is described as it really is today. 0112 — aligned with 27, and lists 0049 and 26 among what it changes. Issue 118 is renumbered 119: another branch took 118 first. 'Control-plane' is gone from 0110 and 0111.
5.4 KiB
topic, status, date, deciders, reconstructed, extends
| topic | status | date | deciders | reconstructed | extends |
|---|---|---|---|---|---|
| building it | accepted | 2026-09-25 | jochen | false | 0069-a-module-is-a-repository-and-a-path.md |
111. A build source is on the mesh's git seat, or it is an external repository
Context
ADR 0069 made a module a repository, a path and a
ref, and the controller records all three against the module so it can rebuild it and say when
its source has moved ahead. The repository is recorded exactly as a person typed it. build <repository> hands the string to a build machine, which runs git clone on it, and the same string
becomes the module's recorded source.
So a self-hosted forge's address is written into every module built from it. The mesh runs its own forge, and most of what it builds lives there. Every one of those modules carries the forge's scheme, host and port in its recorded source. Move the forge to another machine, or change the port it is published on, and every recorded source is stale at once. Nothing notices until a rebuild fails to clone.
And nothing names the mesh's git at all. gitea serves git over HTTP and over SSH, and the mesh's
vocabulary contains neither. No provision, no serves, no seat, as the forge survey
(research 013) found. The only trace
is a label on its public route, which the mesh is explicitly not meant to interpret.
External repositories are ordinary, and must stay so. An application the mesh hosts may live on a public forge. Building it from its URL works today and must keep working unchanged.
Considered Options
1. Keep recording literal URLs. Rejected. It is the problem: the forge's address copied into every module built from it.
2. Recognise a self-hosted source by matching its URL against the forge's current address. Rejected. It infers the kind of source from the shape of a string, and the inference fails in the one case it exists for: after the forge moves, old URLs no longer match anything.
3. Two explicit forms: a repository on the holder of the git seat, or an external URL. Chosen.
Decision
The mesh has a git seat. It is mesh-scoped and delivers the git provision, per
ADR 0110. Its holder provides git,
serving how a repository on it is cloned: the scheme and the port. gitea claims it.
A source is on the git seat, or it is external, and the mesh records which.
build --self <owner>/<repository>builds from a repository on the seat's holder. The recorded source is the repository's path on that holder, and the seat it is on. It never contains an address. At the moment of building, the controller composes the clone URL from where the holder runs and what it serves forgit, so a moved forge changes nothing recorded.build <url>is unchanged: an external repository, recorded and cloned exactly as given. GitHub and GitLab are the ordinary cases.
An unheld seat refuses self-hosted builds and nothing else. With nobody holding git, build --self is refused, naming the seat and saying what would hold it. External builds are unaffected. A
mesh without a forge of its own builds from external repositories only, and says so rather than
failing to clone.
The build machine is not told the difference. It receives a URL either way. Composing the URL is the controller's job, because only the controller knows where the seat's holder runs.
Consequences
- The controller's inventory gains a column saying which seat a source is on. It is empty for every module recorded before this, which is correct: they were all recorded as literal URLs.
build,build --behindandbuild --dry-runresolve a seat source before asking a builder. The recorded source keeps the seat form; the build log keeps the URL that was actually cloned, because that is what happened.- gitea claims
gitand provides it, serving HTTP clone on its web port. - Not decided: credentials for private repositories. The mesh's own repositories are public, and
clone without one. A private repository still works only if the build machine's own git
configuration authenticates, exactly as before. Delivering a clone credential through the
gitprovision's grant is the obvious next step, and it is its own decision. - Not changed: modules already recorded from the forge keep their literal URLs until they are
rebuilt with
--self. Rewriting them in place would be the URL-matching this record rejects.
How it is checked
| Rule | Checked by |
|---|---|
| A seat source records no address | A controller test resolves a seat source and asserts the recorded repository is the path alone. |
| The URL comes from the holder | A test composes the clone URL from a holder's node address and served git scheme and port, and a second where the port was moved on the node. |
| An unheld seat refuses self-hosted builds only | A test with no holder: --self is refused naming the seat; an external URL passes through unchanged. |
References
- ADR 0069: a module is a repository, a path and a ref
- ADR 0110: seats, and a seat delivering a provision
- Research 013: git is served and declared nowhere
mesh-controller cmd/mesh-controller/build.go,internal/builder/builder.go