docs: ADR 0005 — dependency classes (runtime vs development-support)#21
Merged
Conversation
…ment-support) The xmBase-only rule constrains the deployment closure; family development-support components (xmViewer first) may be gated dev dependencies. Resolves the tension surfaced by xmNavigation's visualization tier: the support component's purpose is precisely to be used by domain components during development.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clarifies that the xmBase-only rule constrains the deployment closure (its actual rationale: no unused stacks for consumers, no release-cycle entanglement of behavior-critical layers), and registers a second class: development-support dependencies — family components like xmViewer may be depended on when the dependency is build-gated and provably absent from deployment. Division of labor stated: drawers of a component's types live with the component; the support component stays domain-agnostic. Resolves the doctrine gap surfaced during the xmNavigation visualization review.