From e52479adf82fe62ec5482ad782e11948cc9d6df9 Mon Sep 17 00:00:00 2001 From: maxime Date: Mon, 16 Nov 2026 14:56:41 +0100 Subject: [PATCH] =?UTF-8?q?D=C3=A9p=C3=B4ts=20renomm=C3=A9s=20avec=20le=20?= =?UTF-8?q?pr=C3=A9fixe=20aimsight-=20:=20chemins=20et=20noms=20mis=20?= =?UTF-8?q?=C3=A0=20jour?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 --- CLAUDE.md | 4 ++-- README.md | 22 +++++++++++----------- 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index b148b1c..586b270 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -2,8 +2,8 @@ Optimizer: the optimisation of the AIMsight detectors and of the reading tools, from one analysis of `labeling/auto`, and nothing else (`README.md`). The workflow: `.claude/skills/optimize/SKILL.md` (`/optimize`), launched from the root of Optimizer with the agents plugin (`--plugin-dir agents`); its agents `agents:upgrader`, `agents:validator` (the detectors) and `agents:upgrader` again (the tools), each with its file of `instructions/`; the benchmark `detectors/bench/`. -- **The links**, out of git: `detectors/` → `~/detectors` and `tools/` → `~/tools` (the session commits there); `data/` → `~/aimsight-data/data` and `labeling/` → `~/labeling` (read-only); `agents/` → `~/agents` (the plugin, loaded read-only). -- **The sessions**: `sessions/_/`; Diagnostic-App reads their summary (`summary.md`). +- **The links**, out of git: `detectors/` → `~/aimsight-detectors` and `tools/` → `~/aimsight-tools` (the session commits there); `data/` → `~/aimsight-data/data` and `labeling/` → `~/aimsight-labeling` (read-only); `agents/` → `~/aimsight-agents` (the plugin, loaded read-only). +- **The sessions**: `sessions/_/`; aimsight-app reads their summary (`summary.md`). - **The workflow stays generic**: the skill describes only the workflow (analysis → detectors: upgrader → validator; tools: upgrader → summary); what is specific to a caller (its paths, its git rules, `Caller's context`) arrives in the request. - **Check a change of the skill**: `env -u ANTHROPIC_API_KEY claude -p "/optimize" --plugin-dir agents --model haiku` must say the inputs are missing and stop without touching `detectors/` or `tools/`; then a real session through the app's button. - `archive/`: the former batch and its scanner, stopped; do not run them again. diff --git a/README.md b/README.md index 9dadcd0..11cec66 100644 --- a/README.md +++ b/README.md @@ -1,9 +1,9 @@ # Optimizer -The optimisation of the AIMsight detectors and of the reading tools, from one analysis, and nothing else. An analysis (made in the Diagnostic-App app by the analyst) leaves in its folder the two things needed: its labels, the truth on its range, and its own scripts with what it missed. On that analysis, the `optimize` skill: +The optimisation of the AIMsight detectors and of the reading tools, from one analysis, and nothing else. An analysis (made in the aimsight-app app by the analyst) leaves in its folder the two things needed: its labels, the truth on its range, and its own scripts with what it missed. On that analysis, the `optimize` skill: -1. **the detectors**: measures their score on the range, and the benchmark on every label of `labeling/auto`; has them fixed by the `upgrader`, one fix per commit in `~/detectors`; has them judged by the `validator`, which keeps, has some removed, or cancels: no station goes back, no overfitting; -2. **the tools**: has the `upgrader` bring the analyst's useful scripts into the reading harness, one fix per commit in `~/tools`; always, whatever the detectors gave; +1. **the detectors**: measures their score on the range, and the benchmark on every label of `labeling/auto`; has them fixed by the `upgrader`, one fix per commit in `~/aimsight-detectors`; has them judged by the `validator`, which keeps, has some removed, or cancels: no station goes back, no overfitting; +2. **the tools**: has the `upgrader` bring the analyst's useful scripts into the reading harness, one fix per commit in `~/aimsight-tools`; always, whatever the detectors gave; 3. writes the summary of the session. The `upgrader` and the `validator` come from the `agents` repository, each with its instructions from `instructions/` (`upgrader-detectors.md`, `validator-detectors.md`, `upgrader-tools.md`); the rules of each target are its own `CLAUDE.md`; the benchmark (`bench/`) from the `detectors` repository. Nothing is pushed. @@ -11,22 +11,22 @@ The `upgrader` and the `validator` come from the `agents` repository, each with ## Install ```bash -ln -s ~/detectors detectors # the detectors, shared with Diagnostic-App -ln -s ~/tools tools # the reading tools, shared with Diagnostic-App +ln -s ~/aimsight-detectors detectors # the detectors, shared with aimsight-app +ln -s ~/aimsight-tools tools # the reading tools, shared with aimsight-app ln -s ~/aimsight-data/data data # the pumped data, out of git -ln -s ~/labeling labeling # the labels, the analyses and the families -ln -s ~/agents agents # the generic agents (Claude Code plugin) +ln -s ~/aimsight-labeling labeling # the labels, the analyses and the families +ln -s ~/aimsight-agents agents # the generic agents (Claude Code plugin) ``` `claude` (Claude Code) must be on the `PATH`, logged in to the Claude subscription (`/login`), never to an API key. ## Run -From the "Optimize" button of Diagnostic-App, on a finished analysis; or by hand, from the root of Optimizer: +From the "Optimize" button of aimsight-app, on a finished analysis; or by hand, from the root of Optimizer: ```bash env -u ANTHROPIC_API_KEY claude -p "/optimize ANALYSIS: labeling/auto/analyses//. OUT: sessions/_/." \ - --plugin-dir agents --add-dir ~/detectors --add-dir ~/tools --add-dir ~/labeling --add-dir ~/aimsight-data/data \ + --plugin-dir agents --add-dir ~/aimsight-detectors --add-dir ~/aimsight-tools --add-dir ~/aimsight-labeling --add-dir ~/aimsight-data/data \ --setting-sources project,local --strict-mcp-config \ --allowedTools Read,Write,Edit,Bash,Agent --permission-mode acceptEdits ``` @@ -35,6 +35,6 @@ The station and the range come from the analysis's `request.json` (the range's l ## What a session leaves -`sessions/_