Design 47 H: H-A-262, a module that enters the trunk's module graph is registered at its take-in
This commit is contained in:
@@ -1503,3 +1503,12 @@ Where two preparers disagreed, the chosen one is named.
|
||||
folds into the first pass's keeping need: the first keeping keeps the first pass's revision, then removes. (2) The
|
||||
full-store verdict stays the pass's own: a pass reads the store's fill (one listing) before it writes, so no want is
|
||||
written for a revision that does not fit (G §181). P2 (a want names a kept revision), P4.
|
||||
- **H-A-262 (a module that enters the trunk's module graph is registered at its take-in, 12:58)** Met live: four
|
||||
contracts modules added after the registrations' seed were never registered, so a pipeline's steps for them wait
|
||||
on a registration nobody asked (A-327) with no bound and nothing said beyond a journal line. The indexer registers
|
||||
a module the moment it enters a watched trunk's module graph (the operator, 2026-11-14: a module in the module
|
||||
graph is a registration): the first watched branch, the manifest's path, the policy of its repository's other
|
||||
modules (else the default), no ask (the merge that added it was the operator's word), saying registration-changed
|
||||
so the waiting steps place; a module that leaves the graph keeps its registration until the operator's word. The
|
||||
pipeline runner raises the finding registration-missing (scope module) while any mover waits on one. P4, P2,
|
||||
ADR 0666 §2 read with the operator's rule.
|
||||
|
||||
Reference in New Issue
Block a user