- app/serveur/ (FastAPI) and app/web/ (React, Mantine) moved out of API/, which keeps
only the agents; the Support page drives them
- Images page: view.py in React (slider, zoom, sensor names, displacement arrows on a range)
- Labeling page: labeling.py in React (two aligned plots, label bar, add, edit, delete);
labels are written to labeling/{auto,manual}/ of the repo (AIMSIGHT_LABELS)
- shared station and date selector kept in the address; buttons from a support session
- app/serveur/station.py: the data of both pages, copied computations listed in app/README.md
- app/serveur/check.py: server and station checks (labels in a temporary folder)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Same features as the local page; agents, tools, prompts and knowledge unchanged.
- API/web/: React (Vite) with Mantine components: collapsible sidebar, mobile drawer,
cards, notifications, dark mode
- API/support/serveur.py: FastAPI serves the built page and /api; agent events pushed
by server-sent events (/api/flux) instead of polling
- data, cases folder and port set by AIMSIGHT_DATA, AIMSIGHT_CASES, AIMSIGHT_PORT
- check.py: server check (host guard, analyse, stream, PDF) with a fake client
- old page.html removed
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Self-contained sub-project API/: a local support page where Marc pastes a
client's mail; a support agent and an analyst agent stay alive for the session
and produce a slide PDF that answers the client's question. Tools, detectors,
knowledge and Typst brand are copied (API/PROVENANCE.md). First real case:
Crissier (LENZSPITZE), workflow validated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ids.py puts the id first and never re-gives an id retired in the same operation; labeling.py
keeps it first on add and edit; controle.py requires it first. Cross-review apply: a modified
label keeps its id, and revue is today's date. All 991 auto labels reordered, content unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JUNGFRAU (the PS_DES_COUDRES night, 07.10), NORDEND (03.09 web over CTR04), LENZSPITZE
(turbulence beyond the bridge), WILDSTRUBEL (well compensated, small residual at the bottom).
Expert labels unchanged; map section 6 updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Every auto label carries an id (<STATION>-<n>, labeling/ids.py), kept on edit, given to
new labels by labeling.py and by the reviews; controle.py requires it, unique. The
cross-review matches labels by id, and an applied review is locked (applique.md).
- The label map starts with a summary (labels-map/sommaire.py): readers take the summary and
sections 2-4 in full, then only the cards of the phenomena they meet.
- Tool-builder session on the reviewers' difficulties: jours.py --lissage/--fraction,
ensemble.py --suivre and rejected measures left out of --rigide, --residus non, zero noise
after a lost reference, new agent-tools/stations.py (several stations on one timeline),
long outputs convention in lire-les-donnees.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The labeler writes to its own folder (etiquettes.jsonl); labeling/auto/ only holds
reviewed labels, merged by /review-auto-labels (new apply script: dated, sorted, checked).
- labeling/controle.py also checks a proposed file; the labeler and reviewers run it before
handing back. Reviewers keep their measurements in revue.md, never in the labels.
- Reviewer instructions explicitly add their scripts, .venv/bin/python and for loops to the
lire-les-donnees commands (the contradiction raised by 12 reviews).
- Expert validation optional in /review-auto-labels; an expert hint given to the labeler is
written in the labels it touches. Cross-review ends with the releveur.
- docs/ameliorations-processus.md: 17 entries from this review, by the releveur.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>