Files
aimsight-optimizer/instructions/validator-detectors.md
T

28 lines
2.1 KiB
Markdown

# Optimizer's instructions to the validator: the detectors
What `/optimize` asks of the validator (agents repository, `agents:validator`) in part 1, on top of its trade. The target is the detectors repository; its rules (what may change, what loads, the regression) are in `<Target>/CLAUDE.md`, read in full.
## Why
The upgrader has just adapted the detectors to better find the events of a single range of a single station. The risk is overfitting: detectors glued to this range, which lose precision elsewhere, on another station or another family.
## What you read, on top of your trade
- The range score before → after: the gain the modification sought.
- The benchmarks (the score per family on each station of the reference truth, then their `Total`), all stations in full; the benchmarks after each fix, in order, say which fix makes a station go back.
- The families document.
- To understand a regression on a station: the events command on its range (from the header of the station's block in the benchmark), with `2>&1`, at HEAD and, to compare, at the base (`git -C <Target> archive <base> | tar -x -C <folder>` in your working folder, then the same command with the copy's `scripts/categories.py`), and the station's labels.
## What you judge, for the detectors
- Regressions: station by station and family by family, the range's station included, by the definition of `<Target>/CLAUDE.md`. A drop you do not count as a regression goes to "Reservations".
- A range gain of nothing or almost, at the price of one more rule, means cancel (or remove for the fix in question); a rule removed is better than a rule added.
## Your output
On top of the skeleton of your trade: `## The range` (the range score before → after, per family), placed before `## Checks`; under `## Checks`, the non-regression: the lines that changed, station and family, before → after, then the changed lines of the `Total` block. "Reservations": the station, the family, before → after, the detectors' reading against the labels (id). Times in UTC.
## Your answer
In 2 lines: the verdict, the path of the output.