Generic upgrader and validator on a target; tool-builder folded into the upgrader

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
maximeandClaude Opus 5.5 committed 2026-11-16 14:44:24 +01:00
1 parent 0df04b58ae
commit 3a0c0e615d
5 files changed
+73 -172

No files matched your search

+4 -5
View File
@@ -1,13 +1,12 @@
# agents
The generic AIMsight agents, one copy of each. An agent states only its trade here; everything specific to a caller (its output paths, its report format, its git rules) reaches it in the request, or through an instruction file the request names.
The generic AIMsight agents, one copy of each. An agent states only its trade here; everything specific to a caller (its output paths, its report format, its git rules) reaches it in the request, or through an instruction file the request names (`INSTRUCTIONS`). The rules of a target the upgrader and the validator change (what may change in it, what a regression is) are the target's own `CLAUDE.md`: written once, read by both and by whoever edits the target by hand.
| Agent | Its trade | Request parameters | Called by |
|---|---|---|---|
| `analyst` | read a range like the expert and label it, with an analysis that justifies each label | station, range, hints, output folder, `DETECTORS: yes \| no` (with `yes`, `Events: <command>`), `INSTRUCTIONS: <file>` | Diagnostic-App (`instructions/analyst.md`, `DETECTORS: no`) |
| `tool-builder` | bring the useful scripts of an analysis into the reading harness (tools repository) | the analysis, the tools repository, the path of its report | Optimizer (`optimize` skill), after the detectors |
| `upgrader` | fix the detectors on a range, without overfitting | that of the `optimize` skill | Optimizer |
| `validator` | judge the upgrader's modification on every station and family | that of the `optimize` skill | Optimizer |
| `upgrader` | improve a target (a git repository) on the evidence given, without overfitting, one commit per fix | `Target`, `Evidence`, `Checks` (or `none`), `Base`, `Files already modified`, output folder, `INSTRUCTIONS: <file>` | Optimizer (`optimize` skill): the detectors (`instructions/upgrader-detectors.md`), then the tools (`instructions/upgrader-tools.md`) |
| `validator` | judge an upgrader's change on the checks and the code, without its diagnosis: keep, remove some fixes, cancel | `Target`, `Modification`, `Base`, `Checks` (before, after, after each fix), output, `INSTRUCTIONS: <file>` | Optimizer, the detectors (`instructions/validator-detectors.md`) |
## Launching them
@@ -21,4 +20,4 @@ In a workflow, through the Agent tool: `subagent_type: agents:upgrader`, with `-
The caller launches from its root, which carries the links `data/` (the stations, `~/aimsight-data/data`), `labeling/` (`~/labeling`), `tools/` (`~/tools`), and `detectors/` (`~/detectors`) when the agent needs it; it gives `--add-dir` on their real targets so that the agent can read or write there. Claude does not write into a loaded plugin: what gets written (the tools, the detectors, the sessions) lives in the other repositories, never here.
Taken on 2026-11-16 from Diagnostic-App (`analyst`, `tool-builder`, commit dd6f1bf) and from detectors (`upgrader`, `validator`, commit 5438b0b). The architecture of the repositories: `~/Diagnostic-App/docs/architecture.drawio`.
Taken on 2026-11-16 from Diagnostic-App (`analyst`, `tool-builder`, commit dd6f1bf) and from detectors (`upgrader`, `validator`, commit 5438b0b); the same day, the upgrader and the validator were made generic on a target and the tool-builder folded into the upgrader (`docs/superpowers/specs/2026-11-16-generic-agents-design.md`). The architecture of the repositories: `~/Diagnostic-App/docs/architecture.drawio`.