From d40854a07360cbdb21d8396e0909f27b25c6ca74 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 09:22:28 +0100 Subject: [PATCH] Answer A-251: the branch-unprotected finding's scope and id 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 52b47964..79eae638 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 @@ -275,3 +275,6 @@ the principle that settles it, cited as "design 47 G A-n". assigner's process hears that write on its own state at once, says `version-delivered` again when every present placing machine runs the version healthy and deletes the ask, else keeps it with its reason, read by `assigner_waits`. +- **A-251** (§17, §383, §437; principle 8) The finding `branch-unprotected` has scope `merge`, id the owner, + repository and branch escaped as one key name (`~~`), severity warning, and that scope + and id as its subject.