From 23356b2c88c94875b101dca2e1c58eee0812a52f Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 22:59:37 +0100 Subject: [PATCH] Answer A-68: what outdated compares against is kept as heard 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 121a0363..a23bf1b3 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 @@ -266,3 +266,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". 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. +- **A-68** (ยง375, A-66; principles 1 and 7) The indexer keeps what `outdated` compares against in its own state, as it + hears the events: `toolchain.` the newest `toolchain-agreed` per language, and `delivered.` the + newest `version-delivered` per module, in the same own state as A-66's keys; no new state, no field of `VersionEntry`, + no scan of the streams at a call.