Plan H: the operator's answers of 01:10 (stale data goes, one take-in one pipeline and none in parallel, hand placement yes; groups still open)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
@@ -291,6 +291,19 @@ at all. Before any code, `hq-design-writer` writes these as design lines in this
|
||||
4. **The one hand placement** of milestone H1 at the operator's terminal, one command at a time as before, after
|
||||
which no pack is run again except the ones this plan names. Recommendation: yes; it is what the operator offered.
|
||||
|
||||
**The operator's answers (2026-11-20 about 01:10 CET).** Question 2: "I don't care about old data at this moment, I want
|
||||
a working mesh again": the stale state goes. Question 3: "for my part, pipelines don't exist, or a group of commits
|
||||
form one big pipeline, but parallel pipelines sounds like a very bad idea": no two pipelines run at once, and one
|
||||
take-in is one pipeline (design 47 G §44 already says it for a group: one source revision, one pipeline per watched
|
||||
branch; the single commit is the case of one member); the setting of item 7 keeps the bound at one by its default and
|
||||
the design says serial. Question 4: "I don't mind doing hand placements": yes. Question 1: the operator's first idea was a
|
||||
build plan and a deploy plan per change (ADR 0238 §2, "one commit, one change plan", the glossary's *delivery plan*,
|
||||
deleted at release 6 of ADR 0429 and replaced by ADR 0666's pipelines per module ordered by edges, from research 086);
|
||||
what remains open is only how the mesh learns which commits belong together, since ADR 0666 §13 reads a shared branch
|
||||
name through pull requests. The operator also said they would not mind a start from scratch; the lead's answer is in
|
||||
section 2 (fix in place, two parts written again) with the reason: 78 per cent of the lines are built by their contract,
|
||||
and the parts that are the earlier model are named and bounded.
|
||||
|
||||
**Design lines and records to write** (no operator decision; `hq-design-writer` and `hq-record-writer`):
|
||||
|
||||
5. The take-in by A-476, as a record: it changes ADR 0666 §6 and ends ADR 0633 §1's hold for manifest validation
|
||||
@@ -298,8 +311,10 @@ at all. Before any code, `hq-design-writer` writes these as design lines in this
|
||||
default (A-476 names none), and `manifest-refused` and the cycle refusal move with it.
|
||||
6. The forge bridge's one message for a watched branch's head moving, replacing the `merged`/`pushed` pair where
|
||||
they differ (a `pushed` message carries no base today), and the end of A-464 to A-464e, A-463 and A-490k.
|
||||
7. The runner's bound: the setting, its default, the order waiting starts are placed in, and that a waiting pipeline
|
||||
is not owed progress under G §12.
|
||||
7. One take-in, one pipeline, and no two at once: the pipeline is per source revision of a watched branch, its steps per
|
||||
mover in the graph's build order, delivered in the deploy order (the operator, 2026-11-20); the setting
|
||||
`pipelines-at-once` with default 1 (principle 11), the order waiting take-ins are placed in, and that a waiting
|
||||
pipeline is not owed progress under G §12. A record, since ADR 0666 §1 and §7 speak per module.
|
||||
8. The want rule A-478 and A-478b as design lines, with the list of holds they end (§266, §268, §269, §376, A-189,
|
||||
§524) and the reshaped order wait on one machine.
|
||||
9. The wake-up rule for every delivery part (section 3.6) as a design line in design 47's main file, with how it is
|
||||
|
||||
Reference in New Issue
Block a user