--- name: optimize description: Workflow that, from one analysis (its labels as the truth on its range, its scripts and what it missed), optimises the detectors — the upgrader fixes, the validator judges; detectors a little better on the range without going back elsewhere (benchmark on a reference truth), or unchanged — then the reading tools — the tool-builder brings the analyst's useful scripts into them. The caller gives the analysis, the output folder and any specific context. Run from Optimizer's root with the agents plugin (--plugin-dir ). /optimize . argument-hint: "ANALYSIS: . OUT: . [context]" --- # optimize: the detectors and the tools, from one analysis You are the orchestrator. An analyst has analysed a range of a station; its folder holds its labels (the truth on this range), its report, its analysis and its own scripts. Two parts follow, in this order. **Part 1, the detectors** (the detectors repository, `DETECTORS`: `scripts/`, `thresholds.md`): you run the upgrader, which fixes them, then the validator, which judges the fixes against overfitting, and you return detectors **a little better on the range without going back elsewhere**, or unchanged. **Part 2, the tools** (the reading harness, `TOOLS`): you run the tool-builder, which brings what the analyst needed into the tools. **You judge nothing yourself**: you only read the verdict lines. **You ask no question**: the workflow runs alone to the end. ## Inputs Given by the caller, in the request; any other context or rule it gives (files to read, git rules, where to commit, names) applies to this run and is passed on to the agents as it is (`Caller's context: …`), before their instructions but not before their file scope. - `ANALYSIS` (required): the analysis folder: `request.json` (`station`, `start`, `end`, UTC), `labels.jsonl`, `report.md`, `analysis.md`, `scripts/`. - `OUT` (required): the output folder of this run (`sessions/_/` in Optimizer). - Defaults, relative to Optimizer's root (its links), which the request may override: `DETECTORS: detectors/`, `TOOLS: tools/`, `DATA: data`, `LABELS: labeling/auto` (the folder of the `.jsonl` label files, JSONL: `id`, `start`, `end`, `family`, `description`), `FAMILIES: labeling/families.md` (the families and their boundaries, one detector per family). Derived from `/request.json`: - `STATION`: `/` (read by `DETECTORS/scripts/data.py`); - `FROM`: the day of `start`; `TO`: the day after the day of `end` (UTC days, YYYY-MM-DD, `TO` excluded); - the labels of the range: `/.jsonl` (the analysis's labels are submitted there); - `REFERENCE`, the reference truth for the non-regression: `--labels --data `; - `CONTEXT`: `/report.md`. `ANALYSIS` or `OUT` missing, no `/request.json`, `DETECTORS` or `TOOLS` not a git repository: say so and stop, changing nothing. ## Commands - events: `python3 /scripts/categories.py --from --to ` - sensors: `python3 /bench/sensors.py --from --to ` - range score (the goal): `python3 /bench/score.py --labels /.jsonl --from --to `; it exits with an error if no label touches the range: note it in the summary, touch nothing in the detectors and go to part 2. - benchmark (the non-regression, about 3 min): `python3 /bench/regression.py ` The measures of a step: ` > /range-.txt 2>&1` and ` > /benchmark-.txt 2>&1`. ## Git The fixes are commits in `DETECTORS`, one per fix, so that the validator can have one removed. Note the **base**: `git -C rev-parse HEAD`. Files already modified (`git -C status --porcelain`) stay as they are, neither committed nor reverted; list them in the summary and pass them to the upgrader. Always commit by path (`git -C commit -m "" -- `), never `git add -A`, `git stash` or `git checkout` outside your paths: another session may be working there. Each message ends with an empty line then `Co-Authored-By: Claude Opus 5.5 `. The tool-builder commits in `TOOLS` itself. Nothing is pushed. The rest (branch, committing `OUT`, another repository) is the caller's. ## Steps Each agent is called with the Agent tool, its `subagent_type` (`agents:upgrader`, `agents:validator`, `agents:tool-builder`, from the agents plugin loaded with `--plugin-dir`; not available: say so and stop, changing nothing) and the request below, plus the caller's context. A verdict is read by `grep '^\*\*Verdict\*\*:' `. ### Part 1: the detectors 1. **Measures before**: step `before`. 2. **Upgrader**, a single pass: `Detectors: . Station: , range → (UTC). Labels: /.jsonl. Families: . Context: . Events command: <…>. Sensors command: <…>. Range score command: <…> (before: /range-before.txt). Benchmark command: <…> (before: /benchmark-before.txt). Base: . Files already modified: . Output folder: . Write /modification.md.` It commits each fix it keeps, message `improve: S`, with its benchmark `/benchmark-S.txt`. Verdict `nothing to change`, or no fix commit (`git -C log --format=%h --grep ': S[0-9]*$' ..HEAD` empty): go to part 2. 3. **Measures after**: step `after`. 4. **Validator**, which reads neither the diagnosis nor the detail of the modification: `Detectors: . Families: . Modification: /modification.md. Range score: /range-before.txt → /range-after.txt. Benchmark: /benchmark-before.txt → /benchmark-after.txt, after each fix: /benchmark-S*.txt; command: <…>. Events command for any station: python3 /scripts/categories.py --from --to . Base: . Write /validation.md.` - `keep`: go to part 2. - `remove`: for each fix of the `**Remove**:` line, its commits (`git -C log --format=%h --grep ': S$' ..HEAD`), from the most recent: `git -C revert --no-edit `, then `git -C commit --amend -m "improve: S removed" -m "Co-Authored-By: Claude Opus 5.5 "`. A conflict: `git -C revert --abort`, and do as for `cancel`. - `cancel`, or anything else: `git -C revert --no-commit ..HEAD && git -C commit -m "improve: modification cancelled" -m "Co-Authored-By: Claude Opus 5.5 "` (only what the fix commits changed; files already modified stay as they are). 5. **Measures end**, only after a `remove`; otherwise `end` is `after` (`keep`) or `before` (`cancel`, nothing changed). An output missing or without a readable verdict: note it, put the detectors back as for `cancel` if they changed, go to part 2. Do not rerun an agent. ### Part 2: the tools Always, whatever part 1 gave (a stop in part 1 does not stop part 2). 6. **Tool-builder**: `Analysis: /. Tools: /. Write /tools.md.` It reads the analysis, writes only in `TOOLS` and in ``, and commits in `TOOLS`. Its output missing: note it. Do not rerun it. ## Summary `/summary.md`: ```markdown # optimize: , → **Result**: modification kept | kept without S… | cancelled | none | error **Tools changed**: /tools.md> | error ## The range the range score, before → end, one line per family (found, correct) ## Elsewhere the `Total` line of each family, before → end; then the other changed lines (station, family), before → end ## What changed ; the upgrader's verdict, the validator's ## For the user to decide ## Not fixed <"Not fixed" of the modification; none> ## Reading tools /tools.md, and its "data.py" line if changed; none> ## Scripts of the agents /tools/`); none> ## Errors log --oneline ..HEAD`; `git -C log --oneline -1` if the tools changed> ``` ## Answer In 5 lines at most: the `**Result**` line, the range score before → end (changed families), the `Total` before → end if it changed, the `**Tools changed**` line, the path of the summary.