Food and Beverage

A production site holds specifications, sanitation records and deviation reports. Staff paste that material into a model to get a faster draft. The starter decides what may travel with the paste, and it measures the draft that comes back.

Quality and production staff ask about a specification, a sanitation step or a deviation write-up. The model answers in text, and nothing else happens. There is no tool permission and no route to a line control system, so a release decision stays with the qualified person who owns it.

Two request screens carry fixed wording. The first refuses any prompt that names a facility blueprint, a safety interlock or a control system password. The second uses built-in terms and refuses talk of explosives, weapons and attacks. Neither screen weighs meaning, so a food defense discussion may be refused for a single word.

Identity is required even though the access step carries no options, because authentication is on by default. A request with no verified user and organization is rejected. After that, masking hides badge and operator numbers, maintenance hotline numbers and crew roster lines. Injection screening runs in front of both, so pasted text cannot switch the access rule off.

The response gate wants 0.87 overall with 0.78 relevance and 0.80 accuracy, plus 120 characters and two sentences. A weak answer is refused rather than passed on. Sign-off does not happen on its own, because the oversight point carries no action. Configure it before you tell an auditor that a person reviews the output.

Food safety management, ISO 9001 and NIST CSF 2.0 are the references. What the starter contributes is a traceable input, not a food safety verdict. It does not replace a hazard plan, a verification schedule or a recall procedure. The audit marker records that an evaluated request occurred and never stops one, and retention remains a separate setting.