How this site is made

Food Additive Index is built and written with an AI model, Anthropic's Claude, working to instructions and rules set by the person who runs the site. This page says which parts the AI writes, which parts it does not, and what has and has not been checked. The wider method is on Method.

What scripts read from sources, with no AI in the loop

The legal facts on the 1189 additive pages are not written by anyone. Scripts fetch each regulator's published list — the eCFR, EUR-Lex, legislation.gov.uk, Health Canada, the Federal Register of Legislation, e-Gov, South Korea's notification, the Codex and JECFA databases, EFSA and the FDA — and store, for each row, the source, the provision and the date it was retrieved. A page prints those rows and links the instrument. The status of an additive in a country, the maximum level in a food category, an acceptable daily intake and the identifiers (E, INS, CAS) are all of this kind.

A change to what a source says is detected on the next weekly run and recorded with the date. A change that looks too large, or that the source does not explain, is held back and not published until it has been looked at and released or discarded with a note. The structure diagrams are PubChem's records; the tables are generated from the data. Nothing on the site is an AI-generated image.

What the AI drafts

What the AI does not do

How it is checked

What has not been checked

No error rate has been measured for the prose, and no second reader, whether a toxicologist, a food lawyer or a regulatory specialist, is claimed for any page. The prose is short, and where it is wrong the table beneath it, with its citations, is the authority. Nothing here is legal, medical or regulatory advice. Before relying on an entry for a decision, read the instrument it links.

The pages were added in batches as each source was matched, not all at once, and a page is created only when a regulator names the substance and there is a source to cite for it.