Claims are yours: why Labelkiln will never write organic for you

Ask a language model to write a granola label and it will cheerfully add organic, gluten free, and packed with protein. It does not know your supplier, your certification status, or your nutrition panel. It is guessing, and on a package a guess becomes a claim.

Three guards, in order

• The prompt. The copy model is told to copy your claims verbatim and add none, with a list of regulated terms it must never introduce.
• The schema. Every reply is validated against a strict shape. Front claims are then replaced on our server with exactly the claims you typed, so even a model that ignores instructions cannot add one.
• The scrub. Any sentence in the back story or rationale that contains a regulated term you did not supply is removed before you see it.

What counts as regulated

Our list covers certification words (organic, kosher, fair trade), free-from claims (gluten free, dairy free, non-GMO), nutrient and health language (protein, vitamins, healthy, immune), and a handful of vague words regulators dislike, such as natural. If you type one as a claim, it prints, because it is yours to substantiate.

And the panel you still need

Labelkiln leaves a marked regulated area on every back panel: nutrition facts, ingredients, allergens, net contents, barcode, and legal text. Every export reminds you to add and verify them. We would rather be a little repetitive than let a label go to press with a hole in it.