From be0bf716513b3117d554fa619f4c60d8e3d4279e Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 10:32:23 +0100 Subject: [PATCH] Design 47 H: H-A-130 the start of a take-in read by the verb; H-A-131 a module-less repository and the gate Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 305e294b..dc591420 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -576,3 +576,14 @@ Where two preparers disagreed, the chosen one is named. P1) and takes it in as a heard `source-moved` of that revision would, when its view holds no revision of the branch at or above it; it keeps binding the consumer on `registration-changed` as before. No timer. A fault that reports nothing wrong while nothing moves is P3's failure. Fixed under H1 (playbook 08) before step 5.9 can finish. +- **H-A-130 (the start of a take-in read by the verb, 10:33)** The seat's `source` answer carries no `start`. The + take-in from it uses start true exactly when the indexer's view holds no revision of that branch, false otherwise + (movers against the newest kept): the first take-in's entries are the base later ones are held against (H-A-19), and + a first take-in with movers would pin and start pipelines for every module (P3). The answer names every repository of + the revision; all are taken in as heads (the movers are the fingerprint changes alone, so the outcome is the event's). + Adding `start` to the seat's answer is not built here (P7). +- **H-A-131 (a repository with no module is merged by the gate too, 10:34)** Met live: the new gate refuses hq's pull + request 796 ("its base main is no watched branch") because a watched branch is a registration's and hq registers no + module; the forge's own tools refuse a merge by design (ADR 0266). Until hq has a registration of its own (a module + whose unit step is its checks, P5: everything ships the same way; built after the clean state), hq's lead answers + stay on their branches, pushed, and are cited by branch. Decided as a design detail; told to the operator.