auto/support/: the folders of the support agent, work/ outside git
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
528336f9e5
commit
df979301b5
3 files changed
+4
-2
No files matched your search
@@ -1,3 +1,4 @@
|
||||
__pycache__/
|
||||
auto/analyses/*/work/
|
||||
.index/
|
||||
auto/support/**/work/
|
||||
@@ -1,8 +1,8 @@
|
||||
# CLAUDE.md
|
||||
|
||||
labeling: the AIMsight displacement labels and the knowledge to place them, in a single copy on the workstation (`README.md`). aimsight-app reads and writes there, Optimizer only reads, both through a link `labeling -> ~/aimsight-labeling`; commits are made here.
|
||||
labeling: the AIMsight displacement labels and the knowledge to place them, in a single copy on the workstation (`README.md`). aimsight-app reads and writes there, Optimizer only reads, both through a link `labeling -> ~/aimsight-labeling`; the support agent writes its folders in `auto/support/`; commits are made here.
|
||||
|
||||
- **The labels**: `manual/<STATION>.jsonl` (the expert, for him alone), `auto/<STATION>.jsonl` (the agents; `review` = the date the user validated the label in aimsight-app, nothing else writes it), one per line, `{"id", "start", "end", "family", "description", ...}`. The aimsight-app analyses: `auto/analyses/<STATION>_<start>_<end>/`.
|
||||
- **The labels**: `manual/<STATION>.jsonl` (the expert, for him alone), `auto/<STATION>.jsonl` (the agents; `review` = the date the user validated the label in aimsight-app, nothing else writes it), one per line, `{"id", "start", "end", "family", "description", ...}`. The aimsight-app analyses: `auto/analyses/<STATION>_<start>_<end>/`. The support agent's folders: `auto/support/<YYYY-MM-DD>_<subject>/`.
|
||||
- **The knowledge**, one source per kind (`README.md`), maintained by hand: `families.md` (the families, their boundaries, the catalogue of phenomena), `labeling-rules.md` (bounds, a single event, description, stated cause), `reading-rules.md` (what the data mean), `stations.md` (the installations); the cases are the labels, through `precedents.py`; what the data are: `tools/DATA.md`. A piece of knowledge lives in one of them only.
|
||||
- **The tools**, standard library: `python3 scripts/validate.py [STATION | file.jsonl]` (the rules), `python3 scripts/ids.py [STATION]` (the stable id of new labels), `python3 scripts/client.py` (what the client is told of a detectors' event, from `families.md`; its check), `python3 scripts/precedents.py "<text>" [--exclude STATION START END] [--family F] [--k N]` (the RAG; it starts the Ollama container `ollama-bge-m3` by itself if it does not answer; `--check` without it).
|
||||
- **For aimsight-app**, which calls them and holds no rule of its own: `validate.check(label, proposed)` (the rules of one label, before it is written in `auto/`), `ids.assign`, `client.message` and `client.action` (the "For the client" columns of `families.md`, per family and per variety). A rename here needs the change there.
|
||||
|
||||
@@ -4,6 +4,7 @@ The AIMsight displacement labels and all the domain knowledge to place them, in
|
||||
|
||||
- `manual/<STATION>.jsonl`: the expert's labels, for him alone: no process and no agent uses them; `auto/<STATION>.jsonl`: those of the Support-Agent `etiqueteur` and those submitted by the aimsight-app `analyst`; `review` is the date the user validated a label in aimsight-app (quality over quantity: only the analyses discussed and validated there), and any change removes it; the agents' reviews of 2026-11-04 and 2026-11-05 were removed on 2026-11-17 (in the history); one label per line, `{"id", "start", "end", "family", "description", ...}`, UTC times, `family` = the family.
|
||||
- `auto/analyses/<STATION>_<start>_<end>/`: the analyses launched from the Data page of aimsight-app (`work/` outside git).
|
||||
- `auto/support/<YYYY-MM-DD>_<subject>/`: the folders of the `support` agent (agents repository): the request, the answer, the analyst's work when it was called (`work/` outside git).
|
||||
- The knowledge, one source per kind, maintained by hand by the user; the analyst reads the four files in full:
|
||||
|
||||
| Kind of knowledge | Source |
|
||||
|
||||
Reference in new issue
Block a user