Principle 10: the module is the unit, never the repository #623

Merged
mesh-tools merged 2 commits from principles/module-is-the-unit into main 2026-11-16 10:35:38 +00:00
2 changed files with 4 additions and 7 deletions
+2
View File
@@ -28,6 +28,8 @@ add, sharpen or drop a principle in a pull request to this file.
9. **Depend on the contract, at the level it is interchangeable.** A module depends on a seat where the mesh means
more than one module to be able to fill the need, and on a module where only that module does; never on another
module's internals.
10. **The module is the unit.** Everything is done per module, never per repository. A repository is only where a
module's files are kept; a merge moves only the modules it changes.
How it is checked: the one code review of a milestone checks the code against these principles and the design's
shape; an answer to a develop question names the principle that settles it.
@@ -1258,10 +1258,5 @@ the principle that settles it, cited as "design 47 G A-n".
always for one module. Every fetch of a build seat names its module's directory; a fetch with no `dir` is refused,
naming its asker, and no step runs on a whole repository. Every caller that asks a fetch with no `dir` today names the
module it builds or checks, in the same change.
- **A-447c** (widens A-447b; the operator, 2026-11-16 about 11:32 CET: "everything in a pipeline should be module
based, not repo-based", "nothing is ever repo-based"; principle 7) Nothing in building, checking or delivering works
on a repository: every part works on one module. What it fetches, lays beside, chooses and runs as tests, computes as
digests, lints, builds, publishes, checks, judges and reports is the module's and what that module loads. A merge
is said for the modules it changes, and only those move. A repository is only where a module's files are fetched
from. A part that reads, chooses or judges anything of another module of the same repository is a fault of that part,
fixed in it.
- **A-447c** (principle 10, added 2026-11-16 at the operator's word: "nothing is ever repo-based") A-447b holds for
every part of building, checking and delivering, not only the fetch.