AI Agents (inside one system): Use whenever the person asks to change records in a system whose AI agent may change them: every change goes through here first, and nothing is written. Pick one action and give one item per record, at most 25. set_fields: fills, corrects, empties or makes records with the fields describe_record_type lists (type, and id unless it makes a new record; set holds field keys and new values, clear the keys to empty). update_fields: New values for fields of a record that exist in the person's own system, such as a lead status or a custom field, by their own names. (type, id, fields). move_stage: A record moved to another stage or status of its pipeline, such as a deal to proposal sent or to won; a won or lost stage closes the record. (type, id, stage; optional pipeline). add_note: A note on a record's timeline in the person's system. (type, id, text; optional at, user). add_task: A task or follow up on a record in the person's system, such as a call next week; the system may notify the user it is assigned to. (type, id, subject, due_at; optional notes, priority, task_kind, done, user). link_records: Two records linked in the person's system, such as a contact to a deal, or an existing note or task to another record; nothing changes when they are linked already. (type, id, other_type, other_id). unlink_records: The link between two records removed; both records stay as they are, and only the person can approve it. (type, id, other_type, other_id). Nothing is written yet: the answer shows, per record, what it holds now and would hold after, plus a proposal id. Show it to the person, say so first when something would be sent to the people in their system, ask whether to go ahead, and only then call apply_proposal; when needsApproval is true, share the approve link instead. Not for reading (use search_records or get_record). Never deletes and never records a payment.
