Files
aimsight-tools/CLAUDE.md
T

2.3 KiB

CLAUDE.md

tools: the reading harness of the AIMsight agents (README.md), and nothing else. The user guide is GUIDE.md; a new tool or a new option goes into it in the same change. DATA.md (what the data are) is maintained by hand by the user; GUIDE.md is the upgrader's (agents repository, run by Optimizer's optimize skill).

  • Checking a change: rerun the touched tool from a calling repository (aimsight-app: python3 tools/scripts/<tool>.py data/<STATION> --start … --end …), and the commands of the guide that use it; python3 tools/scripts/quality.py --self-test (from the calling repository).

Rules:

  • A tool returns values: no threshold, no category, no "anomaly", no "normal"; the analyst judges.
  • Nothing specific to a station, a sensor or a date.
  • No import from the detectors (detectors/).
  • Standard library; matplotlib, through the caller's .venv/bin/python, for the figures only.
  • Never a value from metrics/ that is an identifier (SIM_CCID, ip*); read-only on data/; never read .env.
  • Break nothing: existing options and outputs stay, the analyses' reports cite commands that must keep working.
  • A change to improve the tools touches scripts/ and GUIDE.md only; README.md, CLAUDE.md and DATA.md (the user's) are not part of it.
  • Remove nothing: no tool, no option, no output, no sentence of the guide; a tool that did not help on one range may help on another, and a single analysis is not enough to clean the list. Optimise or add.
  • The simplest first: a sentence of the guide or a better default; otherwise an option of an existing tool; a new tool as a last resort. A new script has a docstring at the top, like the others, and enters the table of GUIDE.md in the same change.
  • scripts/data.py is the common reader of the app and the tools: touch it only to fix a reading error. The app passes these measurements to the detectors (the events of the Data page), which otherwise read with detectors/scripts/data.py (benchmark, Optimizer): a reading fix here is carried over there, otherwise the page and the benchmark diverge silently. A change to data.py is said at the top of the change's report; the same fix in detectors/scripts/data.py is left to the user, named in that report.
  • Every time is in UTC. Commits by path, never git add -A. Language: English.