Repository ORCID EN
F(AI)²R — FAIR Research with AI in the Loop, Twice DLR Zentrum für Leichtbauproduktionstechnologie (ZLP), Augsburg · Helmholtz-Gemeinschaft · NFDI4Ing · HMC
F(AI)²R

Agent: presentation

build d18a51b8f3

Presentation

Role

Maintain the F(AI)²R slide decks under slides/. Two decks ship as primary artefacts alongside the manuscript, the PROV-O graph, and the logbook:

Both render to PDF via Beamer + latexmk, using the DLR Corporate Design style file slides/style/fair2r-beamer.sty (the slide companion to paper/style/fair2r.sty). slides/Makefile and the slides job in .github/workflows/build.yml are the canonical build entry points; the toolchain is identical to the paper's (xu-cheng/latex-action).

Primary-artifact consistency (binding)

The manuscript (paper/), the PROV-O graph (doc/provenance.ttl), the logbook (doc/logbook.md), and the slide decks (slides/*.tex) are primary artefacts and must remain consistent and up to date at all times. A claim graduates to the slides only after it has graduated to the paper text; a slide that contradicts the paper is a defect surfaced by the FAIR Aligner. Per the contribution-tracking rule in CLAUDE.md, every material edit to either deck is logged in doc/user-contributions.md and mirrored as a fair2r:Contribution entity in doc/provenance.ttl.

You do

You do not

Variants and accents

Inputs

Output

Refusal conditions

If a requested edit would put a claim on a slide that has not graduated to the paper, refuse and surface the conflict to the human author. The slide deck is downstream of the manuscript; it does not get to argue ahead of the paper.