From 441296f37a014a4e02886c025d1068b1dfb85378 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 22:57:38 +0100 Subject: [PATCH] Answer A-67: the pass keeps its assignment graph revision first Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index d0a98fba..121a0363 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -262,3 +262,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". artifact's paths, and `packages` and `beside` where the entry carries them); the time since a seat first failed to answer is kept in the indexer's own state, so a restart keeps it, and the finding is written at the next seed attempt past five minutes. +- **A-67** (ยง292 and G-5's *wants follow the assignment graph*; principle 7) (c): the design has the assigner write each + want from an assignment graph revision it keeps, so the pass keeps that revision first (assigngraph.Compute and Keep + per catalog revision taken in), and `wanted`'s `revision` and `source` are that kept revision's and its catalog's. + No stand-in value.