Car Log

Adds a car to the user's Car Log from the details the user typed: make, model, year and current odometer in km. A user can keep any number of cars, and every call that saves adds a new one. When the user already has a car with the same make, model and year, nothing is saved and the reply asks whether this is a second car; a repeat call with confirmAnother true saves it. When that existing car is archived, the reply offers unarchive_vehicle for it (by its id) or confirmAnother for a separate new car. intervals holds this make, model and year's typical service intervals, one entry per service category with a sound known figure, in km and/or months. They are stored as estimates the user can change, and the reply calls them estimates. The card shows the car and its intervals; the text reply summarises them.

add_vehicle

Attaches original documents to a saved record, so it becomes a document-backed record. recordId is the record; the attachment comes as file, several as files (or document_id for a Car Log document). The server stores each file it can reach. Files are added after the ones the record already has, up to 10; a call that would take the record past that is refused whole. A record of a car the user archived takes files only with archived true. A document another record cites is not shared. The documents are stored as they are, not read or re-extracted, and the record's fields stay unchanged.

attach_document

Saves the service receipts the user attached at once, one record per receipt. files holds every attachment; each item is one receipt, and its file_indexes are the positions in files of that receipt's pages or photos, in reading order, at most 10 (or its document_id for a Car Log document). Each file belongs to one receipt only. Each item's fields, confidences, documentProblem and problemDetail follow capture_event. When the items are more than one receipt, the first call saves nothing and returns the grouping for the user to check: each receipt with its file numbers, garage and total. A repeat call with the same items and confirmed true saves them. The grouping is the user's: it changes only when the user says which file belongs where, and the changed grouping is shown again before saving. Each item is saved or refused on its own; a failed item never undoes the others. An item refused with duplicateConfirmation carries a save-another question for the user; resubmitting that item with confirmDuplicate true saves it. Currency is checked for every receipt before the grouping preview: an unstated currency takes the user's default; with no default, the whole batch saves nothing and the reply asks which currency, and a repeat call with it shows the grouping again. After saving, the reply asks whether to use it for future receipts (set_currency saves it on a yes). A single receipt goes to capture_event.

backfill_documents

Saves one service or maintenance event the user described in a sentence. Each field is {value, confidence}: confidence is "sure" for a value written in the user's message or shown on the document ("89 EUR" states the currency) and "unsure", with a short reason, for an inferred one. Fields the user did not give are absent. currency is present only when the user stated it or the document shows it; an unstated currency takes the user's default. With no default, nothing is saved and the reply asks which currency; a repeat call with it saves the record, and the reply then asks whether to use it for future receipts (set_currency saves it on a yes). Dates are ISO (YYYY-MM-DD), amounts are plain numbers, currency is a three-letter code. eventType is a short label such as oil change. categories lists every category the record covers, other when none fits. Each fact sits in the field that fits it; what fits no field is the comment, in the user's own words, absent when nothing is left over. The server checks the numbers, saves the record even when a check fails, and reports the check in its reply. amount is the grand total paid, tax included; tax or VAT, discounts and fees are their own line items, so the line items sum to amount. Car Log does not read documents: for an attached document the fields come from the caller's reading of it, and the attachment comes as files (or document_id for a Car Log document). One call is one receipt: files holds every file of that receipt (its pages or photos, in reading order, at most 10 files), and the server keeps them all as that record's originals. Several receipts at once go to backfill_documents, one item per receipt. The server stores each file it can reach and saves the record either way. documentProblem with a problemDetail marks a document that is unreadable or not about the car; userInsists true saves it when the user says it is for the car. A save identical to a recent one returns status duplicateConfirmation with a save-another question for the user; a repeat call with confirmDuplicate true saves a second record. vehicleId picks one of several cars.

capture_event

Marks flagged values of a saved record as right, as the user confirmed them: the flags on the named fields clear and each value stays as it is. fields lists every field the user's message confirms. A field with no flag changes nothing, and the reply says so. A record of a car the user archived changes only with archived true. recordId comes from an earlier Car Log reply. The confirmation is logged with who made it and when.

confirm_values

Changes fields of a saved record, from the user's own words. changes holds every change from one user message as [{field, value}], all in one call; field and value carry a single change instead. When the user adds, rewrites or removes the leftover note of the record, that is the comment field. A record of a car the user archived changes only with archived true. When the user says what the service covered, the categories field is the whole list of what it covered, at least one, each one of oil_change, filters, brakes, brake_fluid, tyres, battery, inspection, wipers, other; it replaces the old list. value null clears odometer, amount, garage, invoice number or comment, for a value the user says is wrong and has none to give, or wants removed; date, event type, currency, line items and categories cannot be cleared. Changes apply all or nothing. An amount needs a currency: a stated currency wins, otherwise the record's currency or the user's default currency is used. With neither, nothing changes and the reply asks which currency, for a repeat call with the amount and currency together; the reply then asks whether to use it for future receipts (set_currency saves it on a yes). recordId comes from the earlier reply. The server keeps the original value, logs who changed what and when, and checks the numbers again. A value the field cannot hold is refused and nothing changes. A reply that changed the record carries it with its change log; each change's groupId identifies it for undo_correction.

correct_event

Deletes one saved record: "delete this record" or a named record. recordId is the record's id (record.id) from an earlier Car Log result, for the record the user named. The record's own car is used, so it takes no car. It takes two calls. The first, with recordId only, deletes nothing and shows the user what goes. The second, with the same recordId and confirmed true, deletes it once the user has said "yes", or its equivalent in their own language, in a later message of their own. A record of a car the user archived is deleted only with archived true on both calls. The record leaves every read with its corrections and files, all kept for 30 days; restore_deleted brings it back for "undo" or a later "bring it back".

delete_record

Deletes everything the user keeps in Car Log: every car, record, document and share link. Answers "delete all my Car Log data", "delete everything" and "delete my records" meant as all of them; delete_record deletes one record. It covers all cars, so it takes no car. It takes two calls. The first, without confirmation, deletes nothing: it shows the user what goes and offers an export first (per car: a user with several cars exports each in turn). The second carries confirmation, the word "delete" or its equivalent in the user's language exactly as the user typed it in a later message of their own, and deletes the data. The account and its connection to this chat stay.

delete_all

Gives the user their own copy of one car's data: a CSV with one row per record (source file name, and both the original and corrected values where something was changed) and a ZIP of the stored original documents named by date, as download links that work for 24 hours. Answers "export the records of <car> as CSV", "export everything", "download my data" and "give me a spreadsheet of my records". vehicleId picks the car the user names among several. The reply carries both files as attachments.

export

Answers "which oil did the shop use" and "what did the brake pads cost": the saved line items of one car whose wording contains the query, newest first, each quoted exactly as the document wrote it with its amount and its source (invoice number, garage, date; or "typed, no document"). The match is plain text on the document's own words, so a query matches when it is the word as the garage would print it, in the document's language. A corrected value comes back as corrected. vehicleId (vehicle.id from an earlier Car Log result) picks the car the user names among several. The reply quotes the lines only; what a line means is not part of it. get_last_service answers the last service of a type.

find_line_items