docs: ADR 0007 — charters vs gates - #33
Merged
Merged
Conversation
…unded) User principle folded in: module definition must not depend solely on existing consumers (they will change). Charters state each module's role forward-looking and veto wrong-home placements; the four criteria become build gates governing WHEN code is constructed/promoted, with incubate-in-the-consumer as the default until gates pass. The charter fixes destination, the gates fix timing.
3 tasks
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.
Folds in the design principle stated 2026-07-12: module definition must be forward-looking (consumers change and will change) while construction stays grounded. §1 restructured into module charters (role-based, define what belongs where eventually, veto wrong-home placements regardless of consumer counts) and build gates (the four criteria, governing when code is built or promoted), with incubate-in-the-consumer as the default until gates pass — the charter fixes destination, the gates fix timing, nothing is built before something needs it. Docs-only.