From 19a1d9342e5e1b2344ea204425fdf0cb087d5adb Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:52:17 +0100 Subject: [PATCH] Answer A-194: the indexer's runs get a read and a drop tool 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 69eea799..a496f27f 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 @@ -59,3 +59,6 @@ the principle that settles it, cited as "design 47 G A-n". called once per candidate revision at the catalog follower's one subscription, whatever branches are followed, so a runner following none still hears it. As §373 says, a run builds each member and its dependents: the dependents' pipelines come from the candidate's entries whose fingerprints the members change. +- **A-194** (principle 4; §64) The indexer's state `runs` and its run candidates get tools as every kept thing does: + `indexer_runs` reads them and `indexer_run_drop` drops one by hand (its hand act written first); a run id is + `run-` and the runner's random 12-hex id, which the indexer's wider pattern accepts.