add_storage_item
ChatGPTAdds something the user has put up to their Storage, with the date it stays good until. check_storage_item with the method's USUAL place — freezing keeps to the freezer, cold storage to a cellar, vinegar pickling / oil infusions / sweet preserves to a fridge, everything else (freeze drying, dehydrating, alcohol infusion) to a pantry shelf — returns the real kinds kept there, which ground the question of where it is kept (a blank "where will it be kept" invites an invalid-sounding guess the real data would have ruled out). A food not in that place's real list is found by check_storage_item for wherever it is. days_ago is the user's own answer for when it was made, packed or frozen (0 for today); an assumed one gives a wrong safety date. A finished batch goes into Storage through finish_batch instead.
check_batch
ChatGPTIs it done? A doneness check for a freeze-drying or dehydrating batch, or a set check for a jam or jelly. Observations go in as the user's own words, untidied and uninterpreted. With batch_id (from get_batches) the check is saved with the batch. The verdict is PreserveAdvisor's: relay it, its explanation and next steps as returned, and say back any numbers the user gave. Where the account has a monthly allowance of checks, this uses one.
check_freezer_outage
ChatGPTAfter a power cut or a freezer left open: is ONE frozen item safe to refreeze or cook, or should it be thrown out? Ask the user for each answer; never assume one. One call covers one item. Relay the answer and its reasons as returned, and say the hours and temperature back to the user. Saves nothing and uses nothing up.
check_storage_item
ChatGPTAnswers "is this still good?" for something the user has put up, whether or not it is in their Storage. With the place alone it returns the kinds and foods PreserveAdvisor has sourced storage times for in that place. With place, kind, food_id and its age (days_ago, or age_unknown: true) it returns the answer: a headline, why, what to check before using it, and the date — PreserveAdvisor's own answer, relayed exactly as returned, not rounded or re-derived. When safety_date is true the date is a safety limit: past it, do not suggest smelling, tasting or looking at it to decide. Saves nothing and uses nothing up.
create_preserve_plan
ChatGPTPlans a batch and saves it to the user's Batches, where the app shows it too. Its real ids come from get_method_options for the method. Three ways to ask: a starter_id (a ready-made recipe); the picked fields for the method (food_id plus the answers that method needs); or request, a plan described in the user's own words, only when the food is not on the list. Ask the user for every answer a method needs — never assume a vinegar acidity, a spirit proof, an amount or a date. The result is PreserveAdvisor's plan: its steps, times, temperatures and ratios are relayed exactly as returned, not rounded or re-derived. When declined is set, PreserveAdvisor will not plan this; relay the reason and what to do, and do not supply a method from your own knowledge.
delete_batch
ChatGPTPermanently deletes a batch with its plan, checks and notes. Deletion is immediate and cannot be undone, and the server does not ask for confirmation itself: it relies on the user having explicitly confirmed this specific batch, identified by its name, before the call. A batch that is simply done is closed with finish_batch instead.
diagnose_batch
ChatGPTWhat went wrong, or did it go right? A diagnosis of a FINISHED freeze-drying or dehydrating batch, from the user's own account of it. Other methods have no diagnosis. If do_this_first is set, say it first. Causes and next_time are PreserveAdvisor's own and are relayed as returned. Where the account has a monthly allowance of checks, this uses one. It marks the batch done; finish_batch then records the outcome and the notes for next time.
finish_batch
ChatGPTCloses a batch: how it turned out, up to three short notes for next time, and optionally puts it in Storage with its date. The outcome and whether it goes in Storage are the user's answers, not inferred. Notes are the user's own words. Uses nothing from the allowance. If throw_it_out_signs comes back, relay it exactly and do not suggest the batch can be saved.
get_batch_status
ChatGPTEverything about one batch: its plan as PreserveAdvisor wrote it, each check so far with its verdict, notes carried in from last time, and its outcome if finished. Plan steps, times and temperatures are PreserveAdvisor's own and are relayed exactly as returned, not rounded or re-derived.
get_batches
ChatGPTThe user's batches: the ones in progress (with a probably_done flag when one is likely ready to finish) and recent finished ones with their outcome and notes for next time. Fits "what have I got going", "is anything ready", and finding a batch_id.
get_last_notes
ChatGPTThe user's own notes for next time from the last finished batch of the same method and food. Fits when they are about to make something again, or want to know what they changed last time.
get_method_options
ChatGPTWith no arguments: the eight preservation methods PreserveAdvisor covers and what each is for. With a method: its ready-made starter recipes, the foods its picker offers, and the questions its form asks, each marked on_your_plan true or false for this user. A plan built from these starts from real choices and real ids. Canning is not a method here.
get_pending_result
ChatGPTFetch the result of a form the user filled in from start_preserve_plan, start_batch_check or start_batch_finish, once the user says they have submitted it — it waits briefly for the result if it is still being built. Relay the result exactly as returned, including a decline: that is PreserveAdvisor's own answer, not an error to work around.
get_quick_guide
ChatGPTA short guide to what PreserveAdvisor does and how it works here. Fits when the user asks for a quick guide, how PreserveAdvisor works, or what it can do.
get_storage
ChatGPTWhat the user has put up: each item's place, the date it went in, how long it stays good (good_until, days_left) and a status — good, use_soon, past_prime (past its best but likely still fine), past, or no_set_date. Items needing attention come first. Fits "what should I use up" and "is my X still good" when X is already in Storage.
mark_storage_used
ChatGPTTakes an item off the Storage list. reason says why: "used" when it was used up or taken out to use, "tossed" when it was thrown out. undo: true puts it back.
start_batch_check
ChatGPTOpens a real PreserveAdvisor form for checking a batch in progress: a free-text observations box plus an optional photo for freeze drying, dehydrating and sweet preserves, or the freezer power-outage questions for freezing. It suits better than check_batch whenever a real form helps — a photo, or a user who would rather type things out than dictate them. The user opens form_url and submits; the form cannot send a signal back, so the user's own message that they are done is the only sign it was submitted. get_pending_result with the returned pending_id then returns the result.
start_batch_finish
ChatGPTOpens a real PreserveAdvisor form for closing out a batch: how it turned out, up to three notes for next time, and — for freeze drying or dehydrating only — an optional diagnosis (what happened, with an optional photo) before the notes. Add to Storage is offered only when PreserveAdvisor would allow it for this batch (not for a discard-blocked "problem", a batch already found spoiled by a diagnosis, or one whose plan was declined) — and PreserveAdvisor checks this again on submit regardless of what the form shows, the same as finish_batch does in chat. The user opens form_url and submits; the form cannot send a signal back, so the user's own message that they are done is the only sign it was submitted. get_pending_result with the returned pending_id then returns the result.
start_photo_upload
ChatGPTReturns a link the user opens to upload one photo for check_batch or diagnose_batch. Once the user says it is uploaded, photo_upload_id carries it into the check. The link works for 15 minutes. This is the only way a photo reaches PreserveAdvisor.
start_preserve_plan
ChatGPTOpens a real PreserveAdvisor form for picking a method, a food, and that method's own fields — built byte-for-byte from PreserveAdvisor's own data (the same lists get_method_options reads), not a re-transcribed guess. Once the method is known, the form suits better than questions in chat — a form with real buttons and steppers answers correctly every time; typed text the model has to parse does not. The user opens form_url and submits; the form cannot send a signal back, so the user's own message that they are done is the only sign it was submitted. get_pending_result with the returned pending_id then returns the result.
update_storage_item
ChatGPTRenames a Storage item, moves it somewhere colder, marks it opened or vacuum-sealed, or changes its amount or notes. Fields left out stay as they are. Its date is recomputed by PreserveAdvisor. A new name alone does not change what food it is. Food taken out to use is not a move: that is mark_storage_used.