jschoubben
e1febe8e0f
The consolidation left a sparse sequence -- 1, 4, 6, 7, 9, 10, 12, 15, 16, 18, 19, 25, 34, 35, 36, 37, 40, 42, 44, 45, 48, 49, 58 -- where the gaps were only the archaeology of what used to be there. Renumbered contiguously. Renames run in ascending order, so every target number is already free and no two files ever collide. The reference rewrite is one simultaneous pass rather than a sequence of replacements. Numbers moved into slots other numbers were vacating -- the node host went 37 to 16 while the lab went 16 to 9 -- so replacing one at a time would have cascaded and silently pointed things at the wrong record. Seven plain-text references survived the merges as prose rather than links, naming records that no longer existed: the enrolment token, the link boundary, what a declaration is, reachability, the repository structure. Each mapped to the consolidated record that now holds it. Verified rather than assumed: every [ADR NNNN](path) link now has matching text and target, checked across the whole repository, and the checker passes. Frontmatter `consolidates:` lists dropped -- they named records that are gone, and each consolidated record already says in prose what it absorbed.
3.1 KiB
status, date, deciders, reconstructed
| status | date | deciders | reconstructed |
|---|---|---|---|
| accepted | 2026-06-04 | jochen | true |
4. No workspace — each module is a standalone package consuming published dependencies
Reconstructed after the fact from the evidence cited below.
Context
Modules depend on each other, above all on the shared library every module builds against. A workspace was the obvious way to express that: sibling packages, resolved locally, one install at the root.
It produced a divergence that is worth stating precisely, because it is not obvious. In development, a workspace member importing a sibling resolves to that sibling's local source. In the pipeline, each module is built alone, from a clone, without its siblings present — so the same import resolves to the published version. The two environments were therefore building different code from identical source, and the failure appeared only in the pipeline, in a module that had not been touched.
Considered options
- Keep the workspace and make the pipeline replicate it — clone every module, build the graph. Rejected: it makes every build a whole-repository build, which is the cost the per-module pipeline exists to avoid, and it does not extend to modules in their own repositories.
- Keep the workspace and pin siblings to published versions. Rejected as the worst of both: the workspace's local resolution silently overrides the pin, so the divergence remains while looking solved.
- No workspace. Every module is standalone and consumes published dependencies. Chosen.
Decision
There is no workspace. Each module is an independent package that declares its dependencies and consumes them from the private registry, including the mesh's own shared library.
A cross-package change is therefore two steps: publish the producer, then consume it. The pipeline does the first on push and resolves the levels so that a module always builds against its dependencies' freshly published versions.
Consequences
- Development and the pipeline resolve imports identically. The divergence is gone by construction rather than by discipline.
- A module in its own repository is not a special case. It builds exactly as a module in the monorepo does — which is what makes ADR 0006 cheap.
- A cross-package change costs a publish-and-consume round trip. This is the real price, paid on every shared-library change.
- There is no repository-wide install and no repository-wide build. Anything that assumed one
broke, and one thing that assumed one has stayed broken: the end-to-end pipeline harness has
not built since this decision landed. See
04-ISSUES/005.
References
fix(noxflow): kill npm workspace, restore encryption inside PgAdminRepo(#240), 2026-06-04. The reason is recorded in the root package manifest, which still carries the note explaining why no workspace exists.- The divergence it fixed is named there: workspace members importing each other resolved to local unbuilt source in the pipeline.