Answer A-194: the indexer's runs get a read and a drop tool

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 18a5617fa4
commit 19a1d9342e
1 changed files with 3 additions and 0 deletions
@@ -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.