The script copies the source and the folder's images into the AIMsight Typst factory, builds, puts the PDF back as presentation.pdf and reports overflowing slides. run.md: how the user edits and compiles a presentation. Skill /presentation, D-114 and CLAUDE.md updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Skill /presentation: the rotation when it is the angle that moves; the "Conclusions" title; model deck updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
BREITHORN: tilt and pan of the camera (slide 3); targets labelled with their axis in the parallax figure (corr_x horizontal, corr_y vertical); "reflections", not "headlights", on the vehicle; every caption says what each panel shows. MICHIGAN, NEBRASKA: a new figure (tilt, pan, station temperature, horizontal displacement of four targets) for the camera events; complete captions; same conclusion. The client is given facts, not instructions. Skill /presentation and D-114: the rules (no instruction, self-explanatory captions, name only what is visible, "the curves drift", wide multi-panel figures).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
BREITHORN, MICHIGAN, NEBRASKA: "the structure does not move", "not a movement of the structure", "these points do not move", "nothing moved" replaced by the observed fact (the camera moves, the jump occurs when the reference is lost, the vehicle hides these targets, the curves follow the camera); conclusions titled by the main facts; "pique du nez" removed from titles and figures. Skill /presentation: the rules and the model deck updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reports: all October labels (data from 03.10), the expert's diagnosis kept; new findings before 20.10 (night without measurements 15-16.10 on all three; BREITHORN references hidden on 04, 07, 10.10; MICHIGAN curves agitated 17-18.10; NEBRASKA camera stepping back 13-17.10); figures redone for the month.
Presentations (presentation.pdf in each report folder), built with the AIMsight Typst factory ~/docfactory-presentation, in the structure set by the user: "Point de situation" title with station and period, a numbered chronological summary, one self-sufficient slide per event with its diagnosis and picture (BREITHORN: the vehicle in front of COLI24), a conclusion (why it is less reliable, what to do), closing slide. A diagnosis, never an instruction ("to ignore"); the camera's movement is real, its cause (fixing, wall or other) not known.
Skill .claude/skills/presentation/: structure, the user's rules, what failed, model deck (BREITHORN) and image-de-la-cause.py (brightened crops around a target).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
30 labels written by an agent from E-001 to E-011, decoded with the anonymization registry and appended to labeling/<STATION>.jsonl, so the labeling tool shows them with the others; no source field. The tool accepts only data/ stations again.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The labeling tool now accepts event folders (Add, Save), and a Save of a label's text drops its "revue" mark.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- inventaire.py: what each source contains on the window (filled or empty columns, metric names, images), names and counts only
- analyser-lot: step 0 on the data, own scripts in <lot>/outils/, section 3 "Outils"
- tool-builder (the optimiser, rewritten): after the analyst, optimises or adds reading tools, never removes; no control yet
- /aiguiser skill, reader, corrector and voir.py removed; its sessions and spec stay as history
- docs: D-097, specs, CLAUDE.md, run.md, README, plan point 56; the shared files also carry another session's pending edits (D-096 entry, plan points 57 to 67)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- /boucle becomes /events-learner: skill and scripts in
.claude/skills/events-learner/, sessions in events-learner/, spec
vues-deplacements/contexte/events-learner.md, end page
out/events-learner_<session>.html, commits "Learn <STATION> ...";
history keeps /boucle, the review page reads both.
- No benchmark-fin.txt: the end benchmark is the last kept
modification's, on the same events as the start.
- The spec keeps only the why; the how lives in the skill and agents.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- event-builder: called at every batch, reads the whole analysis and
decides on its own, against the event base, what is new; an event
keeps the bounds of the event, not of the batch (plus 6 h).
- the "Nouveautés" section leaves the analysis and the upgrader's
output; the summary lists contradictions with the base.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- analyste: the most precise analysis of the batch, detectors allowed as
a tool; reading, labels, known events, novelties in analyse.md; skill
critiquer-lot renamed analyser-lot.
- detectors-critic: compares the detectors to the analysis event by
event, without looking at the data; verdict and at most two
suggestions in critique.md, read by the detectors-upgrader.
- /boucle step 2, builder, review page, /new-event and score.py import
follow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- detectors-upgrader: makes the detectors better on the batch from the
analyst's critique; adds, removes or modifies, removing first; targets
the significant events missed or badly bounded, not a perfect match.
- detectors-control: the guard against overfitting; never looks at the
batch, judges the diff and the benchmark on the event base, decides,
and sends its remarks back to the upgrader.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The event base is the analyst's knowledge base, read before or during
its reading; a known event is a lead to check on the data, not a
conclusion. No measurement of the analyst's progress.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Catch-up: E-004, E-006, E-007, E-008, E-010, E-011 in the map; new
section 5 "Faux amis"; rejected E-009 no longer cited.
- /review-event and /new-event: what the event teaches goes into the
map at validation, shown to the expert with the fiche.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- read-event: map and index first, then the card of close events only,
then their data with the reading tools; never all cards at once.
Diagnostic agent, critiquer-lot and builder point to it; the index
header too. Signature length: about 250 characters, a guideline.
- "Cas" becomes "event": events/E-xxx/event.md, skills new-event,
review-event, anonymize-event.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The diagnostic agent is kept in case it is needed again, under a name that
says what it is; entry point still .claude/agents/diagnostic.md; paths updated
in skills, agents, spec, contexts, the living plan and CLAUDE.md; reports and
history keep old paths. Also: two stale tool paths in the living plan.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reading tools leave agents/diagnostic/outils/ for a root folder of their
own; paths updated in skills, agents, detectors, scripts, case fiches,
support/, contexts and CLAUDE.md; graphique, vignettes and gif find the repo
root one level up; history keeps old paths.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The case base leaves agents/diagnostic/cas/ for a root folder of its own,
with the event map and its graph; paths updated in skills, agents, scripts,
case fiches, contexts, the living plan and CLAUDE.md; history keeps old paths.
Also: plan point 51, an analyst that improves from session to session.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
It zooms on the event, shows its details and its timelapse under the figure,
and keeps only its sensors on the curves (no second click). Bar dates are
given without the trailing Z, which Plotly does not parse.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>