EU Regulation 2024/1143 in a PDO/PGI dairy — the specification changes, the dossier does not fall behind.

The problem

A dossier that ages faster than it gets rewritten.

The PDO/PGI of a European cheese is, at bottom, a written agreement between the plant, the Regulatory Council and the EU. That agreement lives in the product specification, and the specification — under the new EU Regulation 2024/1143 — becomes more demanding on three fronts:

1. Materials and origin — which milk, which breed, which pasture, which rennet, which specific supplier. And traceable.
2. Process — which temperature, how long, which room, which rind. And verifiable.
3. Processing stage — who did what and when, with a signature.

The quality manager owns the specification — but the real data lives on five islands at once: the recipe in the ERP, the vat records in the SCADA, the master cheesemaker's notes in a notebook, the ripening room curve in an Excel sheet, the rennet supplier's invoices in an email inbox. Every change of supplier touches the dossier; every audit forces a manual rebuild. And the question is not whether it will be done properly — it will — but how much qualified people's time is spent reconstructing a past that was already happening in front of them.

How it fits the IRIS system

iLEAN Writer does not add one more system — it writes the file from the data that already exists.

The PDO/PGI dossier is not a document, it is the crystallization on paper of what happened in the plant. Today that crystallization is done afterwards, by hand, against the clock before the audit. iLEAN Writer does it continuously, on the real data captured by Connect, without asking you to change your ERP, MES or SCADA, or the way the Regulatory Council is organized. It is the putty between the data and the written word.

Connect captures the batch data wherever it lives. Writer drafts on what was captured, not on what was remembered. The person validates, signs and sends it to the control body. What is critical is never decided alone.

The iLEAN pieces applied to EU Regulation 2024/1143 compliance:

• Connect — captures the recipe and the batch data whether it comes from the ERP, from the vat SCADA, from the master cheesemaker's notebook (a photo), from the ripening room Excel sheet or from the rennet supplier's email. And it captures what comes from the outside (a notice from the Regulatory Council, a specification change in the Official Journal) at second zero.
• iLEAN Writer (agent) — anchored to the PDO/PGI specification of your cheese and to the text of EU Regulation 2024/1143. It drafts the dossier continuously, batch by batch, with references to the captured data. When a value is missing, it does not invent it: it flags it as pending and proposes the source.
• Three safety rings — fast inference lives in ring 3; validating that every reference actually exists lives in ring 2; the signed dossier lives in ring 1, where the quality manager decides what goes to the control body. A human always closes the door.

See the full IRIS architecture →

Before and after

A PDO/PGI dossier rebuilt by hand vs. a living dossier with iLEAN Writer

Aspect	Manual rebuild before the audit	With iLEAN Connect + Writer
State of the dossier	Frozen at the last annual review	Alive, batch by batch
Change of supplier	Noted down; the dossier is updated "when there's time"	Connect captures it; Writer rewrites the affected section
Traceability at the processing stage	Excel + notebook + the shift lead's memory	Captured and linked to the batch continuously
Preparing for the audit	Weeks of late-night work by the quality manager	The dossier is already there; the person reviews and signs
Adapting to the new specification	A complete rewrite	Writer recomposes from the data; the person adjusts
Risk of an undetected gap	High — it only shows up at the audit	Writer flags pending items in real time

Impact estimate

Impact estimate for your plant — to be validated with your numbers.

The block below is an estimate to be validated with the specific data of your plant. We put it forward so the committee has an order of magnitude; we refine it during the diagnostic.

• Dairy with one or several PDO/PGI designations, multi-recipe, a quality team of 2–4 people spending significant blocks of time on documentation.
• iLEAN Writer + Connect pilot anchored to the specification in force. First value in a few weeks: a dossier up to date on the latest batches, with the gaps visibly flagged.
• Indicative payback between 4 and 9 months, depending on the current internal cost of preparing audits and specification amendments, and on the risk of a finding by the control body.
• Hard lever: a reduction of ≥30% in the quality time spent rebuilding the dossier plus a lower risk of an audit finding (the dossier is there, nobody has to go looking for it).

And the quality manager's reasonable doubt

“What if the AI invents a sentence and it ends up in a signed file?” — hallucination is a problem of free generation, not of anchored tasks. When the AI merely recontextualizes real data into the language of the specification, the best models brought error below 1.5% ^[1]. And even so, what is critical is never decided alone: iLEAN Writer proposes and the person signs. The three safety rings exist precisely for this.

^[1] OpenAI paper “Why Language Models Hallucinate”, 2025 — on the reliability of AI in anchored tasks.