Issue 122: the pattern is already on main, in five modules #122

2026-09-26T13:07:32Z

jschoubben commented

2026-09-26 13:07:32 +00:00

Follow-up evidence, and the reason the three module PRs were merged rather than held.

The question that decided it was whether merging them would set a precedent. It would not: five modules already on mesh-catalog's main branch carry a name belonging to this one mesh. The workflow automation module states its host, its protocol and a full absolute webhook URL as literals; the proxy and the builder each carry a complete clone URL for a repository on this mesh's own forge, scheme, host and port included.

That changes what the issue is for. Refusing three changes would have bought nothing — there is no version of this catalogue today that does not name the mesh it was written in — while leaving two live services misbehaving. A mechanism is the only thing that removes any of them, which is what the open questions ask for.

mesh-catalog #55, #58 and #59 are merged on that reading, each with a comment saying so and pointing here. Checks: cycle 286 documents, the chain holds; records 104, all passed; index current.

Follow-up evidence, and the reason the three module PRs were merged rather than held. The question that decided it was whether merging them would set a precedent. It would not: **five modules already on mesh-catalog's main branch carry a name belonging to this one mesh**. The workflow automation module states its host, its protocol and a full absolute webhook URL as literals; the proxy and the builder each carry a complete clone URL for a repository on this mesh's own forge, scheme, host and port included. That changes what the issue is for. Refusing three changes would have bought nothing — there is no version of this catalogue today that does not name the mesh it was written in — while leaving two live services misbehaving. A mechanism is the only thing that removes any of them, which is what the open questions ask for. mesh-catalog #55, #58 and #59 are merged on that reading, each with a comment saying so and pointing here. Checks: cycle 286 documents, the chain holds; records 104, all passed; index current.

jschoubben added 1 commit 2026-09-26 13:07:32 +00:00

Issue 122: the pattern is already on main, in five modules e399a2c148

Asked whether merging the three reviewed changes would set a precedent. It would not: five modules
already carry a name belonging to this one mesh — a workflow module stating its host, protocol and
absolute webhook URL, and two carrying a full clone URL for a repository on the mesh's own forge.

That changes what the issue is for. There is no version of this catalogue today that does not name
the mesh it was written in, so refusing three changes buys nothing and a mechanism is the only thing
that removes any of them. The three were merged on that reading, each PR saying so.

jschoubben merged commit 859ff49ff2 into main

2026-09-26 13:07:43 +00:00

jschoubben deleted branch issue/122-the-instances-already-on-main

2026-09-26 13:07:43 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#122