Answer A-401: a newly watched branch starts from the forge at its head, as a clone does
This commit is contained in:
@@ -925,3 +925,17 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
writer every reader of the holders reads. It says each key so derived once, and when it stops being derived. The
|
||||
assignment graph's requirement resolution and the order waits keep reading holders from the holds alone; the post-G
|
||||
remarks take that up with the rest of the holders question.
|
||||
- **A-401** (live, the control-node 2026-11-14 21:5x: the assigner ended every proposal, since f1-circuits (watched on
|
||||
master), link2pay and photos (watched on nox-mesh) are held in no catalog graph of their branch; the gate writes
|
||||
`source.<branch>` only on a take-in of a merge on that branch (A-34), so a newly watched branch is never started; the
|
||||
operator, 2026-11-14 about 22:00: "by doing a git clone"; principles 2, 4 and 7, §15, §430, A-85, A-93) A watched branch
|
||||
starts from the forge, as a clone does. The gate, at its start and on each `registration-changed` of the seat
|
||||
`mesh-catalog`, writes `source.<branch>` for every watched branch the registrations name that no source key holds yet
|
||||
(§430, which wrote the default branch alone): each repository registered on it at the branch's head, asked of the seat
|
||||
`git`'s verb `branch`, the group left empty, and says `source-moved`; a repository whose head cannot be read is left out
|
||||
and said, and is added at the next registration change or by hand. Its tool `gate_source_start` (branch, why) does the
|
||||
same by hand through the hand-act log. A key it holds is never rewritten this way: from then on only a take-in moves it
|
||||
(A-34). The indexer takes a head the source names in from that head's merged message as before; a head with no merged
|
||||
message is read whole at that commit through the seat `git` (its tree and files), taken in as a merge whose changed
|
||||
files are every file of that tree, and computed as any other (A-93). So the branch keeps its first revision
|
||||
`branch.<branch>.1`, and its later merges follow the designed path.
|
||||
|
||||
Reference in New Issue
Block a user