Design 47 H: H-A-143, a machine's composition across the watched branches

This commit is contained in:
2026-11-20 15:19:20 +01:00
parent 1c186e1a0e
commit 962e0af17f
@@ -679,3 +679,14 @@ Where two preparers disagreed, the chosen one is named.
further part as it does for a seat's events. Whether the manifest validator accepts `*` in `emits` is read, not
assumed: refused, that is a finding for H2 and the manager's `emits` stays until it is built. A seat event gets its
further part from its seat definition; a module event only from its manifest. P9, P3.
- **H-A-143 (a machine's composition across the watched branches, 15:20)** Met live at every pipeline since the clean
state: the composition step judges a machine at one branch's catalog revision, so ace misses f1-circuits (branch
master) and novox misses Link2Pay and photos (branch nox-mesh), both compositions fail "nothing provides", the
composer's search for culprits reaches its bound and every mover on those machines ends "could not run" (A-470b).
The rule is the one every reader of the catalog half already follows (G-12 §532, the bus module): a machine's
composition takes each module's manifest from the newest revision of the first watched branch that lists it, in the
registration's order (the repository's default branch first, then each branch `watch` added), the candidate's
revision replacing that branch's newest for the modules it moves; a module no watched branch lists is said as such in
the composition's reason, never silently dropped. The assignment of a module the catalog no longer holds (the retired
checker on novox) is removed by the assigner's own tool, written in the hand-act log, not by hand in its state. P9
(one rule per interaction), P3.