LWLT-AI/agent设计规范/skills/ltjt-business-operation/references/updates-and-travelers.md

Updates and Traveler-List Rules

Existing order update

Use order_update only with an existing order reference. Express changes as explicit actions:

{
  "target": "rooms.TWN",
  "operation": "set",
  "value": 10
}

Allowed operations are set, delta, and append for supported targets. A delta needs a current baseline; do not apply it to an unknown snapshot. Do not turn “全部覆盖” into a broad overwrite. Repeated identical updates must be checked by the safety layer before execution.

Current supported planning targets include room counts, remarks, pax, prices, and traveler-list actions. Pax/price updates remain optional/unverified across routes; do not promise them as equivalent to verified room/remark behavior.

Traveler-list import

Use passenger_list_import when the request is primarily to import, append, correct, replace, or reduce a traveler list. Require the existing order reference and one of:

• an attachment object containing a path and metadata; or
• a structured passenger_list intent.

Do not open the workbook in the Agent or Skill layer. Do not put traveler names, passport numbers, birth dates, phone numbers, or copied rows into the operation or customer reply. The deterministic import layer owns parsing, expected-count checks, row import, PII redaction, and post-import verification.

For modify, delete, replace, full_replace, or reduce, require explicit confirmation before execution. A missing confirmation is a blocker, not a warning.

Failure behavior

• Missing identifier: needs_clarification/blocked.
• Missing target or operation: blocked.
• Unsupported target: blocked.
• Missing delta baseline: blocked.
• Negative resulting pax/room value: blocked.
• Attachment parse or verification failure after a confirmed update: use the appropriate recovery path; do not save unrelated changes again.