The catalogue moves out, to novox/mesh-catalog #1

2026-09-02T22:15:58Z

jschoubben commented

2026-09-02 22:15:58 +00:00

The modules the mesh runs lived under examples/modules/, which framed the real catalogue as illustrations of a control-plane package. They're neither examples nor the control plane's — they're the mesh's own catalogue, now in novox/mesh-catalog (30 manifests, flat under modules/), consumed as a build source like any other.

The engine stays here (internal/catalogue): the control plane owns the manifest contract; the data doesn't belong beside it. No runtime code referenced examples/modules/ — only two tests did.

Removed with the manifests: examples/modules/modules_test.go and internal/catalogue/parseall_test.go, which validated the example manifests against the parser. That validation logically follows the catalogue to mesh-catalog, but it imports internal/catalogue, so re-homing it needs the parser exported from internal/ first — a deliberate follow-up, not done here (it's a public-API decision for the control plane). Until then the pipeline is the gate, and internal/catalogue's own inline tests still cover the parser. go build ./... and go test ./... are green.

Answers novox/hq ADR 0030's open tier-4 question — where the catalogue lives — in favour of one flat mesh-catalog repository (the drop of domain grouping in favour of seats/claims/tags is what makes flat the right shape).

https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

The modules the mesh runs lived under `examples/modules/`, which framed the real catalogue as illustrations of a control-plane package. They're neither examples nor the control plane's — they're the mesh's own catalogue, now in [`novox/mesh-catalog`](https://git.novox.be/novox/mesh-catalog) (30 manifests, flat under `modules/`), consumed as a build source like any other. The engine stays here (`internal/catalogue`): the control plane owns the manifest contract; the data doesn't belong beside it. No runtime code referenced `examples/modules/` — only two tests did. **Removed with the manifests:** `examples/modules/modules_test.go` and `internal/catalogue/parseall_test.go`, which validated the example manifests against the parser. That validation logically follows the catalogue to mesh-catalog, but it imports `internal/catalogue`, so re-homing it needs the parser **exported from `internal/`** first — a deliberate follow-up, not done here (it's a public-API decision for the control plane). Until then the pipeline is the gate, and `internal/catalogue`'s own inline tests still cover the parser. `go build ./...` and `go test ./...` are green. Answers `novox/hq` ADR 0030's open tier-4 question — where the catalogue lives — in favour of one flat `mesh-catalog` repository (the drop of domain grouping in favour of seats/claims/tags is what makes flat the right shape). https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

jschoubben added 1 commit 2026-09-02 22:15:58 +00:00

The catalogue moves out, to novox/mesh-catalog f12450d61a

The modules the mesh runs were under examples/modules/, which framed
the real catalogue as illustrations of a control-plane package. They
are neither examples nor the control plane's — they are the mesh's own
catalogue, and they now live in their own repository (novox/mesh-catalog),
consumed as a build source like any other.

The engine that reads them stays here (internal/catalogue): the control
plane owns the manifest contract; the data does not belong beside it.

Removed with them: modules_test.go and parseall_test.go, which validated
the example manifests against the parser. That validation logically
follows the catalogue to mesh-catalog, but it imports internal/catalogue,
so re-homing it needs the parser exported from internal/ first — a
deliberate follow-up, not done here. Until then the pipeline is the gate,
and internal/catalogue's own inline tests still cover the parser.

Answers novox/hq ADR 0030's open tier-4 question — where the catalogue
lives — in favour of one flat mesh-catalog repository.

Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

jschoubben closed this pull request

2026-09-05 01:19:25 +00:00

mesh-tools referenced this pull request

2026-10-18 22:25:26 +00:00

An approved merge into a repository nothing is built from asks its modules' first builds (issue 1146) #386

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#1