From 98d7be07fd07c41455ab1539a33dd71cc0ba9ee0 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:56:04 +0100 Subject: [PATCH] Answer A-202: a pipeline says the publish that started it Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index cc1d5833..f9724a3e 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -88,3 +88,6 @@ the principle that settles it, cited as "design 47 G A-n". - **A-201** (§189, §190, A-160, A-174; principle 7) The assigner keeps a candidate's assignment graph per run (key `run-`), made when the candidate's revision is heard and dropped on that run's last `pipeline-ended`, as the indexer keeps the candidate; the gate's `heads-replaced` drops nothing in the assigner. +- **A-202** (§31; principles 2 and 7) A pipeline's record and `pipeline-started` say their cause: an optional + `published` {artifact, version} set when a package's publish started it; a newer publish of the same artifact on + the same branch supersedes the running pipelines whose `published` names that artifact at an older version.