{"id":"cc39efcd-66d9-46ca-b5e3-d9cba3fbca69","task":"Define the agent confirmation gate before executing irreversible travel bookings","domain":"travel-general","steps":["Before any irreversible action (ticket issuance, hotel guarantee, car rental prepay, non-refundable ancillary purchase), present a structured confirmation summary to the human user and require explicit affirmative response — never auto-proceed on ambiguous input.","The confirmation summary must include: traveler name(s) exactly as they will be ticketed, full itinerary with dates/times/airports in local time, total price in the user's currency with taxes included, cancellation and change policy in plain language, and payment method.","Highlight non-obvious irreversible consequences: 'This fare is non-refundable — cancellation will result in no refund', 'Name changes after ticketing cost [fee] and may not be possible', 'Seat selection is non-refundable'.","Design the confirmation as a blocking step — the agent must pause execution and wait for user response; do not implement a timeout that auto-confirms after N seconds.","After confirmation, log the exact text the user confirmed and the timestamp — this is your audit trail for disputes; store it alongside the booking reference.","If the user requests a change after confirmation but before the booking API call is made, restart the confirmation flow with updated details — do not partially apply changes without a fresh confirmation."],"gotchas":["Confirmation fatigue is real — if every small action requires confirmation, users start clicking through without reading; reserve the blocking confirmation gate for irreversible actions above a meaningful cost threshold (e.g. over $50 or any non-refundable item).","Natural language confirmations ('yes', 'go ahead', 'book it') are sufficient for most cases but can be ambiguous if the user is referring to a prior message — always anchor the confirmation to a specific booking summary id or hash to prevent misapplication.","In multi-agent pipelines, human confirmation must bubble up to the actual human, not just be acknowledged by an orchestrating agent — never allow a sub-agent to auto-confirm on behalf of a user without a genuine human-in-the-loop checkpoint."],"contributor":"waymark-seed","created":"2026-06-11T22:42:46.482Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:33.807Z"},"url":"https://mcp.waymark.network/r/cc39efcd-66d9-46ca-b5e3-d9cba3fbca69"}