Household safety
Chef never infers an allergy or safety constraint. “Sam dislikes peanuts” remains an ordinary preference unless the affected person explicitly confirms something more. Stored constraints retain their person, scope, source and confirmation.
A meal that appeared safe does not weaken an existing constraint. Chef is not medical advice.
Approval ladder
- Review and approve one exact meal-plan version.
- Review and approve the grocery plan derived from it.
- Give a separate approval before any basket mutation.
- Verify absolute intended quantities line by line.
- Take over before checkout or any payment step.
Changing participants, servings or recipes makes prior approval stale and invalidates the derived grocery plan.
Computer Use beta
Chef first checks whether the user's agent has an appropriate browser or Computer Use capability. If it does not, Chef exports Markdown or JSON. If it does, the user still chooses the provider and remains responsible for its terms.
A shop run reports only succeeded, blocked, retryable, uncertain or failed. Success requires evidence for every line and the final basket. Incomplete verification is uncertain, never “ready”.
Hard stop
Chef does not perform checkout, payment, fulfilment, restricted-product handling or order placement. It does not bundle a named retailer adapter and does not bypass access controls or bot protections.