jschoubben
702efca6bb
HQ held only the to-be. Every reader had to already know the system the decisions were about, and an as-is claim had nowhere to live except inside an intention. Adds 02-DESIGN/00-as-is — eleven documents written from the implementation and the operational record, not from intent, including the parts nobody would choose again. The two existing designs move under 01-to-be. Layers are declared in frontmatter and never mix: a design that ships does not move, its as-is counterpart is written, and both stand. Back-fills adr/0001-0014 for decisions taken in implementation and never recorded — the broker, the module abstraction, the mesh database, managed files, provisioning, migrations, the workspace removal, failing loudly, the constitution, application placement, linking, the employee model, the artifact, the three silos. Each marked reconstructed, dated from the history, and citing the evidence it was recovered from. The two existing records renumber to 0015 and 0016 so the ledger runs oldest first; 0017 extends 0015 to modules outside the core, principle only — the domain list is deliberately not invented here. how-we-build.md becomes the source of the mesh constitution, with a sync playbook, so the enforced copy stops being the only one that is true. Process becomes explicit: five playbooks, eight thin skills that defer to them, a repository map, and AGENTS.md with CLAUDE.md as its include. The five Observations become 04-ISSUES 001-005 where they can be owned and closed. 006 is new and uncomfortable: HQ is not indexed into the knowledge base. That claim is what decision 27 rests on, it was never checked, and the README now says so instead of repeating it. Also corrects the ADR index into something generated, the "02-DESIGN is empty" claim, the VISION.md pointer that did not survive the repo split, and a note asserting the symlink rule was contradicted — it was a misreading; the rule forbids hand-made links, the installer links by design.
66 lines
3.1 KiB
Markdown
66 lines
3.1 KiB
Markdown
---
|
|
status: accepted
|
|
date: 2026-06-04
|
|
deciders: jochen
|
|
reconstructed: true
|
|
---
|
|
|
|
# 7. 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
|
|
|
|
1. **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.
|
|
2. **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.
|
|
3. **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 0010](0010-applications-live-in-their-own-repository.md)
|
|
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`](../04-ISSUES/005-pipeline-test-harness-unbuildable/00-report.md).
|
|
|
|
## 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.
|