Answer A-68: what outdated compares against is kept as heard

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:59:37 +01:00
parent 441296f37a
commit 23356b2c88
1 changed files with 4 additions and 0 deletions
@@ -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.<language>` the newest `toolchain-agreed` per language, and `delivered.<module>` 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.